[Unity] Shader problems
Posted: 02 Dec 2015, 08:53
Hey guys..
we are currently evaluating the 1.2.5f7 build of NoesisGUI for Unity but we face a problem we can't solve and we think you might want to take a look at. We are using Unity 5.2.2f1.
Here is a screenshot of what we see AFTER we hit play:
There is not much in the scene at that point because we instantiate pretty much all of our objects during runtime.
One thing we very much depend on is to be able to use SVGs with RageSuite from freakow. As you can see, this blue tint does not only affect the gamescreen alone, but rather the whole game window (including stats etc.). Even when we resize it, it's still there.
Just for comparison we instantiated a RageTools vector object in this scene (using a much more expensive shader) and used NoesisGui to open a context menu right next to it. As you can see, the object is not affected by this, but the context menu is. One thing we found out is that if we change their basic (Ragetools) shader for our objects to something different, this behavior stops.
Do you have any clue how we may be able to fix this?
FYI: We are in touch with the RageTools author just as well of course, but this is only happing when using both solutions (NoesisGUI & RageTools) in the same project.
Regards
we are currently evaluating the 1.2.5f7 build of NoesisGUI for Unity but we face a problem we can't solve and we think you might want to take a look at. We are using Unity 5.2.2f1.
Here is a screenshot of what we see AFTER we hit play:
One thing we very much depend on is to be able to use SVGs with RageSuite from freakow. As you can see, this blue tint does not only affect the gamescreen alone, but rather the whole game window (including stats etc.). Even when we resize it, it's still there.
Just for comparison we instantiated a RageTools vector object in this scene (using a much more expensive shader) and used NoesisGui to open a context menu right next to it. As you can see, the object is not affected by this, but the context menu is. One thing we found out is that if we change their basic (Ragetools) shader for our objects to something different, this behavior stops.
Do you have any clue how we may be able to fix this?
FYI: We are in touch with the RageTools author just as well of course, but this is only happing when using both solutions (NoesisGUI & RageTools) in the same project.
Regards