ELK wrote on 2025-07-10, 19:17:

you can make a batch file

perhaps you right. Batch file give more features for this.

You can do it in a normal shortcut.

You just have to put "start /affinity 0x1 exename"

I put 0x1, because its hex. if you want to use any other single core, options should be 2,4,8,16,32 etc for one core.
ie, the hex is a binary number with each bit representing one core. The first 2 cores should be "0x3"

lowenz wrote on 2025-02-23, 16:26:

Forced MSAA can't work well with an HDR output (I'm testing on a HDR10 monitor) using Color Space > ARGB 8888......is there a solution or it's just inevitable (being the MSAA designed around 8888 color space)?

Up, isn't possible to use forced MSAA and ARGB2101010 (for HDR10 output)?

After the last few tests with Mech 2 mercs over the last 4 days
Things i noticed here that Been_Nath should had noticed too
-Titanium uses 3dfx glide API DLL's while the main menu uses ddraw due to its direct3d rendering option, also there are memory timeout problems with mercs titanium that i noticed where the game suddenly loses the ui and graphics glitches with a -1 memory error ingame that pop up when pressing esc but only by alt+tab you see the message for an instant when using 3dfx, directdraw/direct3d may suffer from this too.
-Every Mech2Mercs version that isnt titanium still uses Ddraw.dll as direct3d that includes even the 3dfx release and other 3d enhancement versions, something mech2.org and pcgw covered it last year https://www.pcgamingwiki.com/wiki/MechWarrior … es#cite_note-11 So it is a issue i wish dege checks out once he has free time, since it covers both the game and graphical settings like software and Direct3d.
-Under Titanium all of the rainbow UI problems mech2 3dfx has are missing from it when using 3dfx, the game works fine and dandy outside the mentioned random memory issue, Main Menu still uses ddraw.dll due to also using direct3d, and it suffers from scaling issues which aren't present on mech 2 and GBL due to said games always being locked to 640x480 windowed and mercs +titanium always forcing fullscreen window like UT'99 does, though some of the erratic menu behavior can be atributed to dxwnd i believe, but that is relegated to the main mechwarrior 2 thread at The Guide/Windows.

This what i could gather til now, the dxwnd stuff i will mention at the mech 2 thread.

In Runaway: A Twist of Fate cursor never changes with dgvoodoo, it supposed to based on context like in majority of adventure games.
Also, about track selection in TOCA 97, I think at some point everyone kinda agreed that it was supposed to look bugged like it does right now, so I decided to check how it runs natively and actually you can see track previews pretty clearly this way.

It's how it runs without any wrappers at all, only couple shims to get it running, same as CMRally has, cause it's the same engine I guess.

Just to inform that i booted up tachyon after a long time with the newest wip, plus i followed Dege's tip to increase space.exe stack to 1mb+ and now i am playing tachyon not only with reshade but also with better stability under windows 10 with CRT Aspect radio enabled.

As for Mechwarrior 3, on which i haven't reported in a while, the game suffers from ghosting cursor issues, but it isn't gamebreaking.
I haven't checked under nGlide yet to see if the bug persists there, i'll give a try later this week.

also i tested with and without reshade and the ghost cursor issue persists

Oh damn, seeing the mechlab of Mech3 after all these years.... 😁

lowenz wrote on 2025-09-23, 08:22:

Oh damn, seeing the mechlab of Mech3 after all these years.... 😁

Lemme also give you an extra after discovering today and i hope dege once he comes back from his work free time, checks out.

Battlezone 😄