Hi.

Just installed 2.09.4-HOTFIX only to find some of my ships on fire now, with no defect tech being shown.

I tried taking them out for a ride, then exit / reload. I tried exiting the game completely, I tried teleporting to other Star Systems, calling my Freighter, rearrange tech -- all to no avail. They'll all eventually be on fire again.

The only pattern I was able to make out seems to be, that certain landing positions on my freighter will have my ships ignited after reload, while others seem to be taken care of my by lazy Vy'keen firefighter crew.


This just keeps getting better and better -- LOL.

2.09.4 really messes up mods, and puts a new DISABLE TXT IN ASWELL. PPl on Steam got hit yesturday by all this, thankfully I have my NSM set to No Auto Updates, so going ride it out, whilst mods etc get sorted/updated.

Well, at least for now, I did notice approaching ships no longer vanished in front of my nose on stations.

But then, seeing, how the ship models, which were resized to enhance the VR experience, expose all sorts of rather massive clipping (through he station itself, through the walkways, ...), maybe it wasn't that bad, that they didn't show up so frequently before.

Edit: First sentence now makes sense ...

I just wonder why in my download list there is just the 2.09.4 HOTFIX, I have never seen the main 2.09.4. Is this included? I have doubts because of the small 8MB size patch.

This we can not be sure of, since HG never released 2.09.4 to GoG, and patchnote for 2.09.4 Hotfix are just:

We have become aware of a number of mod incompatibilities causing a crash on startup with release 2.09.4. As a result, we have pushed a hotfix that will disable mods by default.

Vs 2.09.4:

[i]Bug fixes
Fixed a number of issues where technology was not being correctly detected in exosuits and starships after being moved around or between inventories. This includes being unable to recharge hazard protection.
Fixed an issue that was causing starships to vanish when landing on space stations in systems with a high number of ambient freighters.
Introduced a number of CPU and rendering optimisations for OpenVR.
Introduced better error messages when the game fails to start because of Vulkan compatibility issues.
Allowed users to choose preferred GPU on startup in cases where their discrete GPU driver requires an update but their integrated GPU driver does not.[/i]

Source: nomanssky.com

I guess we have to "look for proof of fixes" from 2.09.4 in our 2.09.4-Hotfix-game... That's ease, for sure.... Maybe one with 2 sets of GPU can confirm "preferred GPU"?

Do you mean the offline installer? The 2.09.4 patch was installable via GoG Galaxy several days ago; many of us here have been running 2.09.4 since then.

2.09.4 wasn't available to me. All I got was a direct update to the 2.09.4 HOTFIX 52147. 2.09.4 does not show up in 'Backups & Goodies' for me, and neither did it show up, when I syncronizeed my offline installers using gogorepo.py (the sync runs daily).

Reading your post, I started gogrepo.py manually right now and its downloading the full ~8.5GB of the 52147 installer.

I don't know how the regional distribution works, but being forced into using Galaxy to get more recent patches, and then seeing, that even using that, I either don't get them at all, or late or only with help of additional toosl is rather disturbing.

The offline backup installers did not get 2.09.4, I'm guessing they skipped uploading it and went straight to 2.09.4 Hotfix (which includes all 2.09.4 fixes, plus the hotfix correcting problems with 2.09.4). If I were in their shoes, and was about to release files which were later than other release methods already, and you now had fixes to it, releasing the more buggy and slightly older version would just have been a waste of time creating two lots of offline installers when you know you are about to update the first anyway.

Personally I dont have more than one fighter at the moment (started a new game when Beyond was released and taking my time doing everything the game now offers), so cant try to reproduce the issue yet.

Having other ships on fire is not something I have heard of before, have you reported it to Zendesk with a save file upload / screenshots / dxdiag ?

Sounds like something they would be very interested in fixing (unless mods are involved)

Apologies for 'quoting you short'.

I never got 2.09.4 in Galaxy, while it was available for dashiichi -- it directly went to the hotfix. That's what I was mainly referring to, but I cleverly obscured it by also talking about the offline installers :)

Edit: Clarification

Im using Galaxy Client 1.2 and went from 2.09.1 and 2.09.3, to 2.09.4.hotfix

My availeble build history attached.

I had the same update history, too. So, I downloaded the offline installs and ran them this morning and it said I had ver 2.11 now. Ok, cool...

Yepp.
Build 52149 went from Experimental to 2.11 a few hours ago. For steam users it occured 6 hours ago.
So public branch in Galaxy Client are 2.11 and no Experimental, not even on Steam...

Problem solved with the latest fix 2.11 ...at least in my case.

Mine are still on fire with 2.09.11.