should I download the GameModule_Ipatix64BitPatchWithWidescreen ?
I will download the other just to see if it changes anything
Those are the same FOV wise
the first one just changes the mode to windowed^^
Okay, I ran into a problem with the new splitter
As I've already said the ELB engine in XXL1 contains a bug from a logical standpoint. I can either include the proper update flag which would give us the opportunity to spam the action key like idiots while being on the overworld to trick the engine into a false loading flag
or we're going for the old flag that just holds if a loading screen is shown
@yarnfang , @Noxus94, @Failentin, @Nekin. Sorry for the ping but I'm kind blocked till I know what we really want^^
I changed the GameModule to GameModule_Ipatix64BitPatchWithWidescreen and it worked
What do you think about that @NoTeefy ?
What's changing on the player side with these two different options ?
Well, that's hard to say... I mean it's an error by the devs after all
but it's still something we could prevent if we'd settle down on a loadless timer that just removes the loading screens, even though it won't cover ALL loadings that way
The problem is essentially this: The engine holds a flag whether something's getting loaded or not (from the disk, memory, whatever); this is the *real* loading flag. So far so good. However they already set the loading flag before the loads even start, which means if you try to load into something (pressing your action key while being in the map discovery animation) it will set the loading state to true, then checks if you're even allowed to enter the level yet, just to realize that you're not allowed to do so by that time and then sets the flag back to false again.
So we definitely can't use that, right ?
What would this mean for us:
Option 1 - Correct loading flag; manipulations will be possible => We have proper loads removed but can trigger "artificial" loads during animations which will save us some seconds in the run
Option2 - Loading screen flag; manipulations won't be possible => It's not really a real representation of loads but at least removes the loading screens
Well one could say it's how the game behaves and therefore valid
but from my pov it's kind of in the grey zone, because they never build the engine/game with the intention that some other programs are going to be using their logic/flags for their own purposes
Aren't there any other flags?