-
-
Notifications
You must be signed in to change notification settings - Fork 21k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VisualServer.set_default_clear_color doesn't do anything #4939
Comments
no longer an issue in 3.0 |
There's no sample and I'm not an expert. I might be off base. Does any of this help? Ubuntu 17.10 x64 ### 4939-1 - Background Color
### 4939-2 - Background Color Sky
### 4939-3 - Background Clear Color - THIS?If you're trying to do something like this, then I agree that it isn't working how I assume it would. But I'm making a lot of assumptions here.
|
No can do. GitHub doesn't allow .gd attachments. Best I can do: 4939-1.gd.txt If you're asking me to completely rework my examples, that's a resounding no. I'm only putting this together as an example of a QA test. The bug reporter should be providing the examples if these aren't to your taste. Do you have an example then? |
Since you're offering to test, I'm assuming that one of these, probably 4939-3 is similar to your issue and you would expect that example to work (the background be green) as well. If so, here is an updated test that builds in a little buffer to ensure everything's initialized. Just for good measure, I threw the Test
In the past, I've had the best success working with VisualServer in _init() or _initialize() as it was in my original example. |
This script is designed to work from the command line, yes. It is designed to test the use of 'clear color' in isolation from other factors. I don't know the syntax for running a script with an AppBundle on OSX, sorry. |
The script is not a fix. It merely attempts to demonstrate the issue in the absence of any other examples. If the script is accurate, it serves as a test for a developer who might try and address this reported bug. |
We have now entered release freeze for Godot 3.0 and want to focus only on release critical issues for that milestone. Therefore, we're moving this issue to the 3.1 milestone, though a fix may be made available for a 3.0.x maintenance release after it has been tested in the master branch during 3.1 development. If you consider that this issue is critical enough to warrant blocking the 3.0 release until fixed, please comment so that we can assess it more in-depth. |
I tested with latest version compiled (Godot 3.1.dev from 01/30/2018) and this issue is present (using Ubuntu 16.04 64bits). For a simple test, use the "2d platformer" from godot demos, delete the node "parallax_bg" from main scene and run it: the background is grey (the default Godot editor color). Add the code below in the player.gd:
Now the background should be black (in Godot 2.1.x this is true) but in latest Godot 3.1.x (or Godot 3.0.0) the background remains gray. |
i tried this on windows and it appears it doesn't work
Seems like environment clear setting overrides it? I cannot tell. |
As a workaround, add the code below in the player.gd (using the example "2d platformer" quoted above):
|
Thanks, the fact that setting the project setting manually is a good hint to fix I'd suggest comparing what happens in both cases to find out why the latter doesn't work when the former does. |
Why do changes on project settings affect a running game? (This is not how it used to work) |
is this still an issue? |
@CarlGustavAlbertDwarfsteinYung unfortunatly yea :P, tested on 3.0.2 |
godot/servers/visual/visual_server_raster.cpp Lines 1272 to 1274 in 22d83bc
Current master: godot/servers/visual/visual_server_raster.cpp Lines 160 to 161 in 5971088
|
really? Since 2016 omg lol |
The way I see it, the solution is to make
@reduz would this stomp all over the render system? |
i put it anywhere doesn't seem to do anything
possibly an OSX only issue
The text was updated successfully, but these errors were encountered: