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
---------