• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

acolangelo

Recruit
Jun 15, 2024
9
1
Description
macOS crash on launch (after working fine forever!) - Invalid view geometry: width is NaN / PC register does not match crashing frame


Mac


Steam

What is your game version?
Latest of game and all DLC

What DLC do you have installed?
Space Race, Green Planet, Below and Beyond, Marsvision Song Contest, Colony Design Set, Project Laika, In-Dome Buildings Pack

Please explain your issue is in as much detail as possible.
Game was working perfectly fine for…years! One day it worked in the morning and then at night, started getting a crash on launch. No macOS updates or anything in between those two attempts.

Full crash log attached with the following messages, among others:

Invalid view geometry: width is NaN

PC register does not match crashing frame


I’ve tried disabling all DLC, completely reinstalling Steam and Surviving Mars, and clearing all save files. No luck yet.

Can you replicate the issue?
Yes, trying to launch the app manually or from Steam.


File(s) attached
 

Attachments

  • MarsSteam-2024-06-14-213727.ips.zip
    6,3 KB · Views: 0
Upvote 0
@Cosmihomi , any chance we can get that info from you too please?
 
I am experiencing this same crash. M2 Max CPU. Logs attached.
I also notice that the Large Dumping Site now has a "reflective" appearance, or just shows the sky environment map through the ground.
Same thing for buildable area inside a dome.

The issue is almost certainly zero-height polygons on those models. I will fix it for you if you give me the source.
 

Attachments

  • surviving mars crash log.txt
    86,3 KB · Views: 0
I’m running macOS Sonoma 14.6.1 (23G93) on a MacBook Pro 14-inch, 2021 (MacBookPro18,4).
I am experiencing this same crash. M2 Max CPU.
So, both Apple silicon platforms, but not quite the same. I'd still like to get input from @Cosmihomi though!

If this is confined to the Mx Macs, there's probably nothing that can be done other than have someone write a mod to deal with the polygon issues you mention. I'm sure Paradox are not going to give out proprietary code - I've never seen them do that with any game. But perhaps you and/or @ChoGGi_2 can work that miracle for these users in a mod.
 
When I opened a support ticket, they told me to post here, saying that "developers and QA staff" would be here to answer questions.
How do we @ them?

Also upon review, it looks like my crash doesn't actually mention the `nan` issue. shrug.

(steam really should require devs to provide an arm64 port of any game if they want to continue to be labeled as supporting osx in the store)
 

Attachments

  • MarsSteam-20240904-21.01.14-627928e8.log
    6,4 KB · Views: 0
  • MarsSteam-20240904-21.01.14-627928e8.crash.txt
    6,4 KB · Views: 0
When I opened a support ticket, they told me to post here, saying that "developers and QA staff" would be here to answer questions.
I can only imagine that was a general reply; there has been no update to this game for over 2 years, so I think it's a fair guess to say there are no developers working on it at present! That said there's been no official announcement that it has ceased development either ...

steam really should require devs to provide an arm64 port of any game if they want to continue to be labeled as supporting osx in the store
No Paradox game except Victoria3 has a native Mx version out, and I frankly doubt any older game will ever do so.

That being the case we are reliant on Apple's Rosetta emulation for the graphics, so all we can really say is to keep your MacOS version up to date, hoping a Rosetta update will address these issues - that is on the assumption that it only happens on Mx Macs, that is.


Available memory:
physical: 227 MB
virtual: 1448 MB
pagefile: 1220 MB
I'm not sure I trust this reading in those logs, but that seems to imply your 32gb of memory is almost all used up! If you unload all the apps you can, does that improve matters? Is your crash at load time, while playing, or what?