TypeError: Cannot read property 'isCustom' of null after Steam Update 1.5.5

Game Dev Tycoon bug
#1

Error Uncaught error. Please report this to support@greenheartgames.com: Uncaught TypeError: Cannot read property ‘isCustom’ of null (file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/Game%20Dev%20Tycoon/compressed/codeNw.js:429) Please restart the game.

Enabled Mods:

No mods activated.

Game Version: 1.5.5

Platform: Windows

Distribution: Steam

Received the above error after loading up fresh install of GDT. Deleted all local content including appdata folders for saved games, and reinstalled a second time. Verified cache, but still getting same error. I noticed people were getting similar errors on these forums, but the variable is different in each case that I have seen. Please Help.

#2

Do you get this error as soon as you start the game or after a certain playtime?

#3

i can say that this happens right after you choose what save game you want to play

#4

Something with your save, maybe. Try creating a new one.

#5

im getting the same except instead of ‘isCustom’ Mine says ‘id’

#6

Sorry to hear about that, can you paste the full message here please?

#7

I have been getting the same error
Cannot read property ‘id’ of null
at Object.TopicsSerializer.save (file:///C:/Steam/steamapps/common/Game%20Dev%20Tycoon/compressed/codeNw.js:1707:293)
at eval (file:///C:/Steam/steamapps/common/Game%20Dev%20Tycoon/compressed/codeNw.js:218:451)
at Array.map (native)
at a.save (file:///C:/Steam/steamapps/common/Game%20Dev%20Tycoon/compressed/codeNw.js:218:411)
at Object.b.save (file:///C:/Steam/steamapps/common/Game%20Dev%20Tycoon/compressed/codeNw.js:79:499)
at Object.b.autoSave (file:///C:/Steam/steamapps/common/Game%20Dev%20Tycoon/compressed/codeNw.js:85:198)
at Window.eval (file:///C:/Steam/steamapps/common/Game%20Dev%20Tycoon/compressed/codeNw.js:153:84)
at Window.EventEmitter.emit (events.js:92:17)
at Window.init.Window.handleEvent (window_bindings.js:148:13)
at IDWeakMap.global.__nwObjectsRegistry.handleEvent (node.js:789:26)

#8

That doesn’t work either