Aller au contenu

Photo

Tint Overrides Not Working


  • Veuillez vous connecter pour répondre
11 réponses à ce sujet

#1
Azag977

Azag977
  • Members
  • 5 messages
I followed the "Creating Recolors of existing items" tutorial and was unsuccessful at changing the intended armor color for a custom created item.  I did notice that when I select the custom tint override the color changed to a default gray color.  This exact color scheme is what I see for all of the default tint overrides.  What can I do to resolve this?

#2
Phaenan

Phaenan
  • Members
  • 315 messages
Where are those tints files ? As in, in which override folder ? 'Cause DA won't use properly tints found in the Addin / uid / * / Override folders, so if that's the case you'll have to move those files to the Package / core / override folder.

That being said, I can't be sure that'll be relevant to your specific case. :o

#3
Azag977

Azag977
  • Members
  • 5 messages
My tint_override.gda is located in Documents\\BioWare\\Dragon Age\\packages\\core\\override. Regardless, when I pick any of the tint overrides within the toolset, (9), (10), green, blue, etc, they do not show any change other than the default grey color scheme and they do not make any color change while in game.

#4
IriathZhul

IriathZhul
  • Members
  • 18 messages
I have the same problem... I followed the tutorial, placed my GDA in the Documents\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\BioWare\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\Dragon Age\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\packages\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\core\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\override. None of the tint overrides do anything other than turn the armor a flat gray. It's very depressing.

*edit* The tint overrides only turn the armor a flat gray.

Modifié par IriathZhul, 09 juin 2010 - 02:39 .


#5
IriathZhul

IriathZhul
  • Members
  • 18 messages
Sorry about the above post's ugliness. I tried editing something and my connection spazzed and this came out on the other end. At least it's still legible.

#6
LostAngelz

LostAngelz
  • Members
  • 2 messages
Could any1 provide any help to his? i have the exact same problem as well and it's driving me nuts!

Thx for any help in advance!

#7
LostAngelz

LostAngelz
  • Members
  • 2 messages
accidental double post.

Modifié par LostAngelz, 01 août 2010 - 05:44 .


#8
Proleric

Proleric
  • Members
  • 2 360 messages
OK, several issues here, I think.

The non-default tint overrides in the toolset (Blue, Green, etc) seem to do little or nothing. My impression is that they're deprecated.

So, you'll need to make a custom tint override (see tutorial).

Before you do the work, take a quick look ahead at the step "Open the tint file for the object you are recoloring", if only to confirm that the tint map actually has sections that can be tinted.

You can safely put the tint override GDA in your module override folder, to avoid compatibility problems with other mods. There is a reported problem which requires tint maps to be placed in the packages override folder, but AFAIK that's a different issue which doesn't apply here.

Now reopen the toolset. Your custom tint override should be available on the item properties dropdown, and it should work fine.

If your custom tint override turns the armour grey, you've probably made a minor mistake when following the tutorial, such as the colour values in your material.

There is a toolset bug which you'll probably have to work around. If you find that the suggestion about using packages override works for you, you can still move the GDA back to module override before distributing to players.

Modifié par Proleric1, 01 août 2010 - 06:42 .


#9
tadej123

tadej123
  • Members
  • 1 messages
please help i dont have override map....:(

#10
Proleric

Proleric
  • Members
  • 2 360 messages
Can you explain the problem you're having in detail?

#11
errant_knight

errant_knight
  • Members
  • 8 256 messages
So, my tint overrides are in the addins, and they seem to be working properly. Can you tell me what the bug is, so I know it if I see it?

#12
Proleric

Proleric
  • Members
  • 2 360 messages
The bug is described here.