Tacoma
Screen turning black on menu
For some reason when I try and play the game the screen turns black on the menu and I can't play it. Any fix for this?
< >
Showing 1-11 of 11 comments
brett_douville Aug 3, 2017 @ 5:59am 
Can you describe your computer further? Operating system, graphics card, etc? Furthermore, could you look in <Steam directory>\SteamApps\Common\Tacoma\Tacoma_Data and send us the output_log.txt file you find there to support@fullbrig.ht?

There's a chance your graphics card drivers are out of date. If so, could you see whether updating them fixes the problem?
QuantumShoulder Aug 3, 2017 @ 6:08am 
operating system is windows 10 pro. Processor is intel cor i5-6400. Grapics card is geforce gtx 1050ti, 8gb ram I also just updated my graphics driver and reinstalled it. I tried a few other games also to see if it was an issue on my end. I just emailed th output log also :)
tomlachlan Aug 5, 2017 @ 8:39am 
Hey, having the same problem here. Running Windows 10. The game ran fine the first couple of times I loaded it, Windows updated itself to the Creator Edition and now I get the intro spash screens fine but then just a black screen and the ambient noise playing over what should be the menu. Any help? All drivers are up to date.
Last edited by tomlachlan; Aug 5, 2017 @ 8:40am
brett_douville Aug 6, 2017 @ 7:22am 
Could one or both of you send the output_log.txt found in <SteamDir>\SteamApps\Common\Tacoma\Tacoma_Data to support@fullbrig.ht? Thanks.
tomlachlan Aug 6, 2017 @ 10:54am 
Thanks Brett, I've sent the log over to the address mentioned in your first post.
Last edited by tomlachlan; Aug 6, 2017 @ 11:02am
Vorkuta Sep 19, 2017 @ 9:07am 
@brett_douville I had a look at the logs after the game was initialised and there were around 100 entried along the lines of what I have posted below. Could this be due to a broken save file? When I quit the game before I did a save and exit to desktop (not save and exit to menu). Maybe that has something to do with it. I also had a look at the save file json and it all seems to be blank! Just a lot of newline characters. So potentially this is something to do that.

The last thing I can think is that the save file is located on my C: drive and the game data is all on another drive that has my games on it. My OS runs on C:, steam app data is on D:

Doing a callback of a request of type ReadComplete with filename C:/Users/storm/AppData/LocalLow/Fullbright/Tacoma/TacomaSave000.json (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51) Executing callback and removing request of ReadComplete for C:/Users/storm/AppData/LocalLow/Fullbright/Tacoma/TacomaSave000.json (ID: 3) (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51) JsonReaderException: Unexpected character encountered while parsing value: at Newtonsoft.Json.JsonTextReader.ParseValue (Char currentChar) [0x00000] in <filename unknown>:0 at Newtonsoft.Json.JsonTextReader.ReadInternal () [0x00000] in <filename unknown>:0 at Newtonsoft.Json.JsonTextReader.Read () [0x00000] in <filename unknown>:0 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.ReadForType (Newtonsoft.Json.JsonReader reader, System.Type t, Newtonsoft.Json.JsonConverter propertyConverter) [0x00000] in <filename unknown>:0 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00000] in <filename unknown>:0 at Newtonsoft.Json.JsonSerializer.DeserializeInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00000] in <filename unknown>:0 at Newtonsoft.Json.JsonSerializer.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00000] in <filename unknown>:0 at Newtonsoft.Json.JsonConvert.DeserializeObject (System.String value, System.Type type, Newtonsoft.Json.JsonSerializerSettings settings) [0x00000] in <filename unknown>:0 at Newtonsoft.Json.JsonConvert.DeserializeObject[TacLoadGameSinkData] (System.String value, Newtonsoft.Json.JsonSerializerSettings settings) [0x00000] in <filename unknown>:0 at TacSaveLoadUtils.DeSerializeAndDispatchSaveGame (System.Byte[] serializedSaveGameBytes, UInt32 earliestLoadableSaveVersion, System.Collections.Generic.Dictionary`2 saveLoadRegistry, System.Collections.Generic.Dictionary`2 saveLoadDatabase, .TacSaveGameMetaData& outMetaData) [0x00000] in <filename unknown>:0 at TacSaveLoadManager.LoadGame_ReadSaveGameCallback (UInt32 saveDataRequestID, System.Byte[] serializedSaveGameBytes, Boolean bresult) [0x00000] in <filename unknown>:0 at TacPlatformManager.CallbackAndRemoveRequest () [0x00000] in <filename unknown>:0 at TacPlatformManager_Standalone.UpdateSaveDataRequests () [0x00000] in <filename unknown>:0 at TacPlatformManager_Standalone.Update_Derived () [0x00000] in <filename unknown>:0 at TacPlatformManager_Steam.Update_Derived () [0x00000] in <filename unknown>:0 at TacPlatformManager.Update () [0x00000] in <filename unknown>:0 (Filename: Line: -1)
Vorkuta Sep 19, 2017 @ 9:15am 
@brett - update -> started a new game and saved once you enter the facility. Checked save files and all looked good. Quit to menu -> saves still intact. Quit and exit -> saves still intact.

When the game got messed up before i had been playing for 30m or so and started investigating the crew area and the work area. That's when I quit and had issues from that point on.
brett_douville Sep 22, 2017 @ 11:20am 
Ah, okay; sorry, folks, I was traveling. So, this looks like a save issue. If anyone is still having this problem, please send your save file (located usually in c:\Users\<username>\AppData\LocalLow\Fullbright\Tacoma\TacomaSaveGame0000.json) to support@fullbrig.ht. I can try and diagnose and get a fix out in a second patch.
jerhill Mar 23, 2019 @ 11:22pm 
This is an old thread, but I just had this problem show up with a new install and found a fix. Using regedit, go to Computer\HKEY_CURRENT_USER\Software\Fullbright\Tacoma and check the keys for resolution. My default was set to 15 x 768, which wasn't very useful. Reset the width to reasonable value (1200), then you should be able to start the game and use the option screen to set the actual resolution you want to use.
Sakuranohime Apr 2, 2019 @ 12:34am 
Originally posted by jerhill:
This is an old thread, but I just had this problem show up with a new install and found a fix. Using regedit, go to Computer\HKEY_CURRENT_USER\Software\Fullbright\Tacoma and check the keys for resolution. My default was set to 15 x 768, which wasn't very useful. Reset the width to reasonable value (1200), then you should be able to start the game and use the option screen to set the actual resolution you want to use.

This worked for me! Thank you so much!
Here we are in 2025. Same issue
< >
Showing 1-11 of 11 comments
Per page: 1530 50