|
Post by AncientxFreako on Dec 14, 2014 18:04:54 GMT
Who created this patch? maybe I can help.
|
|
|
Post by tyrael on Dec 14, 2014 20:11:24 GMT
I cant remember his name but he was a member of the old mechwarrior3.org and he posted the patch there. If my memory is correct he figured out that the issue is with the 16-bit z-buffer. My understanding from his post was that in direct x there are two ways of dealing with the buffer, one that most games use and an obscure one that mech 3 and a few other games use that causes the issue. I believe that the patch wraps the direct x dll and only catches this problem causing call, reformatting some of the data and uses the other z-buffer call, fixing the problem.
|
|
|
Post by AncientxFreako on Dec 16, 2014 1:13:28 GMT
You're not talking about eop's resolution patch are you?
|
|
|
Post by tyrael on Dec 16, 2014 1:47:43 GMT
no, or at least I don't believe so. The ddraw issue happens regardless of the resolution.
As an update on Pirate's moon, I was playing around with it on my own system and have managed to get the game running quiet well, without the use of any mods (other than no cd), compatibility settings or throttling my cpu and gpu (an amd card). despite that this same graphics card and system previously showed this issue on both mech 3 and pirate's moon for some reason it seems to have stopped at least on Pirate's moon (i have the ddraw fix applied to mech 3, so I cant verify if mech 3 works properly).
If anyone wants to know, I am running the game at 1280 x 1024 resolution, using my primary graphics driver (not the software rendering)
Here are my specs: CPU: i7-3770k Ram: 16 GB GPU: Sapphire radeon hd 7870 GHZ edition GPU driver: amd's new omega driver OS: Windows 7 sp1 x64
|
|
|
Post by AncientxFreako on Dec 16, 2014 15:40:12 GMT
You're running a no cd patch for Pirate's Moon? where did you get it, I wasn't aware there was one that actually worked. I used to know of one that didn't work, though. Perhaps it didn't work with xp but does work with newer os.
|
|
|
Post by tyrael on Dec 16, 2014 16:06:57 GMT
Cant remember where I got it, but it works for me at least. But ill be happy to upload it and share a link once Im home from work tonight
|
|
|
Post by AncientxFreako on Dec 16, 2014 16:13:08 GMT
sounds good, I'll give it a try, thanks.
|
|
|
Post by tyrael on Dec 17, 2014 2:57:11 GMT
|
|
|
Post by vandervecken on Dec 18, 2014 15:54:11 GMT
So the NoCD patch definitely worked. but the graphical corruption is present. My GFX card is a Radeon HD5870.
|
|
|
Post by tyrael on Dec 19, 2014 2:21:53 GMT
What settings are you using?
|
|
|
Post by vandervecken on Dec 19, 2014 7:18:34 GMT
v 1.0.11.5, Primary display driver, 1280x1024, with 8MB textures, Shadows on, self-shading off, lighting - light maps, all other options on High.
|
|
|
Post by tyrael on Dec 19, 2014 23:34:56 GMT
Those are the same settings that I am using, maybe just a difference in the gfx driver or architecture? I used to see the issue on my card, not sure why it suddenly stopped
|
|
|
Post by AncientxFreako on Dec 20, 2014 12:36:59 GMT
why not turn on self shading? I would think that would help with the "pushing resources" theory?
|
|
|
Post by tyrael on Dec 21, 2014 3:11:49 GMT
At least for myself, I have never needed to throttle or make my system work hard to make the game playable. other than the occasional crash (which I have mostly figured out how to avoid), the worst I see is the occasional APC jumping into the air, and even then its only a few meters off the ground, and only for a second or two
|
|
bryo
New Member
Posts: 14
|
Post by bryo on Jan 4, 2015 19:29:11 GMT
Try running the latest omega drivers. The game runs without the graphical corruption which i used to get. I applied no fixes, not even the radeon fix.
|
|