Forums » Bugs
1.8.84 Back to not starting
I've updated to 1.8.84 and now the game won't load.
I'm running linux (ubuntu) with an Intel GMA 945 chipset. It gets into the loading screen, starts loading resources up to 100% and then crashes.
I checked my config.ini file, and everything as it was before (basically, everything is set to 0). No good.
It was doing this when I first tried to install the game back at version 1.8.78( or something like that) and I had to turn off the config.ini settings to get it into the game.
*EDIT:
So, I also tried erasing the config.ini file to check that. Doesn't even start loading textures then. It only occurs when the loading gets to 100%, then it crashes out.
I'm wondering if the new roid textures are making calls that ought to be disabled by setting doshaders=0. When I was first having problems, I had to set this manually along with all the other options to 0 to get the game to load. Since the Intel chipset is so craptacular, is there a new texture setting that is getting called that should not?
I'm running linux (ubuntu) with an Intel GMA 945 chipset. It gets into the loading screen, starts loading resources up to 100% and then crashes.
I checked my config.ini file, and everything as it was before (basically, everything is set to 0). No good.
It was doing this when I first tried to install the game back at version 1.8.78( or something like that) and I had to turn off the config.ini settings to get it into the game.
*EDIT:
So, I also tried erasing the config.ini file to check that. Doesn't even start loading textures then. It only occurs when the loading gets to 100%, then it crashes out.
I'm wondering if the new roid textures are making calls that ought to be disabled by setting doshaders=0. When I was first having problems, I had to set this manually along with all the other options to 0 to get the game to load. Since the Intel chipset is so craptacular, is there a new texture setting that is getting called that should not?
Ok, I'll see what I can do.
Ray, if you want me to test patches, let me know.
Ok, i just released a new patch for you to try. Update 1.8.84.2
The patch fixed it.
Yay, thanks!
Confirmed :) I went through 3 hours of debugging on 3 different PC's this morning =P. Nice to know it's fixed now, I don't really want to stay on a windows OS!