pls give info on update


I believe they said that the 1.0.2.7 manual hotpatch they released on Saturday would be coming out today. I'm curious if there will be anything beyond what was just in that hotpatch though.


In Tech Support they said there is a 1.0.2.8 patch that we should get ...

His gpu supports dx 11.1 not the newest dx 11.3 feature set. Afaik unless the gpu fully supports the 11.3 feature set it will have random issues in a modern dx11 based game using an up to date dx11 sdk.


Ah, is that my issue, older DX11? I didn't know there were subdivisions to it.

Also I ...

Ah, understood - two cards working in tandem. Does the HD 7800 fully support DirectX 11?


His gpu supports dx 11.1 not the newest dx 11.3 feature set. Afaik unless the gpu fully supports the 11.3 feature set it will have random issues in a modern dx11 based game using an up to date dx11 sdk ...

Please can you come back to the forums @Erik, us users need to know you are still looking into these critical issues. I cannot play the game more than a few minutes right now and it has been like this since day 1. I have never before encountered a persistent bug like this triggered in exactly ...

Tkins wrote: Thu Mar 24, 2022 2:44 pm I'm also pretty disappointed that this crash doesn't seem to be getting any attention.

At first Erik was here talking with us all, but now he isn't around much and I have no idea the status of this bug or others....

Sad to report that 1.0.2.3 and 1.0.2.4 do exactly the same thing. Upon projectile impact the display driver stops responding and needs to recover, resulting in CTD. Both the logs are still gone, and Event Viewer no longer gives specific information. This crash is making me want to refund the game ...

Still a thing in 1.0.2.2? I have discovered it is not the zoom that does it per say, but when the projectiles hit. The moment you observe a projectile impact another ship is when the driver shits the bed.

This looks very much like my crashes when battles occur and projectiles hit, can you confirm this? Does it still happen on 1.0.2.2?

I will have to examine this as a test, thank you.

Please tell us if this happens on 1.0.2.2

Do you still experience this issue on 1.0.2.2? We must all speak up

Do any of you gentleman and/or ladies have still have this issue? We were discussing this as of 1.0.1.6 and it is still happening on 1.0.2.2. We must speak up to get this fixed.

I have received similar warnings about SharpDX Xenko Graphics etc....since day 1. However, my crashes occur when battles start and projectiles hit ships. Other than this I can be of no help except to say I have never been able to play for more than a few minutes, and it is something about AMD ...

Once again I have tried the latest build, 1.0.2.2, and sadly I must report that this issue still occurs. I noticed you changed the HDR so it was not default, and I kept that off to see if it made a difference, sadly it did not. I did notice a large performance increase elsewhere though, particularly ...

Still happening on 1.0.2.1. I will try a new game and see what happens but I am doubtful....

Ok so I tried a brand new game made on 1.0.2.1 and the very first combat I try and observe (between two, rival pirate factions at the planetary system next to homeworld) the game immediately CTDs. There is ...

...annnnnd now 1.0.2.0 doesn't even let me start, let alone get to battles. Instant CTD following the splash screen. Event Viewer's warning is far larger and longer now. Whatever this update did SharpDX Xenko Graphics stuff is now messed up worse...

Application: DistantWorlds2.exe
Framework Version ...

wolfclan wrote: Wed Mar 16, 2022 3:14 pm Seems to be working with 1.0.2.0. I won't be able to try a full game for a while, but for the first couple of minutes, it is working as would be expected.

Strange...1.0.2.0 is what seems to have given me startup CTDs...

I'm getting instant CTDs on startup now whereas before I had battle CTDs...

So I have now tested 1.0.1.9 and I can say this:

Shift ~ works for bringing up system info
The resolution error on startup is fixed, thank you
However the battle crashes still occur

What is different now is that what can be best described as a giant visual artifact now appears on screen directly ...

We were planning to release a new 1.0.2.0 update today which hopefully will resolve the battle crashes (and another try at the black screens) but unfortunately we just discovered a critical new issue with that update, which means it will have to wait until tomorrow while we work on it a bit more ...