Thanks for checking. A minidump won't help us here, only an apitrace would have been useful, had that worked.

One more thing to try, I guess: does it get any further with dxvk 2.4?

Thanks for checking. A minidump won't help us here, only an apitrace would have been useful, had that worked.

One more thing to try, I guess: does it get any further with dxvk 2.4?

Nope, doesn't get any further on 2.3 either, I will try to do an apitrace though, but I'm not sure if it will provide anything.

The Sims 2 Content Manager.trace.zip
Here's the trace for the Content Manager. :)

The Sims 2 Content Manager.trace.zip Here's the trace for the Content Manager. :)

Thank you. It has indeed captured something, however no D3DERR_INVALIDCALL errors to speak of, so it's still unclear why the crash happens. That being said, the things in the trace are somewhat nonsensical, and it appears to create textures, query them, and then not even release them fully? Perhaps it's simply running out of memory.

I assume both these utilities work on modern Windows? If so, it would be useful to capture an apitrace of that behavior, to see at least what the application expects to be proper in such cases, if there even is such a thing.

The Sims 2 Content Manager.trace.zip Here's the trace for the Content Manager. :)

Thank you. It has indeed captured something, however no D3DERR_INVALIDCALL errors to speak of, so it's still unclear why the crash happens. That being said, the things in the trace are somewhat nonsensical, and it appears to create textures, query them, and then not even release them fully? Perhaps it's simply running out of memory.

I assume both these utilities work on modern Windows?

They do, yes. :)
Here's also the HomeCrafter Plus trace too in case anything differs.
TS2HomeCrafterPlus.trace.zip

Here's also the HomeCrafter Plus trace too in case anything differs. TS2HomeCrafterPlus.trace.zip

Appears to be mostly identical to the other one. No errors here either, just nonsensical behavior.

Here's also the HomeCrafter Plus trace too in case anything differs. TS2HomeCrafterPlus.trace.zip

Appears to be mostly identical to the other one. No errors here either, just nonsensical behavior.

Content Manager loads almost instantly and works fine on Windows, I think HomeCrafter Plus has some issues on modern Windows though, it was working for me at one point however. Since both apps appear to have the same issue, I’ll try and see if I’m able to do an apitrace of Content Manager.

(NVM, HomeCrafter Plus is working it just took long time to load lol)

I’ll try and see if I’m able to do an apitrace of Content Manager.

If you can capture a trace of whichever is working on Windows, that would be fine and much appreciated.

I’ll try and see if I’m able to do an apitrace of Content Manager.

If you can capture a trace of whichever is working on Windows, that would be fine and much appreciated.

I got the Content Manager trace from windows. :)
The Sims 2 Content Manager(Windows).zip

I got the Content Manager trace from windows. :) The Sims 2 Content Manager(Windows).zip

Thank you. This trace looks vastly different and... sane. I'll have to figure out what's causing it to diverge so wildly with dxvk/WineD3D, which may take a while, but I have all that I need now.

While I haven't worked with apitraces before, I have noticed that right off the bat from line 8 it differs a bit:

Windows:

• 8 Direct3DCreate9(SDKVersion = 32) = 0x5340260
• 9 IDirect3D9::GetAdapterCount(this = 0x5340260) = 1
• 10 IDirect3D9::GetAdapterMonitor(this = 0x5340260, Adapter = D3DADAPTER_DEFAULT) = 0x10001
• 12 IDirect3D9::GetAdapterIdentifier(this = 0x5340260, Adapter = D3DADAPTER_DEFAULT, Flags = 0, pIdentifier = &{Driver = "igdumdim32.dll", Description = "Intel(R) HD Graphics 4000", DeviceName = "\\.\DISPLAY1", DriverVersion = {QuadPart = 2814827077177490}, VendorId = 32902, DeviceId = 358, SubSysId = 3234927693, Revision = 9, DeviceIdentifier = uuid(d7b78e66-4226-11cf-6f67-dbe0b4c2c735), WHQLLevel = 0}) = D3D_OK
• 13 IDirect3D9::GetAdapterCount(this = 0x5340260) = 1
• 14 IDirect3D9::GetAdapterMonitor(this = 0x5340260, Adapter = D3DADAPTER_DEFAULT) = 0x10001
• 15 IDirect3D9::Release(this = 0x5340260) = 0
• 16 Direct3DCreate9Ex(SDKVersion = 32, ppD3D = &0x5340260) = D3D_OK

Linux:

• 8 Direct3DCreate9(SDKVersion = 32) = 0x1d63e0
• 9 IDirect3D9::GetAdapterCount(this = 0x1d63e0) = 1
• 10 IDirect3D9::GetAdapterIdentifier(this = 0x1d63e0, Adapter = D3DADAPTER_DEFAULT, Flags = 0, pIdentifier = &{Driver = "aticfx32.dll", Description = "AMD Custom GPU 0405 (RADV VANGOGH)", DeviceName = "\\.\DISPLAY1", DriverVersion = {QuadPart = 9223372036854775807}, VendorId = 4098, DeviceId = 5695, SubSysId = 0, Revision = 0, DeviceIdentifier = uuid(00000000-0004-0000-0000-000000000000), WHQLLevel = 0}) = D3D_OK
• 11 IDirect3D9::GetAdapterDisplayMode(this = 0x1d63e0, Adapter = D3DADAPTER_DEFAULT, pMode = &{Width = 1280, Height = 800, RefreshRate = 60, Format = D3DFMT_X8R8G8B8}) = D3D_OK
• 13 IDirect3D9::Release(this = 0x1d63e0) = 0

Everything matches up until line 8 where the second Create9 function is and Linux instead does GetAdaptorDisplayMode? that doesn't happen on Windows until line 89.

It's also missing an additional GetAdaptorCount, and two GetAdaptorMonitor lines are missing from Windows. Linux is also missing the Create9Ex function entirely?

I'll have a quick look at Body Shop as that works on Linux, and see if it differs at all.

So Linux does the exact same thing on Body Shop, yet it's opening just fine there?
TS2BodyShop.1.zip

While I haven't worked with apitraces before, I have noticed that right off the bat from line 8 it differs a bit

That is a red herring. Games (and utilities) may have different paths depending on the hardware they're using or various other factors, it's nothing unusual.

The notable diverging point follows a call to IDirect3DDevice9::GetAvailableTextureMem which queries the total available video memory. We already have a memory limit in place here for The Sims 2, since it doesn't appear to work correctly without one. Extending this to the tools you've mentioned should fix things.

@Blisto91 is on the case and we should soon have a PR to fix them.