Just downloaded the latest Rimworld Alpha this morning after getting my SendOwl email. Game boots up to a completely black screen, can't see or click on anything. Tried a fresh restart, no dice. :(
Same here, OS X 10.9.5.
First time it started ok in a window, but than I switched it fullscreen and since then it is only fullscreen black page with cursor visible. There are sound effects when I move the mouse cursor, so I guess the interface is there, just not visible.
Is there a way to force it to open in window again?
Same here. Also 10.9.5.
Same here, hoping Tynan hops on this one soon so I can enjoy this game
I got the same black screen + cursor as above users, but I was able to fix it.
SOLUTION: While game is full screen & black, use CMD+OPT+SHIFT+ESC (opens the force-quit menu).
This will knock the game back to the windowed menu screen (you can dismiss the force quit window at this point). At this point the game will play, but will remain windowed instead of full screen (which I rather prefer anyway).
I think it's actually just Command-Esc which knocks it out of fullscreen. Helpful tip, seems to work. Thanks!
Phew, I tried everything on the Mac to get it running, and a simple cmd+esc did the trick, awesome, and thanks :)
Same here.
534 works perfectly, 581 can't run in full screen.
Give us fullscreen back !
Same problem here. If I run the previous Alpha 6 executable, set fullscreen mode, then exit and run Alpha 7, it will work properly in fullscreen mode. But if I attempt to switch from windowed to fullscreen mode within Alpha 7, the screen goes black except for the mouse cursor. I can still hear that the UI is active as I mouse around on that black screen, because I hear the clicks from the buttons on the mouseovers, but obviously I can't do anything.
By the way, pressing Cmd+Esc will switch back to windowed mode and make the window contents reappear, for anyone who feels they are stuck in that mode.
Reported on Mantis: http://ludeon.com/mantis/view.php?id=1224
I desperately need a log file to be able to fix this!
Can anyone find theirs and post it please? It's found in:
~/Library/Logs/Unity/Player.log
Quote from: Tynan on October 02, 2014, 11:50:53 AM
I desperately need a log file to be able to fix this!
Can anyone find theirs and post it please? It's found in:
~/Library/Logs/Unity/Player.log
I just reproduced the issue on a fresh computer right after installing Alpha 7. (It came up in a window by default, and I then switched it to fullscreen and then used Cmd+Esc to return to the windowed screen and exited the program after staring at the black screen for ten seconds or so.) The log contents you asked about are below (thankfully it's not too long). Let me know if there is anything else I can provide to you to diagnose the issue.
Initialize engine version: 4.5.3f3 (fca41a4fabea)
GfxDevice: creating device client; threaded=1
LoadSystemBundle - Could not create bundle URL for framework 'OpenGL.framework'
OpenGL:
Version: OpenGL 2.1 [2.1 ATI-1.24.38]
Renderer: ATI Radeon HD 5750 OpenGL Engine
Vendor: ATI Technologies Inc.
VRAM: 1024 MB
Extensions: GL_ARB_color_buffer_float GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_seamless_cube_map GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture_array GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array_bgra GL_APPLE_aux_depth_stencil GL_APPLE_client_storage GL_APPLE_element_array GL_APPLE_fence GL_APPLE_float_pixels GL_APPLE_flush_buffer_range GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_packed_pixels GL_APPLE_pixel_buffer GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_specular_vector GL_APPLE_texture_range GL_APPLE_transform_hint GL_APPLE_vertex_array_object GL_APPLE_vertex_array_range GL_APPLE_vertex_point_size GL_APPLE_vertex_program_evaluators GL_APPLE_ycbcr_422 GL_ATI_blend_equation_separate GL_ATI_blend_weighted_minmax GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_IBM_rasterpos_clip GL_NV_blend_square GL_NV_conditional_render GL_NV_depth_clamp GL_NV_fog_distance GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_barrier GL_SGI_color_matrix GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod
GL: buggy packed depth stencil; Deferred rendering will use slower rendering path
GL: Detected 11620145 MB VRAM
Begin MonoManager ReloadAssembly
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/UnityEngine.dll (this message is harmless)
Loading /Applications/RimWorld581Mac.app/Contents/Data/Managed/UnityEngine.dll into Unity Child Domain
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-CSharp-firstpass.dll (this message is harmless)
Loading /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-CSharp-firstpass.dll into Unity Child Domain
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-CSharp.dll (this message is harmless)
Loading /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-CSharp.dll into Unity Child Domain
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-UnityScript-firstpass.dll (this message is harmless)
Loading /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-UnityScript-firstpass.dll into Unity Child Domain
- Completed reload, in 0.518 seconds
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/System.dll (this message is harmless)
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/System.Core.dll (this message is harmless)
RimWorld 0.7.581 rev35981
(Filename: /Applications/buildAgent/work/d63dfc6385190b60/artifacts/MacStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/System.Xml.dll (this message is harmless)
Mods config data is from build 534 while we are at build 581. Resetting.
(Filename: /Applications/buildAgent/work/d63dfc6385190b60/artifacts/MacStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/System.Xml.Linq.dll (this message is harmless)
Knowledge data was missing key MedicalOperations. Adding it...
(Filename: /Applications/buildAgent/work/d63dfc6385190b60/artifacts/MacStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
Knowledge data was missing key MedicalOperations. Adding it...
(Filename: /Applications/buildAgent/work/d63dfc6385190b60/artifacts/MacStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
Thanks Mystic! I don't fully understand the steps you're describing. At what point was the screen black? Is it black only in fullscreen or windowed? When you Command+Esc back and forth, is it consistently black in one mode and okay in the other? If you start playing, and switch modes back and forth, does it go black and then return to normal?
Also, can you run it again and post the log again? I want to capture it without the config data resets involved.
Thank you!
Quote from: Tynan on October 02, 2014, 12:27:45 PM
Thanks Mystic! I don't fully understand the steps you're describing. At what point was the screen black? Is it black only in fullscreen or windowed? When you Command+Esc back and forth, is it consistently black in one mode and okay in the other? If you start playing, and switch modes back and forth, does it go black and then return to normal?
Also, can you run it again and post the log again? I want to capture it without the config data resets involved.
Thank you!
The screen goes black when I tick the "Fullscreen" item in the Options dialog to switch to fullscreen. The screen fades to black as it is expanding to cover the whole desktop, and then just stays that way, except that the mouse cursor is visible. Moving the mouse around causes audible mouseover sounds from the UI elements that should be on the screen, so the program apparently thinks it is still operating normally at that point ... I just can't see what I am doing.
I can do this repeatedly in a single game load with the same results. I also tried starting a game in windowed mode, then switching to fullscreen while in the game ... same results (screen turns black anytime I switch to fullscreen mode). It is consistently black in fullscreen mode other than the mouse cursor, and never black in windowed mode.
Note that Cmd+Esc doesn't toggle back and forth ... it just exits fullscreen mode back to windowed mode. Hitting that key combo while the game is in windowed mode has no effect.
Please take note of the fact that, if I run Alpha 6 and set the fullscreen mode there, then exit that version and launch Alpha 7 so that it is loading in fullscreen mode by default, then the fullscreen mode works perfectly in Alpha 7. That is, until I switch to a windowed mode and then back from within Alpha 7, then I get the fullscreen black window back. It is something about performing the switch from windowed to fullscreen mode from within Alpha 7.
Here's a new log from repeating the steps described earlier (just starting the app, attempting the switch to full screen, then exiting).
Initialize engine version: 4.5.3f3 (fca41a4fabea)
GfxDevice: creating device client; threaded=1
LoadSystemBundle - Could not create bundle URL for framework 'OpenGL.framework'
OpenGL:
Version: OpenGL 2.1 [2.1 ATI-1.24.38]
Renderer: ATI Radeon HD 5750 OpenGL Engine
Vendor: ATI Technologies Inc.
VRAM: 1024 MB
Extensions: GL_ARB_color_buffer_float GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_seamless_cube_map GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture_array GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array_bgra GL_APPLE_aux_depth_stencil GL_APPLE_client_storage GL_APPLE_element_array GL_APPLE_fence GL_APPLE_float_pixels GL_APPLE_flush_buffer_range GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_packed_pixels GL_APPLE_pixel_buffer GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_specular_vector GL_APPLE_texture_range GL_APPLE_transform_hint GL_APPLE_vertex_array_object GL_APPLE_vertex_array_range GL_APPLE_vertex_point_size GL_APPLE_vertex_program_evaluators GL_APPLE_ycbcr_422 GL_ATI_blend_equation_separate GL_ATI_blend_weighted_minmax GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_IBM_rasterpos_clip GL_NV_blend_square GL_NV_conditional_render GL_NV_depth_clamp GL_NV_fog_distance GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_barrier GL_SGI_color_matrix GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod
GL: buggy packed depth stencil; Deferred rendering will use slower rendering path
GL: Detected 11620145 MB VRAM
Begin MonoManager ReloadAssembly
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/UnityEngine.dll (this message is harmless)
Loading /Applications/RimWorld581Mac.app/Contents/Data/Managed/UnityEngine.dll into Unity Child Domain
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-CSharp-firstpass.dll (this message is harmless)
Loading /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-CSharp-firstpass.dll into Unity Child Domain
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-CSharp.dll (this message is harmless)
Loading /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-CSharp.dll into Unity Child Domain
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-UnityScript-firstpass.dll (this message is harmless)
Loading /Applications/RimWorld581Mac.app/Contents/Data/Managed/Assembly-UnityScript-firstpass.dll into Unity Child Domain
- Completed reload, in 0.057 seconds
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/System.dll (this message is harmless)
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/System.Core.dll (this message is harmless)
RimWorld 0.7.581 rev35981
(Filename: /Applications/buildAgent/work/d63dfc6385190b60/artifacts/MacStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/System.Xml.dll (this message is harmless)
Platform assembly: /Applications/RimWorld581Mac.app/Contents/Data/Managed/System.Xml.Linq.dll (this message is harmless)
Okay, thanks for the info Mystic.
EDIT: Yeah, this bug is brutal. There is nothing at all in that log file!
Does Unity not throw an error you can handle somewhere if a graphics device context fails to acquire?
Unity forums suggest that people end up with black in fullscreen if they choose an unsupported resolution, though in this case the user isnt manually selecting one -- so gracefully detecting and falling back would probably be the best bet if you can catch it programatically.
Quote from: Dieform on October 02, 2014, 01:45:08 PM
Does Unity not throw an error you can handle somewhere if a graphics device context fails to acquire?
Unity forums suggest that people end up with black in fullscreen if they choose an unsupported resolution, though in this case the user isnt manually selecting one -- so gracefully detecting and falling back would probably be the best bet if you can catch it programatically.
People are running A6 without issue, but A7 fails in the same resolution, so that's unlikely to be an issue. In any cases Unity doesn't expose anything related to graphics contexts to me.
I'm suspecting it may be related to full screen postprocess effects.
Quote from: Tynan on October 02, 2014, 01:08:43 PM
Okay, thanks for the info Mystic.
EDIT: Yeah, this bug is brutal. There is nothing at all in that log file!
Yeah. I don't know Unity at all, but even to my eyes that log file looked pretty devoid of any messages pertinent to this. And the in-game behavior suggests that everything thinks it is working normally. Can you at least reproduce it on a locally accessible Mac, I hope? ('Cause otherwise its going to be even harder to track down.)
Quote from: Mystic on October 02, 2014, 02:16:27 PM
Quote from: Tynan on October 02, 2014, 01:08:43 PM
Okay, thanks for the info Mystic.
EDIT: Yeah, this bug is brutal. There is nothing at all in that log file!
Yeah. I don't know Unity at all, but even to my eyes that log file looked pretty devoid of any messages pertinent to this. And the in-game behavior suggests that everything thinks it is working normally. Can you at least reproduce it on a locally accessible Mac, I hope? ('Cause otherwise its going to be even harder to track down.)
Unfortuantely I don't even own one. I'm installing one on a VM. I know someone who would let me borrow one too.
Quote from: Tynan on October 02, 2014, 02:18:00 PM
Quote from: Mystic on October 02, 2014, 02:16:27 PM
Quote from: Tynan on October 02, 2014, 01:08:43 PM
Okay, thanks for the info Mystic.
EDIT: Yeah, this bug is brutal. There is nothing at all in that log file!
Yeah. I don't know Unity at all, but even to my eyes that log file looked pretty devoid of any messages pertinent to this. And the in-game behavior suggests that everything thinks it is working normally. Can you at least reproduce it on a locally accessible Mac, I hope? ('Cause otherwise its going to be even harder to track down.)
Unfortuantely I don't even own one. I'm installing one on a VM. I know someone who would let me borrow one too.
Hmm, and the VM doesn't show this behavior, I suppose. That does make it rough. :(
If you make any test builds (perhaps with extra logging, switches for testing, etc) that you'd like to have evaluated on the actual hardware in regards to this issue, you can certainly contact me via email.
Same here,
Retina 15"
2.6GHz i7
16GB DDR3
Nvidia GFCE GT 750M (2048MB)
Yours for testing if you make test builds.
I am also experiencing the bug in alpha 7
Quote from: Mystic on October 02, 2014, 02:27:59 PM
If you make any test builds (perhaps with extra logging, switches for testing, etc) that you'd like to have evaluated on the actual hardware in regards to this issue, you can certainly contact me via email.
Thanks. We may have to do that. Much appreciated.
I actually was able to repro this in a VM.
Quote from: Tynan on October 02, 2014, 03:35:38 PM
I actually was able to repro this in a VM.
Excellent ... that should give you a fighting chance against it. Go get 'em! :)
I hate bugs like this.
Quote from: Mystic on October 02, 2014, 03:46:37 PM
Quote from: Tynan on October 02, 2014, 03:35:38 PM
I actually was able to repro this in a VM.
Excellent ... that should give you a fighting chance against it. Go get 'em! :)
Just confirm this for me - did the bug appear in actual gameplay, or only in the menus? If you start a game and then switch to fullscreen in-game goes it go black?
Quote from: Tynan on October 02, 2014, 04:11:05 PM
Quote from: Mystic on October 02, 2014, 03:46:37 PM
Quote from: Tynan on October 02, 2014, 03:35:38 PM
I actually was able to repro this in a VM.
Excellent ... that should give you a fighting chance against it. Go get 'em! :)
Just confirm this for me - did the bug appear in actual gameplay, or only in the menus? If you start a game and then switch to fullscreen in-game goes it go black?
Yes, it goes black when switching during actual colony game play, as well as when in the starting menu.
To make it even weirder... Alpha 7 works perfectly in fullscreen mode on my MacBook Pro Retina 15“. No issues so far.
Quote from: stefanstr on October 02, 2014, 04:59:19 PM
To make it even weirder... Alpha 7 works perfectly in fullscreen mode on my MacBook Pro Retina 15�. No issues so far.
Curious. Is there any chance that you already had been running Alpha 6 in fullscreen, so that Alpha 7 was in fullscreen by default when you started it up? (Because that works on my system, too.) If that's the case, can you try switching Alpha 7 to windowed mode and then back to see if you then experience the problem?
Quote from: Mystic on October 02, 2014, 05:05:27 PM
Quote from: stefanstr on October 02, 2014, 04:59:19 PM
To make it even weirder... Alpha 7 works perfectly in fullscreen mode on my MacBook Pro Retina 15�. No issues so far.
Curious. Is there any chance that you already had been running Alpha 6 in fullscreen, so that Alpha 7 was in fullscreen by default when you started it up? (Because that works on my system, too.) If that's the case, can you try switching Alpha 7 to windowed mode and then back to see if you then experience the problem?
Yes, that is exactly my case. Although I have deleted all RimWorld related data in Caches to have a new start. I will try it later to move to windowed mode and back to fullscreen, but right now I will not, knowing that it might make it difficult for me to play. I like Alpha 7 too much. ;)
Quote from: stefanstr on October 02, 2014, 05:14:41 PM
Quote from: Mystic on October 02, 2014, 05:05:27 PM
Quote from: stefanstr on October 02, 2014, 04:59:19 PM
To make it even weirder... Alpha 7 works perfectly in fullscreen mode on my MacBook Pro Retina 15�. No issues so far.
Curious. Is there any chance that you already had been running Alpha 6 in fullscreen, so that Alpha 7 was in fullscreen by default when you started it up? (Because that works on my system, too.) If that's the case, can you try switching Alpha 7 to windowed mode and then back to see if you then experience the problem?
Yes, that is exactly my case. Although I have deleted all RimWorld related data in Caches to have a new start. I will try it later to move to windowed mode and back to fullscreen, but right now I will not, knowing that it might make it difficult for me to play. I like Alpha 7 too much. ;)
That's understandable, and I suspect you'd see the same problem if you did the test. One thing to note: if you still have Alpha 6 installed alongside Alpha 7 (as do I), you should be able to get fullscreen in Alpha 7 back again after such an experiment via the following procedure: once you get the black screen in Alpha 7, hit Cmd+Esc to get back to windowed mode, quit Alpha 7, run Alpha 6 (ignoring any startup errors from data file incompatibility), switch to fullscreen in Alpha 6, then exit Alpha 6 and relaunch Alpha 7. If your system is like mine, you'll have your fullscreen mode back in Alpha 7 at that point (as long as you don't change it again in Alpha 7 prior to any patch Tynan might come up with).
Fullscreen status isn't stored in ~/Library/Caches/unity.Ludeon Studios.RimWorld/Config, so where is that? Might be a place to start. I was trying to recreate the "set it in 6 and then switch to 7" without having 6 installed.
Quote from: asciiface on October 02, 2014, 06:09:04 PM
Fullscreen status isn't stored in ~/Library/Caches/unity.Ludeon Studios.RimWorld/Config, so where is that? Might be a place to start. I was trying to recreate the "set it in 6 and then switch to 7" without having 6 installed.
An interesting idea! I don't know where the setting is stored, unfortunately ... maybe Tynan or someone else more knowledgeable about this than myself will be able to help.
Wait wait, so does that work? You can make A7 run properly in fullscreen by setting it up in Alpha6?
If so, can any of you please post any relevant config files/data before and after this change? I'm desperate to see what the difference might be.
Quote from: Tynan on October 02, 2014, 06:32:16 PM
Wait wait, so does that work? You can make A7 run properly in fullscreen by setting it up in Alpha6?
If so, can any of you please post any relevant config files/data before and after this change? I'm desperate to see what the difference might be.
Where is fullscreen True/False stored? I was going to try and check it by hand without reinstalling A6
Quote from: asciiface on October 02, 2014, 06:33:30 PM
Quote from: Tynan on October 02, 2014, 06:32:16 PM
Wait wait, so does that work? You can make A7 run properly in fullscreen by setting it up in Alpha6?
If so, can any of you please post any relevant config files/data before and after this change? I'm desperate to see what the difference might be.
Where is fullscreen True/False stored? I was going to try and check it by hand without reinstalling A6
At this moment I don't even know. It's a Unity setting, in Windows it's in the registry, I don't know the Mac equivalent.
It seems the state is stored in:
~/Library/Saved\ Application\ State/unity.Ludeon\ Studios.RimWorld.savedState/
~/Library/Preferences/unity.Ludeon\ Studios.RimWorld.plist
Removing these DID force it back to starting in FullScreen, but it is still broken. I am digging around more.
$ plutil -convert xml1 ~/Library/Preferences/unity.Ludeon\ Studios.RimWorld.plist
Fullscreen:
$ ls
Config Saves Worlds
[REDACTED@ringworld ~/Library/Caches/unity.Ludeon Studios.RimWorld]
$ cat ~/Library/Preferences/unity.Ludeon\ Studios.RimWorld.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Screenmanager Is Fullscreen mode</key>
<integer>1</integer>
<key>Screenmanager Resolution Height</key>
<integer>856</integer>
<key>Screenmanager Resolution Width</key>
<integer>1440</integer>
<key>UnityGraphicsQuality</key>
<integer>1</integer>
</dict>
</plist>
windowed:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Screenmanager Is Fullscreen mode</key>
<integer>0</integer>
<key>Screenmanager Resolution Height</key>
<integer>856</integer>
<key>Screenmanager Resolution Width</key>
<integer>1440</integer>
<key>UnityGraphicsQuality</key>
<integer>1</integer>
</dict>
</plist>
Not very exciting. But this is how Unity seems to be handling it, so it literally makes 0 sense to me how opening in Alpha6 and then Alpha7 makes it work, unless someone feels like providing me the plist file from alpha6 fullscreen'd to compare (it MIGHT be different, doubt it)
I don't have any more downloads for alpha 6, so could someone follow these steps for me:
Open Alpha6, set it to fullscreen, enter a game and then exit.
Then you need to open command line and run:
edit: had the wrong unity game
plutil -convert xml1 ~/Library/Saved\ Application\ State/unity.Ludeon\ Studios.RimWorld.savedState/windows.plist
cat ~/Library/Saved\ Application\ State/unity.Ludeon\ Studios.RimWorld.savedState/windows.plist
Copy the results of cat. Then open Alpha7 and do the same and paste both results :D
I am thinking Unity Save States might have clues... I am trying to figure out a potential workaround for fullscreen
Blast! Ok, well that's as expected. But I really want to see what it looks like after it's configured by Alpha 6.
alpha 6:
$ cat ~/Library/Preferences/unity.Ludeon\ Studios.RimWorld.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Screenmanager Is Fullscreen mode</key>
<integer>1</integer>
<key>Screenmanager Resolution Height</key>
<integer>856</integer>
<key>Screenmanager Resolution Width</key>
<integer>1440</integer>
<key>UnityGraphicsQuality</key>
<integer>1</integer>
</dict>
</plist>
$ cat ~/Library/Saved\ Application\ State/unity.Ludeon\ Studios.RimWorld.savedState/windows.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<array>
<dict>
<key>MenuBar AvailableSpace</key>
<real>1179</real>
<key>MenuBar FilterInfo</key>
<true/>
<key>NSDataKey</key>
<data>
MKK6AoLOLMgOFNAq8OC3FQ==
</data>
<key>NSIsMainMenuBar</key>
<true/>
<key>NSWindowID</key>
<integer>1</integer>
<key>NSWindowNumber</key>
<integer>6340</integer>
</dict>
<dict>
<key>NSDataKey</key>
<data>
XGkm+cfz+UiuDZE8ro6hAw==
</data>
<key>NSDragRegion</key>
<data>
AAAAgAIAAAADAAAACAAAABUAAAAbAAAAKQAAAC8AAAA9AAAAlAUAAAwAAAAK
AAAAAwAAAAcAAAAVAAAAGwAAACkAAAAvAAAAPQAAAJ0FAAATAAAABAAAAAMA
AACdBQAAFgAAAAIAAAD///9/
</data>
<key>NSIsFullScreen</key>
<true/>
<key>NSTitle</key>
<string>RimWorld534Mac</string>
<key>NSUIPersistenceIsKey</key>
<true/>
<key>NSUIPersistenceIsMain</key>
<true/>
<key>NSWindowCloseButtonFrame</key>
<string>{{7, 3}, {14, 16}}</string>
<key>NSWindowFrame</key>
<string>0 0 1440 900 0 0 1440 900 </string>
<key>NSWindowID</key>
<integer>2</integer>
<key>NSWindowLevel</key>
<integer>0</integer>
<key>NSWindowMiniaturizeButtonFrame</key>
<string>{{27, 3}, {14, 16}}</string>
<key>NSWindowNumber</key>
<integer>6343</integer>
<key>NSWindowZoomButtonFrame</key>
<string>{{47, 3}, {14, 16}}</string>
</dict>
<dict>
<key>CFBundleVersion</key>
<string>4.5.0f6</string>
<key>NSDataKey</key>
<data>
A9s3HrknTCUu02+iqEx5RQ==
</data>
<key>NSExecutableInode</key>
<integer>3889295</integer>
<key>NSIsGlobal</key>
<true/>
<key>NSWindowID</key>
<integer>4294967295</integer>
<key>NSWindowZOrder</key>
<array>
<integer>6343</integer>
<integer>6344</integer>
</array>
</dict>
</array>
</plist>
Quote from: asciiface on October 02, 2014, 07:20:55 PM
alpha 6:
$ cat ~/Library/Preferences/unity.Ludeon\ Studios.RimWorld.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Screenmanager Is Fullscreen mode</key>
<integer>1</integer>
<key>Screenmanager Resolution Height</key>
<integer>856</integer>
<key>Screenmanager Resolution Width</key>
<integer>1440</integer>
<key>UnityGraphicsQuality</key>
<integer>1</integer>
</dict>
</plist>
$ cat ~/Library/Saved\ Application\ State/unity.Ludeon\ Studios.RimWorld.savedState/windows.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<array>
<dict>
<key>MenuBar AvailableSpace</key>
<real>1179</real>
<key>MenuBar FilterInfo</key>
<true/>
<key>NSDataKey</key>
<data>
MKK6AoLOLMgOFNAq8OC3FQ==
</data>
<key>NSIsMainMenuBar</key>
<true/>
<key>NSWindowID</key>
<integer>1</integer>
<key>NSWindowNumber</key>
<integer>6340</integer>
</dict>
<dict>
<key>NSDataKey</key>
<data>
XGkm+cfz+UiuDZE8ro6hAw==
</data>
<key>NSDragRegion</key>
<data>
AAAAgAIAAAADAAAACAAAABUAAAAbAAAAKQAAAC8AAAA9AAAAlAUAAAwAAAAK
AAAAAwAAAAcAAAAVAAAAGwAAACkAAAAvAAAAPQAAAJ0FAAATAAAABAAAAAMA
AACdBQAAFgAAAAIAAAD///9/
</data>
<key>NSIsFullScreen</key>
<true/>
<key>NSTitle</key>
<string>RimWorld534Mac</string>
<key>NSUIPersistenceIsKey</key>
<true/>
<key>NSUIPersistenceIsMain</key>
<true/>
<key>NSWindowCloseButtonFrame</key>
<string>{{7, 3}, {14, 16}}</string>
<key>NSWindowFrame</key>
<string>0 0 1440 900 0 0 1440 900 </string>
<key>NSWindowID</key>
<integer>2</integer>
<key>NSWindowLevel</key>
<integer>0</integer>
<key>NSWindowMiniaturizeButtonFrame</key>
<string>{{27, 3}, {14, 16}}</string>
<key>NSWindowNumber</key>
<integer>6343</integer>
<key>NSWindowZoomButtonFrame</key>
<string>{{47, 3}, {14, 16}}</string>
</dict>
<dict>
<key>CFBundleVersion</key>
<string>4.5.0f6</string>
<key>NSDataKey</key>
<data>
A9s3HrknTCUu02+iqEx5RQ==
</data>
<key>NSExecutableInode</key>
<integer>3889295</integer>
<key>NSIsGlobal</key>
<true/>
<key>NSWindowID</key>
<integer>4294967295</integer>
<key>NSWindowZOrder</key>
<array>
<integer>6343</integer>
<integer>6344</integer>
</array>
</dict>
</array>
</plist>
Configuring in alpha6 then switching to 7 didn't fix it
Quote from: asciiface on October 02, 2014, 07:22:17 PM
Configuring in alpha6 then switching to 7 didn't fix it
Well hell then...
I'm at my wits end, it might be time for you to tap the Unity community :\
@mystic can you change the title to 10.9.4 & 10.9.5? I am on *.5
Quote from: asciiface on October 02, 2014, 07:38:55 PM
I'm at my wits end, it might be time for you to tap the Unity community :\
@mystic can you change the title to 10.9.4 & 10.9.5? I am on *.5
I would change it if I had started the thread, but I didn't, so I don't have the permissions. By the way, I'm on 10.9.5 as well (on both of the Macs on which I am seeing this problem). Specs of my systems follow, in case it matters (which I don't think it does, but I suppose you never know):
iMac 27", core i7 quad 2.93GHz, 16GB RAM, ATI HD 5750 1GB video
MacBook Pro 15" (non-retina), core i7 quad 2.6GHz, 8GB RAM, NVIDIA GT 650M 1GB video
Updated.
Anyway, it's not looking good, I tried a version with some extra logging to investigate but I'm seeing absolutely nothing out of the ordinary.
I submitted a bug to Unity.
Quote from: Tynan on October 02, 2014, 09:17:53 PM
Anyway, it's not looking good, I tried a version with some extra logging to investigate but I'm seeing absolutely nothing out of the ordinary.
I submitted a bug to Unity.
Sometimes that's all you can do. I wonder if any other games have run into the same issue with the latest Unity build? I kind of hope so, actually, 'cause that might help escalate the issue and get them working on it posthaste.
Quote from: Tynan on October 02, 2014, 09:17:53 PM
Updated.
Anyway, it's not looking good, I tried a version with some extra logging to investigate but I'm seeing absolutely nothing out of the ordinary.
I submitted a bug to Unity.
Hey I am just impressed you did this much in one work day, that is light years ahead of other early access devs going "well it IS mac, so, deal with it"
Quote from: asciiface on October 02, 2014, 10:04:20 PM
Hey I am just impressed you did this much in one work day, that is light years ahead of other early access devs going "well it IS mac, so, deal with it"
I wholeheartedly agree with this.
Jumping into the fray here. I am running A7 on my Mac okay when it's attached to the same display that I was running with earlier alphas. However, I observe this problem when I switch to a different display which doesn't run at the same resolution as my first display.
Here's the rub: I manually edited Preferences/unity.Ludeon Studios.RimWorld.plist (using Xcode) and saved it, then started RimWorld, and the prefs file reset itself to the prior resolution! I've dug into every RimWorld file I can find under ~/Library, to no avail--somehow Unity really, passionately believes that my fullscreen resolution is 1920x1200 no matter what reality might say. I can't discover where it's getting that from.
Another observation: if I hit Command-Escape to force RimWorld into windowed mode, which works, then click fullscreen in the options window, I go back to black screen. There's just no way to convince it that my fullscreen resolution is something different.
Tynan: while googling, I noticed that Unity's scripting API has a way to get the list of the screen's resolutions (Screen.resolutions) and the current resolution (Screen.Resolution). Could you perhaps ensure that the current resolution is a member of the list of possible resolutions, and change it if not?
Thanks to everyone working on this problem. A7 is a wonder to behold when I play on that one monitor.
Best regards,
Josh
Quote from: joshcarter on October 03, 2014, 08:29:04 PM
Here's the rub: I manually edited Preferences/unity.Ludeon Studios.RimWorld.plist (using Xcode) and saved it, then started RimWorld, and the prefs file reset itself to the prior resolution! I've dug into every RimWorld file I can find under ~/Library, to no avail--somehow Unity really, passionately believes that my fullscreen resolution is 1920x1200 no matter what reality might say. I can't discover where it's getting that from.
Good information, so I went to look at that same user preferences file. My laptop's native resolution is 1680x1050. Here's what I found when I went into full screen mode in A7, got the black screen, then pressed Cmd-Q to exit the application:
<key>Screenmanager Is Fullscreen mode</key>
<integer>1</integer>
<key>Screenmanager Resolution Height</key>
<integer>915</integer>
<key>Screenmanager Resolution Width</key>
<integer>1533</integer>1533x915 happens to be what my most recent windowed size was.
Then I ran A6 to remind myself of how it used to behave. When I switch A6 to fullscreen in the options, it initially comes up in fullscreen, but still at the previous 1533x915 resolution, resulting in a severely aliased but still usable screen. I then can change the screen resolution to my native desktop resolution and the screen sharpens up, with the plist file containing the following afterwards:
<key>Screenmanager Is Fullscreen mode</key>
<integer>1</integer>
<key>Screenmanager Resolution Height</key>
<integer>1050</integer>
<key>Screenmanager Resolution Width</key>
<integer>1680</integer>What I next tried was to run A7 in windowed mode, then I exited and manually updated this plist file with the correct fullscreen resolution settings. However, after doing this A7 still came up initially in the windowed mode at the previous resolution.
So I am taking two things away from this round of tests:
1) it seems like either the game or Unity must be storing and getting the resolution from somewhere else and just updating this plist file after the fact. (I looked to see if there was a system-wide version of this preferences file in /Library/Preferences, but did not find one.)
2) The distinction between the version of Unity in A6 and the one in A7 seems to be that the A6 version will display fullscreen in a non-native resolution, allowing the screen to become aliased, while A7 will not attempt to display the screen at all in that situation. This has me wondering if, when A7 switches to fullscreen in Windows, it now also automatically changes to the screen's native resolution rather than making the user change that additional setting after the fact? (Someone other than I would need to check on that.) If it does this, and if A6 didn't, perhaps some new Unity code that is doing a native resolution lookup during a switch to fullscreen is failing to get the proper resolution on the Mac version?
Were both A6 and A7 built off the exact same Unity versions?
Quote from: Dieform on October 05, 2014, 02:51:52 PM
Were both A6 and A7 built off the exact same Unity versions?
I believe not. From my research thus far there was a Unity update in between. The previous version of Unity would accept resolutions your screen couldn't handle and "just do it". The version of unity a7 is on just black screens if it is an unsupported resolution. We could work around this except Unity's accessing of its plist files seems flakey at best (it tends to write TO the file before it reads from it)
Quote from: asciiface on October 05, 2014, 05:17:49 PM
Quote from: Dieform on October 05, 2014, 02:51:52 PM
Were both A6 and A7 built off the exact same Unity versions?
I believe not. From my research thus far there was a Unity update in between. The previous version of Unity would accept resolutions your screen couldn't handle and "just do it". The version of unity a7 is on just black screens if it is an unsupported resolution. We could work around this except Unity's accessing of its plist files seems flakey at best (it tends to write TO the file before it reads from it)
Tynan did mention earlier in this thread that he'd used a newer Unity version on A7, and that he gets exactly the same black screen if he rebuilds A6 using that newer version. So I believe your research to be spot on. Did you find additional developers reporting the same "black screen on unsupported resolutions" behavior with the latest versioon of Unity, then?
I didn't get any specific Unity versions out of it, but I did find exactly identical issues involving Unity updates and resolution handling. The one that stuck out was that a previous version of Unity just dealt with different resolutions and rendered it anyway while a newer one just doesn't render.
Quote from: Mystic on October 06, 2014, 09:34:21 AM
Quote from: asciiface on October 05, 2014, 05:17:49 PM
Quote from: Dieform on October 05, 2014, 02:51:52 PM
Were both A6 and A7 built off the exact same Unity versions?
I believe not. From my research thus far there was a Unity update in between. The previous version of Unity would accept resolutions your screen couldn't handle and "just do it". The version of unity a7 is on just black screens if it is an unsupported resolution. We could work around this except Unity's accessing of its plist files seems flakey at best (it tends to write TO the file before it reads from it)
Tynan did mention earlier in this thread that he'd used a newer Unity version on A7, and that he gets exactly the same black screen if he rebuilds A6 using that newer version. So I believe your research to be spot on. Did you find additional developers reporting the same "black screen on unsupported resolutions" behavior with the latest versioon of Unity, then?
(https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcRX4o7NBHBwC1npouqXj-bP4STJ84CZ5Q4dUCq0xkD5QNgnpJF_iZAUQw)
UNITY
According to the Info.plist, Alpha 6 was using version 4.5.0f6 of Unity. Alpha 7 is using version 4.5.3f3.
I may be talking through my hat here, but I thought I'd read something that indicated Unity had an API method for returning the native resolutions supported by a display. I don't know if that API exists, or if it works correctly on Macs or not, but if it does, I wonder if it might be possible for RimWorld itself to query that information and then change to a/the natively supported resolution immediately before attempting the switch to fullscreen? Could that possibly address this issue without a Unity patch?
that is one solution I had seen on other bug report forums, automagically correcting the resolution.
If I know anything about development and systems tho, (and I know quite a lot, not to toot my own horn more than it is worth), unless implemented with some thought and care could cause more harm than good.
Quote from: Mystic on October 07, 2014, 10:41:28 AM
I may be talking through my hat here, but I thought I'd read something that indicated Unity had an API method for returning the native resolutions supported by a display. I don't know if that API exists, or if it works correctly on Macs or not, but if it does, I wonder if it might be possible for RimWorld itself to query that information and then change to a/the natively supported resolution immediately before attempting the switch to fullscreen? Could that possibly address this issue without a Unity patch?
Quote from: asciiface on October 07, 2014, 01:44:22 PM
that is one solution I had seen on other bug report forums, automagically correcting the resolution.
If I know anything about development and systems tho, (and I know quite a lot, not to toot my own horn more than it is worth), unless implemented with some thought and care could cause more harm than good.
Quote from: Mystic on October 07, 2014, 10:41:28 AM
I may be talking through my hat here, but I thought I'd read something that indicated Unity had an API method for returning the native resolutions supported by a display. I don't know if that API exists, or if it works correctly on Macs or not, but if it does, I wonder if it might be possible for RimWorld itself to query that information and then change to a/the natively supported resolution immediately before attempting the switch to fullscreen? Could that possibly address this issue without a Unity patch?
I suppose the same could be said for most software development, of course ... anything implemented without thought and care is asking for trouble. :) I'm sure Tynan would give it the thought required beforehand. At least it would be worth trying, because I suspect that waiting for a fix from the Unity developers might be a long, long wait (based upon things I've read elsewhere).
You're in the software development business too, then? As am I (for over three decades now). From what I am seeing, there's no shortage of technical know-how in the RimWorld user community ... it must be the type of game that appeals to other developers.
Mac-using developers at that... ;)
I am not a professional developer but I know a fair bit about programming and am doing it as a hobby. (Nothing publicly released to show for it, though.)
Quote from: Mystic on October 07, 2014, 10:41:28 AM
I may be talking through my hat here, but I thought I'd read something that indicated Unity had an API method for returning the native resolutions supported by a display. I don't know if that API exists, or if it works correctly on Macs or not, but if it does, I wonder if it might be possible for RimWorld itself to query that information and then change to a/the natively supported resolution immediately before attempting the switch to fullscreen? Could that possibly address this issue without a Unity patch?
[/quote]
I suppose the same could be said for most software development, of course ... anything implemented without thought and care is asking for trouble. :) I'm sure Tynan would give it the thought required beforehand. At least it would be worth trying, because I suspect that waiting for a fix from the Unity developers might be a long, long wait (based upon things I've read elsewhere).
You're in the software development business too, then? As am I (for over three decades now). From what I am seeing, there's no shortage of technical know-how in the RimWorld user community ... it must be the type of game that appeals to other developers.
[/quote]
TechOps technically (devops+sysadmin). I am more of a systems/linux guy, but I do write a lot of tooling! I think it is the style of game that attracts, in the same way as RTS's and similar.
Quote from: stefanstr on October 07, 2014, 02:56:16 PM
Mac-using developers at that... ;)
I am not a professional developer but I know a fair bit about programming and am doing it as a hobby. (Nothing publicly released to show for it, though.)
I started using mac for work because of the native command line and compilation capability. I primarily work with Linux so it made sense to have a native interface (WINE and puttySSH can ***k a ***k), in the end I just ended up enjoying it more and tend to sacrifice playing some games I really want to play to help support the mac gaming community by being involved in testing + bug hunts.
I realize that the issue is moving into a possible Unity bug, but I just wanted to post that I was experiencing the same issue as well. Black screen, can hear the audio and see the cursor but nothing else. Switching to windowed mode works fine. Currently running a 2009 15" MBPro, 3.06GHz Core 2 Duo, 4GB RAM, NVIDIA GeForce 9400M 256 MB running 10.9.5. I'm running the latest Alpha Build.
It looks like Rimworld isn't the only game suffering from this problem.
http://forum.unity3d.com/threads/black-screen-after-game-start-on-mac-os.224820/ (http://forum.unity3d.com/threads/black-screen-after-game-start-on-mac-os.224820/)
Apparently, starting the game in full screen on a Mac in a non-native resolution can cause the black screen for some mac users. It looks like the bug may have been fixed in Unity 4.5.4.
From the log files I saw earlier, it looks like Rimworld was still using 4.5.3 which is where other people were having the problem too.
I hope this helps. :)
- Eck
Quote from: Eck on October 20, 2014, 05:03:08 PM
It looks like Rimworld isn't the only game suffering from this problem.
http://forum.unity3d.com/threads/black-screen-after-game-start-on-mac-os.224820/ (http://forum.unity3d.com/threads/black-screen-after-game-start-on-mac-os.224820/)
Apparently, starting the game in full screen on a Mac in a non-native resolution can cause the black screen for some mac users. It looks like the bug may have been fixed in Unity 4.5.4.
From the log files I saw earlier, it looks like Rimworld was still using 4.5.3 which is where other people were having the problem too.
I hope this helps. :)
- Eck
Yeah, that looks very, very promising ... great find. It would be nice to hear whether Tynan has any thought of moving up to Unity 4.5.4, either for a patch release or (at least) for Alpha 8.
In the mean time, you can probably get the game to run by running it in windowed mode. Or if you are able to specify the resolution of Rimworld in the config files, set it to your native screen resolution and that might do the trick.
- Eck
Quote from: Eck on October 20, 2014, 06:19:22 PM
In the mean time, you can probably get the game to run by running it in windowed mode. Or if you are able to specify the resolution of Rimworld in the config files, set it to your native screen resolution and that might do the trick.
Yes, I've been running Alpha 7 in windowed mode for now. As detailed earlier in this thread, I can also run Alpha 7 in fullscreen mode as long as I go back to Alpha 6 to actually set the fullscreen mode in the first place ... that way Alpha 7 sees the full native window resolution in fullscreen mode at startup and sidesteps the problem. But it's a pain to do that, so for now I'm just going with windowed mode.
Also as seen earlier in this thread, a good deal of effort was put into trying to update config files, without success, unfortunately. Read back through the thread to see much more detail on those efforts.
I'm just glad to hear it is a Unity bug that has been fixed, and now am hoping to hear that RimWorld will be capitalizing on that fix soon.
Based on Tynan's change log from today, it looks like this issue will most likely be resolved with the next alpha:
Quote
I'm getting a similar error; instead of the blank start-up screen, whenever I try to load my colony I get a wierd color-distorted loading screen, but I can still hear the sounds of the game I'm just stuck in the loading screen. Game version is Alpha 8f unmodded and I created my colony in the same version, also always playing in windowed mode. I'm playing on a macbook pro OSX Yosemite v10.10. Here's my Unity player.log https://www.dropbox.com/s/wuy41uqfdv3iffl/Player.log?dl=0 (https://www.dropbox.com/s/wuy41uqfdv3iffl/Player.log?dl=0)
Quote from: beast on January 20, 2015, 12:41:31 PM
I'm getting a similar error; instead of the blank start-up screen, whenever I try to load my colony I get a wierd color-distorted loading screen, but I can still hear the sounds of the game I'm just stuck in the loading screen. Game version is Alpha 8f unmodded and I created my colony in the same version, also always playing in windowed mode. I'm playing on a macbook pro OSX Yosemite v10.10. Here's my Unity player.log https://www.dropbox.com/s/wuy41uqfdv3iffl/Player.log?dl=0 (https://www.dropbox.com/s/wuy41uqfdv3iffl/Player.log?dl=0)
You're not playing unmodded. The log says, "<li Class="battlestations.newSelectorThing">", which is not a class from the main game.
Quote from: Tynan on January 20, 2015, 01:44:36 PMYou're not playing unmodded. The log says, "<li Class="battlestations.newSelectorThing">", which is not a class from the main game.
Hmmm, I removed that mod from my rimworld mods folder quite some time ago, could that be why the game is starting to glitch? I also have removed all mods loaded in the "mods" menu.
EDIT: Nevermind, creating a new colony without any mods works okay, removing that mod a while ago must've corrupted the save.
I think the problem originally described in this topic has been solved with Alpha 8. I am not running into any problems at least.