Re: [WIP] ToEE Front-End X 4.0 Progress Report Hey Ag, one other minor interface quibble: could we heighten the boxes where the module names are displayed? Right now they look a little scrunchy. From a design point of view, I suspect that the reason for this is that the lower half of the interface features large, wide open spaces where the module image and text description are displayed, so the eye senses some incongruity with the other end of the spectrum (small spaces) holding sway up top. I think if each module name box could be maybe tripled in size, that would be ideal. See below for current and proposed examples.
Re: [WIP] ToEE Front-End X 4.0 Progress Report @ Gaear: I agree, that sounds like a nice idea! I'll see what I can do, not sure how easy/hard this might be to code with the standard Swing library, I'll do a little research on that! - Agetian
Re: [WIP] ToEE Front-End X 4.0 Progress Report UPDATE: Updated to Release Candidate 6. Increased the row height in the module list table. @ Gaear: Please let me know what you think (if it's good enough or not). - Agetian
Re: [WIP] ToEE Front-End X 4.0 Progress Report Ok, v4rc. From v1: Code: 0x164E 32bit - width 0x1656 32bit - height New: Code: 0x147298 89 44 24 30 DB 44 24 30 - old DB 05 4C 51 2F 10 90 90 - new 0x1472FF 89 44 24 44 DB 44 24 44 - old DB 05 50 51 2F 10 90 90 - new Btw, I have a 16:9 monitor, so fullscreen 1680x1050 crashes(even vanilla .dll), and 1920x1080 seems to work. Request: "advanced resolution input" option.) //Sadly .cfg file is loaded after windowed mode adjustment, so i can't just read .cfg values. .dlls to test: 1680x1050 1920x1080
Re: [WIP] ToEE Front-End X 4.0 Progress Report @ AjiTae: Hmm seems to work the same way for me in fullscreen as the previous one (the party isn't centered on the screen, for instance) - in the windowed mode it's centered normally). And yeah, might work on implementing the custom resolution setup (with a note that it's an unsupported feature, I guess). By the way, out of curiosity - are you running 1920x1080 mode fullscreen or windowed? I know it never ran fullscreen for anyone before and it's marked as unsupported for that reason on the widescreen gaming website, it's actually very remarkable that you've gotten it to work! Could it be that your hack is allowing it to run correctly?... - Agetian
Re: [WIP] ToEE Front-End X 4.0 Progress Report Strange. Works for me. V3 changes must be cleared, may be it is the problem. Fullscreen mode screenshot right after new game start:
Re: [WIP] ToEE Front-End X 4.0 Progress Report Hmm OK let me retry again, I've killed the old temple.dll first though (but maybe I was mistaken when entering the patch data...) - Agetian
Re: [WIP] ToEE Front-End X 4.0 Progress Report Bear in mind that resolution failure is also seen in more sneaky ways, like discovering down the line that your party doesn't appear on map changes. I've heard tales about greater resolutions working before, but the Widescreen guys know what they're talking about. Unless we can document basically a full play-through with no issues, I don't think we should deviate from their recommendations in our products.
Re: [WIP] ToEE Front-End X 4.0 Progress Report @ Gaear: Yeah, ToEE can indeed be devious when it comes to unexpected behavior. So, what do you say, should we support custom resolution setups in TFE-X or not? :\ - Agetian
Re: [WIP] ToEE Front-End X 4.0 Progress Report @ Aji'Tae: Sadly, I can't get it to work Maybe I'm just doing something wrong, but if I patch the .dll with this: 0x164E 32-bit width 0x1656 32-bit height then both new patches you submitted and run the game fullscreen (tried in 1680x1050), the game crashes to desktop. If I revert the first two values (0x164E and 0x1656) to 800x600 before running the game fullscreen, it doesn't crash but it doesn't center the party on screen either, so it behaves like the older version of the patch. Made sure I'm working with a clean temple.dll before patching and made sure the patches are applied correctly in correct locations. - Agetian
Re: [WIP] ToEE Front-End X 4.0 Progress Report As an advanced option - why not? Just warn the user that it can ruin his game at any moment.) Hmm. =\
Re: [WIP] ToEE Front-End X 4.0 Progress Report SUGGESTION: Since the new front-end appears stable enough (as of RC6) and the new reshack might take a while to stabilize and fully test, while some additional features such as custom resolution setups need discussion (and potentially extra testing, too), I suggest that we release the latest RC6 (unless there are any current issues you can think of) publicly as final version 4.0 and then keep working on the new features and updates to the current features - there's no point in delaying v4.0 because of it, we can always release v4.1, v4.2, etc. What do you say, guys? - Agetian
Re: [WIP] ToEE Front-End X 4.0 Progress Report By the way, tried the .dll you supplied above to make extra sure it wasn't my fault - the 1680x1050 one CTD'ed for me too Sadly, can't test the 1920x1080 one 'cause my monitor isn't big enough. - Agetian