Matrix Games Forums

Hello !

Yeah me again

New question... Why does some of my exploration ships do this ? And how can I fix this because leaving explo ships automated are important to me...

EDIT : Even my construction ships are trying to jump to the top left corner after building mining stations [:(]

EDIT2 : Some systems can't be explored by my exploration ships. When I try to explore these systems, they bug between this system and the top left corner of the galaxy

ORIGINAL: Z4ng3tsu67

Hello !

Yeah me again

New question... Why does some of my exploration ships do this ? And how can I fix this because leaving explo ships automated are important to me...

EDIT : Even my construction ships are trying to jump to the top left corner after building mining stations [:(]

EDIT2 : Some systems can't be explored by my exploration ships. When I try to explore these systems, they bug between this system and the top left corner of the galaxy

As far as I know the ships don't actually travel to 0,0. The vectors show that location because there is no destination when construction ships are building or waiting for supplies.
Also, if you manually give exploration ships orders I would avoid "Explore sector". I leave my science ships automated and have never had one actually move toward 0,0.

True the ships don't go 0,0.

But when automated some explo ships can't explo correctly. And I had some other bugs crashing the game. So I'm sadly going back to the original version.
I'll cross my fingers the bugs will be fixed later because I can see how much it improves the game. But I lost 30 minutes because suddenly when I try to save the game crash which didn't happen the last time I tried to save.

The last 0,0 bug I had was due to Vista x64 and the Windows API. Crazy I remembered, and more crazy I found the thread hehe.

https://www.matrixgames.com/forums/tm.a ... g&#3634251

It works ! Finally !

Yeah, I got back to the original DWU but, I hate RogerBacon and Retreat for ths, once you tasted the Bacon/Retreat/DasChrome pack...you can't go back. So much small and big improvements, it's too hard to do without them.
That's why, I tested a lot of things and I finally got a version working with Bacon/Retreat/Chrome.

The main issues I had were not being able to access saves and other files. I did two things :
- I installed DWU in the GAMES sub folder of my GOG Galaxy install (not on my system drives so I don't think it matters too much)
- I added DWU root folder and the saves folders as exception in my antivirus (can be important because antivirus can restrain sometimes access to files).

So now it's entirely working and man it's so great !

But now I'll have to learn how to deal with pirates with gravity wells (you can't jump to the ennemy in your system, and that's hard sometimes to defend ^^.

Thank you all for these mods ! See ya

New bug to report.

Again playing this incredible Bacon/Retreat/Chrome package, when I start a game with the Humans (the classic ones), after first space port built and the system is explored, even one or two mines built too, no private ships are built.
I have no idea why. Never had this with the other races. And the people on my initial colony think that 0% taxe rate is too much... Strange no ? And when I start the game, the taxe rate is 100%...
Any idea ?


EDIT : Tested on my second computer, no problem with the Humans. But on this computer I had another strange thing. Can't build Gas mining station on Gas planet. I had the option for a mining station but greyed out (of course).


Conclusion : Seems that installations of these mods add a slight random in stability and bugs. But, still worth it !

Windows is freaking out on the executable in the latest version thinking it's a virus... is this a false positive? https://imgur.com/a/TFb2L4b

ORIGINAL: BIGtrouble77

Windows is freaking out on the executable in the latest version thinking it's a virus... is this a false positive? https://imgur.com/a/TFb2L4b

Yeap ! I got the same warning but it's clean.
And if you can, set an exception in your antivirus for the game folder and the save folder. It prevented some exception for me.

For the upcoming 1.81 release I've been continuing to look at fighters and bombers. I found a bug (or feature?) in the game's original code concerning fighters. They have a myopic zone. If they are less than range 40 to their target they will not fire. This can lead to some funny situations where the fighter will fire on a bomber as it closes with it and then just follow it back to its carrier (where the fighter usually gets clobbered by AA). I've fixed that bug/feature for the next release.

In the Bacon mod fighters are meant to prioritize enemy bombers and bombers are meant to target ships. If there are no enemy bombers then fighters will go after ships. I've added code in the next release where a fighter targeting a ship will change targets if a bomber appears (such as being launched from a ship).

I've revised the custom bomber screen from 1.80 release. A level of shields will now give +100% instead of +50%. Also, a new option will be to add a tail gunner. Here isa short, rough video showing 8 fighters taking on 8 torpedo bombers with tail gunner turrets.


https://www.bitchute.com/video/ebWIM0sKtDIL/

Some limitations of tail gunner bombers:
1 They will pick a random fighter that is targeting them or another bomber in their flight. There is no way to maintain the same target from shot to shot so each time it is random.
2 They will not fire at a fighter that is returning to its carrier. That's balanced though because fighters don't try to avoid bombers when returning to their carrier. It can look a bit funny though.
3 The graphic of the shot can be a little off. A hit or miss can be determined by seeing the slight shield flash and noticing the depletion of the shield bar.

Any word on a 2004 fix?

ORIGINAL: Retreat1970

Any word on a 2004 fix?

I was going to ask the same until I realized what you were asking... read back several pages and noticed that my issue is consistent with everyone else. I really hope that my time with this mod doesn't end here, Roger has done such a wonderful job.

Roger, if you need anyone to run experimental builds or help you debug, I can certainly help on that front.

ORIGINAL: BIGtrouble77

ORIGINAL: Retreat1970

Any word on a 2004 fix?

I was going to ask the same until I realized what you were asking... read back several pages and noticed that my issue is consistent with everyone else. I really hope that my time with this mod doesn't end here, Roger has done such a wonderful job.

Roger, if you need anyone to run experimental builds or help you debug, I can certainly help on that front.

Thanks. I don't really understand why teh 2004 update breaks the mod. If you have received the update within the past 9 days I suggest rolling it back. I think that Microsoft stopped rolling out the update before that though so you've probably already had it past the 10 day cutoff period.
I hope the next Microsoft update will resolve the issue. Until then the only options (all kind of extreme) are:
1 reinstall Windows
2 Run DWU in a virtual machine. I had to do that for a year or so on my old machine. It would crash 100% of the time of saving but ONLY on saving. So I ran the whole game in a virtual machine and never saved. I would pause the game and then shut down the virtual machine. I learned a lot about virtual machines that year.

Just wondering. Playing the old way still works.

The one thing I miss most of all were the range circles. With the extended base ranges missiles could cover 30% of a system! Funny.

I'll quit asking I promise.

ORIGINAL: Retreat1970

Just wondering. Playing the old way still works.

The one thing I miss most of all were the range circles. With the extended base ranges missiles could cover 30% of a system! Funny.

I'll quit asking I promise.

Since the base game still works, maybe we can figure out what breaks the modded version. Here is a link to the 1.0 Bacon Mod. Copy over the exe and see if your computer will load it. There is very little difference between 1.0 and vanilla. Fingers crossed.

https://www.dropbox.com/s/iwev4t1bey1mm ... 0.zip?dl=0

Thanks for the upload.

Unfortunately the same issue.

P.S. I've tried so many things (reinstalls of DX and .net to name a few things)

No change for me except that the older file does not trigger my antivirus.

Roger, is it possible to have a build with debug info that dumps to the screen when an exception happens?

ORIGINAL: RogerBacon

ORIGINAL: Retreat1970

Just wondering. Playing the old way still works.

The one thing I miss most of all were the range circles. With the extended base ranges missiles could cover 30% of a system! Funny.

I'll quit asking I promise.

Since the base game still works, maybe we can figure out what breaks the modded version. Here is a link to the 1.0 Bacon Mod. Copy over the exe and see if your computer will load it. There is very little difference between 1.0 and vanilla. Fingers crossed.

https://www.dropbox.com/s/iwev4t1bey1mm ... 0.zip?dl=0

Roger...... I used version 1.0 and after the bacon mod message box appeared I went into task manager and saw the mod was doing something as a background process....... then created a dump file.

I have added the dump file in my onedrive at the following link if you want to check it

https://1drv.ms/u/s!AgNg3YuwkZJPho9AG_I ... A?e=waO2HB



The following is what I see in the dump file for the bacon mod version of distantworlds.exe
Repeated again with the bacon mod running for 10 minutes...... same result in dump file.


Roy




Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Program Files (x86)\Steam\steamapps\common\Distant Worlds Universe\Customization\distantworlds.DMP]
User Mini Dump File with Full Memory: Only application data is available

Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Debug session time: Tue Oct 6 18:53:46.000 2020 (UTC + 11:00)
System Uptime: 1 days 3:22:30.248
Process Uptime: 0 days 0:00:33.000
................................................................
..............
For analysis of this file, run !analyze -v
wow64cpu!CpupSyscallStub+0xc:
00000000`77d51cfc c3 ret
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4421

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on LAPTOP-0GLUA9ET

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 96889

Key : Analysis.Memory.CommitPeak.Mb
Value: 131

Key : Analysis.System
Value: CreateObject

Key : CLR.BuiltBy
Value: NET48REL1LAST_C

Key : CLR.Engine
Value: CLR

Key : CLR.NOSOS
Value: 1

Key : CLR.Version
Value: 4.8.4250.0

Key : Timeline.OS.Boot.DeltaSec
Value: 98550

Key : Timeline.Process.Start.DeltaSec
Value: 33

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

Key : WER.Process.Version
Value: 1.9.5.12


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD: 00004a30

PROCESS_NAME: distantworlds.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_CODE_STR: 80000003

MISSING_CLR_SYMBOL: 0

ADDITIONAL_DEBUG_TEXT: SOS.DLL is not loaded for managed code. Analysis might be incomplete

STACK_TEXT:
00000000`0009eed8 00000000`77d51856 : 00000023`77dd16ec 00007ffa`e2df0023 00000000`00000246 00000000`000a6178 : wow64cpu!CpupSyscallStub+0xc
00000000`0009eee0 00000000`77d511b9 : 00000000`0019fd24 00007ffa`e2df39b4 00000000`0009efb0 00007ffa`e2df3aaf : wow64cpu!WaitForMultipleObjects32+0x1d
00000000`0009ef90 00007ffa`e2df38c9 : 00000000`0033d000 00000000`004000c0 00000000`00000000 00000000`0009f800 : wow64cpu!BTCpuSimulate+0x9
00000000`0009efd0 00007ffa`e2df32bd : 00000000`00000000 00000000`012924a8 00000000`00000000 00000000`00000000 : wow64!RunCpuSimulation+0xd
00000000`0009f000 00007ffa`e32e3492 : 00000000`00000010 00000000`00000010 00007ffa`e3341a80 00000000`0033c000 : wow64!Wow64LdrpInitialize+0x12d
00000000`0009f2b0 00007ffa`e32d211b : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000001 : ntdll!LdrpInitializeProcess+0x1932
00000000`0009f6e0 00007ffa`e32847b3 : 00000000`00000000 00007ffa`e3210000 00000000`00000000 00000000`0033e000 : ntdll!_LdrpInitialize+0x4d94f
00000000`0009f780 00007ffa`e328475e : 00000000`0009f800 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrpInitialize+0x3b
00000000`0009f7b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe


SYMBOL_NAME: wow64cpu!CpupSyscallStub+c

MODULE_NAME: wow64cpu

IMAGE_NAME: wow64cpu.dll

STACK_COMMAND: dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s; .ecxr ; kb

FAILURE_BUCKET_ID: BREAKPOINT_NOSOS_80000003_wow64cpu.dll!CpupSyscallStub

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.19041.546

FAILURE_ID_HASH: {5d009ffa-26a5-16a1-a09c-f0690f332ad6}

Followup: MachineOwner
---------

Can someone with the 2004 patch try this and let me know waht happens:

In your Startup.ini add the lines
SCREENWIDTH 800
SCREENHEIGHT 600

See if you get a popup asking you about the size. It should say something like "Distant Worlds requires a screen resolution of at least 1024 x 768..."

No popup asking about size. Otherwise same behavior (doesn't run).

Hi Roger,

No Pop up with the same background process only