|
Post by teleguy on Jun 24, 2015 11:50:06 GMT
Ok I looked at it, cool idea. So the launch button works presently? Or is it still inactive and in planning stage? Mine said "mech3.exe could not be found" The launcher has to be in the game directory.
|
|
|
Post by AncientxFreako on Jun 24, 2015 11:52:35 GMT
Before I make any change suggestions, what is the proposed function? I assume it will give a list of choices for what resolution to play in? I think the launch button should be set inactive until a resolution is chosen. That way there will be less confusion if there's an error of some kind. If someone is using the lesser resolutions they don't need the program anyway.
|
|
|
Post by AncientxFreako on Jun 24, 2015 11:54:39 GMT
ok we're caught up now lol
|
|
|
Post by teleguy on Jun 24, 2015 11:55:09 GMT
Yes, it should give a list of available resolutions. I'll see if the button can be disabled.
|
|
|
Post by AncientxFreako on Jun 24, 2015 12:00:46 GMT
Alright, rather than placing it in the directory I think the program should do that on its own. When making a program for convenience, think the consumer knows nothing about computers. Make it as easy as possible. I would even go as far as putting a readable definition of the program right on that GUI above or below the buttons explaining that it's only for playing certain resolutions. It might be a good idea to include EOP's targeting fix install with it...assuming your added code doesn't interfere with his.
|
|
|
Post by AncientxFreako on Jun 24, 2015 12:02:13 GMT
Make sure you give yourself credit in some kind of read-me file!
|
|
|
Post by teleguy on Jun 24, 2015 13:42:54 GMT
Alright, rather than placing it in the directory I think the program should do that on its own. When making a program for convenience, think the consumer knows nothing about computers. Make it as easy as possible. I would even go as far as putting a readable definition of the program right on that GUI above or below the buttons explaining that it's only for playing certain resolutions. It might be a good idea to include EOP's targeting fix install with it...assuming your added code doesn't interfere with his. Well then either the user has to enter the install path during installation or the installer has to read the path from the registry somehow. I could find this registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\MicroProse\MechWarrior 3\1.0] "Program"="M:\\MicroProse\\MechWarrior3\\" on my system but I don't know if or where it exists on a 32 bit OS. Putting an explanation on the GUI might make things too cluttered, not sure yet. It should definitely be in the readme though. EOP's res fix is only for 1024x768, right? I'll probably replace that resolution with 1280x720. Anyway I intend to include a patch tool (in addition to a Mech3.exe with my patches already applied) so that you can (in theory) apply widescreen resolutions to any Mech3. exe you want, be it EOP's or a nocd one.
|
|
|
Post by teleguy on Jun 24, 2015 15:58:03 GMT
Setting resolutions should work now. Of course some of them haven't been added to the game yet so they will default to the original resolutions, like 1600x1200 etc.
|
|
|
Post by teleguy on Jun 24, 2015 20:38:28 GMT
Here are the screenshots. Attachments:

|
|
|
Post by AncientxFreako on Jun 24, 2015 22:28:08 GMT
EOP's fix is a little misconceived by people. It fixes an error in the mech3.exe with regards to how the screen resolution relates to the targeting triangle...something about how the triangle does not begin at an existing point on the screen maybe...He can explain it better but that is my understanding of it. I do not believe it is a patch for adding resolutions. 1024x768 already exists in the game. So, if you are using an exe with his fix applied...well I guess there's nothing to worry about since his code will be using empty spaces to begin with and by default you are looking for empty spaces and won't overwrite his code. If you did start with his .exe fix you'd be serving up a two-in-one patch., but if your installer patches the .exe without replacing it I guess it won't be incompatible...unless one of you overwrites the other. I guess what I'm saying is both fixes are highly relevant to getting the game to run well on modern OS, so for them to be compatible would be a good thing.
|
|
|
Post by AncientxFreako on Jun 24, 2015 22:31:15 GMT
And wow, those huds are way off. Looks like I've got my work cut out for me.
|
|
|
Post by AncientxFreako on Jun 24, 2015 22:38:11 GMT
Btw, the game already supports (at least in the HUD file, so I would assume the .exe as well) the following resolutions: 1600x900; 800x600; and 640x480; So, although maybe you're thinking of convenience, but you don't have to waste code on those.
|
|
|
Post by teleguy on Jun 24, 2015 23:01:42 GMT
Btw, the game already supports (at least in the HUD file, so I would assume the .exe as well) the following resolutions: 1600x900; 800x600; and 640x480; So, although maybe you're thinking of convenience, but you don't have to waste code on those. No, these are the only hud sizes the game exe (as of Patch 1.2) recognizes:  I saw the 1600x900 Hud in the reader.zbd file you gave me and assumed you added it, is that not the case? That's the Hud from the screenshot I posted on the last page. 1600x900 
|
|
|
Post by AncientxFreako on Jun 25, 2015 0:04:26 GMT
Oh, yes that's right, I did add that to the hud file. However, I guess I'm basing my opinion on the fact that I've been playing the game on a flat screen with 1600x900 resolution for a while now, without the modded hud file, and it has worked find. I must assume that the .exe defaults to one of the other larger resolutions it supports in the hud file and .exe.
|
|
|
Post by AncientxFreako on Jun 25, 2015 9:39:42 GMT
|
|