|
Post by speedyspcfan on Jun 26, 2015 0:44:02 GMT
I don't think I can contribute much at this point with what you guys are on now, but I want to say that it's really cool that all this is happening. Hopefully we'll eventually achieve full 60FPS action on Windows 7 with no glitches and widescreen/HD support in Mech3. EDIT: Well, after playing around for a bit I noticed something strange in 1600x900: no enemy damage display. Any idea what's up?
|
|
|
Post by AncientxFreako on Jun 26, 2015 5:18:58 GMT
Ok, np. Would love a screenshot of that last one
|
|
|
Post by AncientxFreako on Jun 26, 2015 5:29:08 GMT
hud.zrd (6.87 KB) There you go, one hud.zrd, a subfile of the main reader.zbd Just one thing, I'm not sure if the workbench translates the files before separating them or not, so that file might be in its original language or human readable text. It's probably in its original form, but I thought I'd mention it.
|
|
|
Post by AncientxFreako on Jun 26, 2015 5:31:07 GMT
I play mine in 1600x900 and have no problems with any damage displays. (hehe )
|
|
|
Post by teleguy on Jun 26, 2015 9:45:35 GMT
I don't think I can contribute much at this point with what you guys are on now, but I want to say that it's really cool that all this is happening. Hopefully we'll eventually achieve full 60FPS action on Windows 7 with no glitches and widescreen/HD support in Mech3. EDIT: Well, after playing around for a bit I noticed something strange in 1600x900: no enemy damage display. Any idea what's up? Yep, it's missing for me too.
|
|
|
Post by teleguy on Jun 26, 2015 9:46:43 GMT
There you go, one hud.zrd, a subfile of the main reader.zbd Just one thing, I'm not sure if the workbench translates the files before separating them or not, so that file might be in its original language or human readable text. It's probably in its original form, but I thought I'd mention it. Ok, doesn't work that way.
|
|
|
Post by teleguy on Jun 26, 2015 9:50:22 GMT
Ok, np. Would love a screenshot of that last one I'm a bit in a hurry, will post the screenshot later.
|
|
|
Post by speedyspcfan on Jun 26, 2015 13:43:43 GMT
|
|
|
Post by teleguy on Jun 26, 2015 14:59:58 GMT
Unfortunately using only the hud.zrd file doesn't work, a real bummer.
|
|
|
Post by AncientxFreako on Jun 27, 2015 16:19:51 GMT
teleguy, I was giving more thought to the issue with the speed meter and jj fuel bar; Since we observed that once I edited the coordinates in the lowest setting, 640x480, assuming the game draws from that as a default when not recognizing the new resolution for hud, it occurred to me to wonder if you changed the video res setting in the game under "options"? If you had never made that change then that would be the game's choice in a default setting, and we will have to re-think what we're going to put in for coordinates.
|
|
|
Post by teleguy on Jun 27, 2015 16:59:14 GMT
No, I didn't make any changes to the resolution settings in the ingame options menu.
I thought about the speed meter issues. Maybe the coordinates you chose are too big for the game to handle and that's why it defaults to 640x480. Can you perhaps try with coordinates that are really low?
|
|
|
Post by teleguy on Jun 27, 2015 18:10:56 GMT
Ok, np. Would love a screenshot of that last one Ok, here it is:
|
|
|
Post by AncientxFreako on Jun 27, 2015 18:32:26 GMT
No, I didn't make any changes to the resolution settings in the ingame options menu. I thought about the speed meter issues. Maybe the coordinates you chose are too big for the game to handle and that's why it defaults to 640x480. Can you perhaps try with coordinates that are really low? Meaning you never went into options at all? Ok, that explains it then. We need to test it by having you go into the options screen, choose graphics and video, then you'll see the checklist (if you're not familiar) the choices for resolutions will have 3, 640x480, 800x600, and 1024x768. Choose 1024x768 then take another screenshot and let's see if anything moves.. If you never switched it to anything then it was always at the default, which is 640x480. If it was set at 1024x768...well we'll see what it does. Another big reason for this test is that your utility might already be built into the game and you might be able to alter it in the options screen to make those choices. We will need to add entries into the .dll file, and then you'll need to put the proper links to the .dll in the .exe
|
|
|
Post by teleguy on Jun 27, 2015 21:11:58 GMT
No, I didn't make any changes to the resolution settings in the ingame options menu. I thought about the speed meter issues. Maybe the coordinates you chose are too big for the game to handle and that's why it defaults to 640x480. Can you perhaps try with coordinates that are really low? Meaning you never went into options at all? Ok, that explains it then. We need to test it by having you go into the options screen, choose graphics and video, then you'll see the checklist (if you're not familiar) the choices for resolutions will have 3, 640x480, 800x600, and 1024x768. Choose 1024x768 then take another screenshot and let's see if anything moves.. If you never switched it to anything then it was always at the default, which is 640x480. If it was set at 1024x768...well we'll see what it does. No, it doesn't work that way. The game creates a registry key called InGameVMode. Valid entries go from 00000005 to 0000000A and each value is associated with a resolution (and a certain HUD preset) stored in the game exe. What both the ingame resolution settings and my Launcher do is modify InGameVMode. So if I for instance select 1920x1080 in my Launcher, start the game and then chose 1024x768 ingame the game will overwrite the InGameVMode value set by the Launcher and the screen resolution will switch to 1024x768 and HUD V1024x768 will be used. The unmodified game contains 6 possible resolutions 640x480 800x600 1024x768 1152x864 1280x1024 1600x1200 however everything over 1024x768 was broken (pressing Esc during a mission would crash the game, I was able to fix that) so the developers only included the first 3 in options. Adding new entries to the menu would probably be extremely hard to do (for very little benefit) without messing up the offsets of every line of code that comes below that location unless we had access to the source code.
|
|
|
Post by AncientxFreako on Jun 28, 2015 3:49:06 GMT
Ok, I hear you.
Assuming you're right, then we have 3 possible "default" settings we could use for the bigger resolutions the way I used the lowest setting to fix the speedframe/jjfuel default, but we'd need to tell the user to set the in-game resolution to one of them for each related setting provided in your launcher. OR, we could just go with one, notify the user to leave the in-game option at 640x480 and just use whatever I put in that one for all of them...which means for at least two of them the speed frame and jj fuel will migrate to the middle of the screen.
The first option will be a little complicated for the user, the 2nd option will have a bit of our hud issue.
What do you think?
|
|