MTM2.com

I found this online...





http://www.vogons.org/viewtopic.php?t=33134

The problem is that DXGL is a wrapper, like nGlide. It won't fix the game having stuttering issues due to too many 256x256 textures or the snow problem. It might help get the game going for ATI/AMD users but that's about it.

never had a problem with my radeon cards runing MTM2 on D3D. Only time I had problems were with that sh*tty intel GPU.

Well you're the first

If you're referring to those Intel CPUs that have the built-in graphics or w/e that say "Intel HD Graphics" on the cpu, I originally meant to buy one of those when I built my computer back in 2011..lol..but I made a mistake and bought the wrong type of board and processor..looks like it wasn't for the worst though.

Not sure if I'm the only one seeing this problem or this has already been discovered, but Beta 0.35 and Beta 0.37 seems to be causing parts of the trucks such as the tailgate and the wheels to be seen through whenever the camera is close enough to them. Switching to far away cameras such as Chase Far hides this problem, but if I were to switch to cameras such as Chase Near or any other camera that has a close range, that's when the problem becomes visible.

Yeah it has been mentioned. I'm not advanced enough to fix this as it happens on some cards and not on others.

Aww. I hope that does not mean this problem will be permanent, for me anyways.

Sadly I don't see it getting fixed within the next year. I have been having significant issues with work that I have had no time to look into the coding since December and I don't see this changing until the summer. I do hope to get this fixed at some point but at best it is probably going to be next year.

Stay away from those. Intel graphics are the worst POS available for graphics. At work I use laptops with Intel processors with integrated graphics and I can tell you, their drivers are terriblle still in 2017 (I had problems with my Intel IGPU back in 2008), it displays artifacts even in simple GUIs, let alone gaming. Drivers were somehow stable for Win7, but they still haven't fixed Win10 drivers.

So if you have budget in mind, go for a cheap radeon/geforce. Never trust those intel GPUs. I think the background overlap problem was never fixed in those cards.

28nm Laptop AMD APUs seems to be very, very faulty also. From my work experience.



Looks more like a faulty gpu driver than a code bug. What graphics card are you using?

Dual GTX 980's with SLI enabled. If I switch back to CommPatch #1, everything's pretty much fine.

I tried to reproduce your problem because my hardware is similar to yours.

My CPU: Intel Core i5-760 Lynnfield Quad-Core 2.8 GHz Socket 1156, (BUT mine doesn't have any "integrated" Intel HD graphics)
My Video Card: GeForce GTX 970 (I don't run SLI though)

The only bugs I ever saw in the betas were/are the ones Fila mentions(ed) as known bugs and things like that, but that's just me..I tried to reproduce here's a pic of mine.

But there is one more thing..Possibly..like Kmaster said, the driver version of the gpu, just curious. I use version 376.53 driver version of Nvidia driver for my Geforce GTX, maybe you could try that version if you don't use it? See if it helps any?

edit: oh by the way, this picture was taken from the latest beta: 0.37

Just updated driver to 378.92, still doing the same thing.

What overlay is that? Turn it off and try again.

Also, absolutely disable the xbox DVR overlay, it robs performance from all games, and causes glitches.

It's some NVIDIA setting that allows you to video or take photos during gameplay, but that doesn't really affect anything, nor will turning it off solve this problem.

Also, about the Xbox DVR overlay. I'm using Windows 7, not 10.

Shadowplay? And if you added mtm2 to geforce experience, remove it in case it changed to whatever it thinks is the optimized settings. nVidia hasn't support DirectX 5 since I believe 2007 when 1 through 8 were dropped from support.

Also, try turning off SLI, and turning off Threaded Optimization

Not really Shadowplay as far as I know, It's a simple share setting from the GeForce Experience general settings. (and yes it is turned off)

Also, I did turn off SLI and Threaded Optimization like you said, same result unfortunately.

Lastly, I haven't added MTM2 to GeForce Experience, the only games on there are more modern games that are still being supported by NVIDIA.

It's kinda funny you guys mention on this page.. (about the artifacting).. things like faulty gpu driver, shadowplay, geforce experience, etc, because I'm the one that previously posted the picture of Bigfoot with a perfectly working game, but today I needed to download Shadowplay so I could record my desktop for a tutorial for Draz so I could show him how to friggin install HBC tomorrow, if he hasn't already done so...(I couldn't think of another program to record desktop in windows 10, but googled it and apparently shadowplay will record desktop, but anyway), after it updated my driver version, my game 0.37 was artifacting; it hadn't done that before the shadowplay/driver update, I thought hmm, that's interesting. Anyway i think I messed around with the resolutions of the game, maybe switched between direct3d and 3dfx a ton of times, eventually I think I got it back to where the game used to be set up as with the graphics and all and the artifacting is gone now I believe. Yeah; I completely uninstalled the game today, deleted all the files, and reinstalled it today including the patches and betas, got artifacting that I didn't get before but now that's gone. Fixed back to the way it was before I ever deleted it.

edit: by the way, the whole uninstallation and reinstallation of the game and all that nonsense wasn't BECAUSE of the artifacting...it was because I was for the tutorial on how to show Draz how to NOT install mtm2 to c:\progra~1 ... aka c:\Program Files x86\ ....

deleted it and installed everything from scratch during the tutorial, that was the point of the tutorial was to show HOW to properly install the game & betas and pod hbc & hbc ini list & fixmore4. Draz is kinda behind the times when it comes to hbc...heh

I have noticed slight behavioral differences in the game between Comm Patch 1 and 0.37 and I really don't know how to deal with that (my programming skills are not advanced enough). I have been using the same settings to build the game in visual studio 2015 so in theory such differences should not exist but Visual Studio 2015 did upgrade itself with patches and I suspect the newer patches might have slightly changed some things. MTM2 is a very finicky game due to the deprecated DirectX and the general lack of support from the newer OSes for such an old DirectX version.

Check your compiler optimizations, you probably have to disable a few.
https://msdn.microsoft.com/en-us/library/k1ack8f1.aspx
And I have had success back in the day by disabling things like automatic array out of bounds checks and overflow checks, which when enabled causes the compiler to wrap in a lot of extra validation that slows the code down. I suspect these things aren't valid anymore lol. But still, it could be some modern optimization doesn't work right with old directX or something.