When playing Factorio 0.16 on Mac OS X 10.12.6:
1. Load attached game "Hotel 0.16" (I have disabled all mods, problem happens with or without mods)
2. Run directly north to the short segment of train track
3. Get locomotive out of inventory
4. Place locomotive on track
FPS (on my machine) immediately drops from 60 to 4 and game becomes unplayable.
Save game.
Load the game just saved.
Crash message that takes me to the attached log file
Placing a train kills FPS then crashes on load
Placing a train kills FPS then crashes on load
- Attachments
-
- Hotel 0.16.zip
- Saved file
- (4.86 MiB) Downloaded 90 times
-
- factorio-current.log
- crash when loading Hotel 0.16.1
- (30.05 KiB) Downloaded 102 times
Re: Placing a train kills FPS then crashes on load
Your settings require more VRAM than you actually have, change to: [Graphics quality: normal]. The preset is unexpected imo, so will not close the report.Dedicated video memory size 1536 MB
0.205 Graphics settings preset: high
0.205 Graphics options: [Graphics quality: high] [Video memory usage: all]
Re: Placing a train kills FPS then crashes on load
Thanks for the report however I can't reproduce what you're saying. When I place the locomotive absolutely nothing happens.
If you want to get ahold of me I'm almost always on Discord.
Re: Placing a train kills FPS then crashes on load
@kevmurray: Loewchen is correct. Your computer is not good enough to run the game on your current graphics settings. You might be able to make High Graphics Quality work by reducing Video memory usage to High or Medium, enable Low quality sprite rotations and enable Low VRAM Mode.
graphics-quality=normal, video-memory-usage=all (when computer has at least 1.5GB VRAM and 4.5GB RAM)
Very-high:
graphics-quality=high, video-memory-usage=high (when computer has at least 3GB VRAM and 8GB RAM)
Extreme:
graphics-quality=high, video-memory-usage=all (when computer has at least 4GB VRAM and 12GB RAM)
I am open to suggestions to rename them just Medium should be graphics-quality=normal and video-memory-usage=high
High preset is:Loewchen wrote:Your settings require more VRAM than you actually have, change to: [Graphics quality: normal]. The preset is unexpected imo, so will not close the report.Dedicated video memory size 1536 MB
0.205 Graphics settings preset: high
0.205 Graphics options: [Graphics quality: high] [Video memory usage: all]
graphics-quality=normal, video-memory-usage=all (when computer has at least 1.5GB VRAM and 4.5GB RAM)
Very-high:
graphics-quality=high, video-memory-usage=high (when computer has at least 3GB VRAM and 8GB RAM)
Extreme:
graphics-quality=high, video-memory-usage=all (when computer has at least 4GB VRAM and 12GB RAM)
I am open to suggestions to rename them just Medium should be graphics-quality=normal and video-memory-usage=high
Re: Placing a train kills FPS then crashes on load
The name is fine, I assumed that the current settings were the preset and it would only be announced in the log if it had not been altered manually.
Re: Placing a train kills FPS then crashes on load
Thanks! Problem fixed. Please close the report unless you want to tinker with the presets.
I don't see a "Graphics Quality" in the GUI, so I set "Video memory usage" to Medium (instead of All) and "Sprite resolution" to Normal (instead of High) and re-tested - everything worked fine, still at 60 FPS.
I don't understand how come my computer isn't fast enough. It's state-of-the-art ... 5 years ago, which only makes it about 180 yrs old in computer years (joke )
I guess what took me by surprise is how it went from 60 FPS to 4 FPS then crash just by placing a train, a slower degradation would have clued me in to a performance issue. I don't know if this means I was right on the edge and that one sprite was the straw that broke the camel's back, or whether locomotive processing is as expensive as a small starter setup. Under 0.15 I was running a pretty large base, launching a rocket every 3 minutes with 15-20 trains running all at 60 FPS. I don't remember changing any of the graphics settings under 0.15 or 0.16, but I probably did (it's not the sort of thing that sticks in my mind).
Thanks for the great game guys - as a 50-something mechanical engineer, there aren't many games that I find more interesting than my grandkids these days, but I've put more hours into Factorio than any other game I've played in the last 20 years! Sláinte!
I don't see a "Graphics Quality" in the GUI, so I set "Video memory usage" to Medium (instead of All) and "Sprite resolution" to Normal (instead of High) and re-tested - everything worked fine, still at 60 FPS.
I don't understand how come my computer isn't fast enough. It's state-of-the-art ... 5 years ago, which only makes it about 180 yrs old in computer years (joke )
I guess what took me by surprise is how it went from 60 FPS to 4 FPS then crash just by placing a train, a slower degradation would have clued me in to a performance issue. I don't know if this means I was right on the edge and that one sprite was the straw that broke the camel's back, or whether locomotive processing is as expensive as a small starter setup. Under 0.15 I was running a pretty large base, launching a rocket every 3 minutes with 15-20 trains running all at 60 FPS. I don't remember changing any of the graphics settings under 0.15 or 0.16, but I probably did (it's not the sort of thing that sticks in my mind).
Thanks for the great game guys - as a 50-something mechanical engineer, there aren't many games that I find more interesting than my grandkids these days, but I've put more hours into Factorio than any other game I've played in the last 20 years! Sláinte!
Re: Placing a train kills FPS then crashes on load
Ah, I forgot we changed "Graphics quality" to "Sprite resolution" in the GUI, sorry for confusion.
Mistake we made was to introduce "High Sprite resolution" setting when just about one third of sprites was converted to high-resolution, without creating dummy textures to allocate VRAM budget for future high-resolution sprites. People tried the high resolution setting, found out it worked for them and now have issues when updating to 0.16, which has lot more high-res sprites.
Thanks for playing our game. I am glad you like it
I think it was the straw that broke the camel's back, even though locomotive is composed of 4 sprites (undercarriage - rendered twice, locomotive, color mask and shadow), so it might not qualify for "a straw".kevmurray wrote:I guess what took me by surprise is how it went from 60 FPS to 4 FPS then crash just by placing a train, a slower degradation would have clued me in to a performance issue. I don't know if this means I was right on the edge and that one sprite was the straw that broke the camel's back, or whether locomotive processing is as expensive as a small starter setup. Under 0.15 I was running a pretty large base, launching a rocket every 3 minutes with 15-20 trains running all at 60 FPS. I don't remember changing any of the graphics settings under 0.15 or 0.16, but I probably did (it's not the sort of thing that sticks in my mind).
Mistake we made was to introduce "High Sprite resolution" setting when just about one third of sprites was converted to high-resolution, without creating dummy textures to allocate VRAM budget for future high-resolution sprites. People tried the high resolution setting, found out it worked for them and now have issues when updating to 0.16, which has lot more high-res sprites.
Thanks for playing our game. I am glad you like it