|
Post by AncientxFreako on Jun 28, 2015 3:52:48 GMT
btw, I recognize you're a pretty smart programmer for gleaning those from the .exe. The hud file originally had those settings as well. Do you know c#?
|
|
|
Post by AncientxFreako on Jun 28, 2015 7:06:30 GMT
So I'm going to get started on 1680x1050
|
|
|
Post by speedyspcfan on Jun 28, 2015 15:02:15 GMT
Okay, so I figured out why I'm not getting an enemy MFD on my side. For some reason the MFD is being displayed as a bunch of unintelligable garbage on my screen, which I can't capture with any software, so my apologies in advance for the potato quality video and background noise. So here's this video of me sorting between three different MFD modes and the weird glitches they cause.
|
|
|
Post by AncientxFreako on Jun 28, 2015 15:29:53 GMT
|
|
|
Post by AncientxFreako on Jun 29, 2015 19:58:00 GMT
speedy...graphics issue maybe? are you using teleguy's fix and my hud reader, or just the hud reader?
|
|
|
Post by speedyspcfan on Jun 29, 2015 21:08:20 GMT
speedy...graphics issue maybe? are you using teleguy's fix and my hud reader, or just the hud reader? No, I wasn't aware there was a fix by teleguy. My game, right now, has the MechWarrior 3 Launcher he made, a modified Mech3.exe for the widescreen resolutions, and the reader.zbd with the modified HUD stuff.
|
|
|
Post by AncientxFreako on Jun 29, 2015 22:27:58 GMT
Ok that's what I meant by his fix, the launcher. I was thinking your issue might be from using one without the other. There is an issue where the game might not recognize the new resolution and so it choses another as a default, and so far this seems to affect parts of the hud. We need to continue testing and observing in order to figure it out.
|
|
|
Post by speedyspcfan on Jun 29, 2015 22:44:40 GMT
Ok that's what I meant by his fix, the launcher. I was thinking your issue might be from using one without the other. There is an issue where the game might not recognize the new resolution and so it choses another as a default, and so far this seems to affect parts of the hud. We need to continue testing and observing in order to figure it out. I'll try and make a new install of the game (with 1.2 patch of course) and then use his launcher and the newest reader.zbd, I'll see where that takes me. EDIT: Vanilla install of the game, with the launcher and modified reader.zbd of course. Game didn't work without a widescreen modded exe. After adding that exe, same problem as before. I don't think it's my install of the game or my setup. Hm...
|
|
|
Post by AncientxFreako on Jun 30, 2015 3:31:49 GMT
and was there a version of this project that did not have the issue?
|
|
|
Post by speedyspcfan on Jun 30, 2015 3:58:47 GMT
and was there a version of this project that did not have the issue? No, I had this issue with multiple versions of the reader.zbd - I'll set up the patch on my Win8 laptop hopefully tomorrow and see if it's just my rig or if it's something with the game
|
|
|
Post by AncientxFreako on Jun 30, 2015 4:09:13 GMT
I suppose it could be graphics related?
|
|
|
Post by teleguy on Jun 30, 2015 16:35:40 GMT
I have the same problem. I looked into it and found out that the behavior of the enemy damage display changes depending on what version of reader.zbd you use. With some of the earlier ones the display is not merely missing but activating it actually crashes the game. Also I tried assigning one of the original HUDs that are included with the vanilla game to the 1600x900 resolution and the enemy display worked fine (albeit at the wrong position of course). Therefore I think it's likely caused by some error in reader.zbd / V1600x900.
|
|
|
Post by teleguy on Jun 30, 2015 16:38:11 GMT
and was there a version of this project that did not have the issue? No, I had this issue with multiple versions of the reader.zbd - I'll set up the patch on my Win8 laptop hopefully tomorrow and see if it's just my rig or if it's something with the game Can you post your hardware specs to rule that out?
|
|
|
Post by speedyspcfan on Jun 30, 2015 17:50:39 GMT
Specs:
OS: Windows 7 Pro 64-bit CPU: Intel Core i7 4770K @ 3.50GHz RAM: 8GB DDR3 @ 799MHz MOBO: Gigabyte Z97X-SLI-CF GPUs: Nvidia GeForce 770 2GB (two in SLI)
|
|
|
Post by AncientxFreako on Jun 30, 2015 20:20:07 GMT
It's possible that the reader I've been working on has gotten corrupt, but we can't discount that we're in unfamiliar waters. There are also other graphics issues that show up with the changes to the reader.zbd. Stripes on the landscapes, boot to desktop. Earlier versions of windows seemed to skip over these issues more often, as if the newer versions of windows are more sensitive and need to have the code in mech3 be perfect, which it isn't.
I could try and do it over again with a fresh install, although it was pretty tedious, and the reader I used was directly from a 1998 backup. All I can do is work in the workbench, I don't work directly with the code. So if you want to investigate deeper into the reader.zbd you'll have to do it. I suppose that editing the reader and other files in the game without the source/original dev utility would come with it's set of problems because we really don't have any kind of error checking/debugging like they probably would have had back when they were making the game.
Could the issue still lie in the .exe?
|
|