1.04b unhandled exception at startup

[Calis17]

Hello Tech-Team,

I have posted an issue a couple of weeks before with the 1.03b patch and haven't received any final resolution to the problem. The post can be found here:

tm.asp?m=2429553

I have not pressed the issue further because I figured a public 1.03 would be coming out soon and it did. However I just tried installing the patch (and the 1.04b as well) today.

Unfortunately Distant World does not seem to agree with my computer at all...here are the issues (I posted a Dxdiag on my previous post btw, to which I never got an answer...the system hasn't changed):

Patch 1.03 the issue with the autosaving has not been resolved and new games (and saves) still quit with an unhandled exception in that regard. Detailed description of that bug can be found in the linked post above. Afterwards I installed 1.04b.

Patch 1.04b is a real beauty. I couldnt be bothered to type it all up, but it was a bunch. Therefore I made a screenshot (see attached file).

I would love to play the game again, since I havent been able to in the past weeks. Your help yould be appreciated.

Cheers,

Calis

[Erik Rutins]

Hi Calis,

Sorry, we must have missed your earlier report.

Could you also post a DxDiag for us please?

Regards,

- Erik

[elliotg]

Hi Calis

Can you please try cleaning out your windows temporary files (C:\Users\[my user]\AppData\Local\Temp) and see if that makes a difference?

Thanks Elliot

[Calis17]

Hello Elliotg and Erik,

I cleaned out my temp files as suggested...sadly it didnt change anything for the game, but freed up quite a bit of disk space. Thanks for the suggestion though

I ran the dxdiag again in 32 and 64 bit. See attached txt file for reference.

I am looking forward to your reply.

Cheers,

Calis

[Calis17]

Since I can only post one file per post here is also the 64-bit version as attachment.

Cheers,

Calis

[Calis17]

More than a week has passed and I still got no answer. Please excuse me for being frank. I did not buy a game which I cannot get to work and constantly being ignored by the tech support only because the easy fixes dont work. Hello anyone home???

I would really appreaciate it, if someone from the tech team could put in some effort to resolve this issue!

[Erik Rutins]

Calis,

Did you try the official 1.0.4 update we released yesterday yet?

Regards,

- Erik

[Calis17]

Yes I did, same issue.

[Erik Rutins]

I've asked Elliot to check in on this issue again as I'm really not sure where to go from here. I don't see any real problems, but it is definitely a system specific issue.

[elliotg]

Hi Calis

Sorry we missed you somehow before.

This problem you are encountering is caused by an old version of Distant Worlds on your system. When Distant Worlds runs, it is trying to use some components from a previous installation of DW. Not sure why or how, but that causes the specific error you are seeing.

I think that the old installation of DW is being cached somewhere on your system by Windows. I would suggest completely uninstalling Distant Worlds (all versions, if multiple versions exist), and then reinstall the latest version. You might need to search your hard drive for DistantWorlds.exe to see if an old version is lurking somewhere...

Also, be sure to clear out the file "defaultOptions" in the following folder: C:\Users\[YourUserName]\AppData\Roaming\Code Force Limited\Distant Worlds\1.0.4.5\

Let me know how you get on.

Thanks Elliot

[Calis17]

Thanks a lot Elliot,

after deinstalling and cleaning the system from any leftovers I did a new download of the game, patch etc. Now it works fine.

Thanks for your support!

Cheers,

Calis

[Pipewrench]

Just to add to this.... I was re-organizing my HD this morning and after re-installing Distant worlds I ran into the same problem at startup. The crash happened after applying the updates.

Elliot I followed your advice and deleted all the DW information and purged the Roaming folder. It did not seem to work and the error message still haunted my startup of the game so I tried a workaround,

I had DW installed on my drive d: so I purged all the information again and restarted my computer on drive e:, installed DW and applied all the patches.The game then started. WTF?

To add to the 3 hours of frustration I just now re-installed DW back on drive d: following the same exact steps that had given me the startup error and it worked perfectly!

It is something that is conflicting with an old version but with my case if I re-install on a new HD the conflict disappears..

I am going to try and re-create this error this week and this time give you a detailed breakdown with attachments