Chat
Discord
07-25-2015, 08:02 PM
So I might be able to clear up a few things here.
LF2 loads data from the current working directory, which is not necessarily the same as where the executable is located.
If you go and double click lf2.exe it will be the same, but if you have a shortcut you can manually change it by right clicking and changing the value of the "Start in"-field, which will cause it to load its data from the specified directory.
If you have a shortcut on say the desktop and move files around Windows tends to get confused and that may have been what caused the scenario empirefantasy had encountered.
Also, LF2 will load sprites slightly differently. It will first try to load them relatively to where the executable is located, but if the sprite cannot be found it will look in the working directory. The reason for this probably has to do with how DirectDraw works.
LF2 loads data from the current working directory, which is not necessarily the same as where the executable is located.
If you go and double click lf2.exe it will be the same, but if you have a shortcut you can manually change it by right clicking and changing the value of the "Start in"-field, which will cause it to load its data from the specified directory.
If you have a shortcut on say the desktop and move files around Windows tends to get confused and that may have been what caused the scenario empirefantasy had encountered.
Also, LF2 will load sprites slightly differently. It will first try to load them relatively to where the executable is located, but if the sprite cannot be found it will look in the working directory. The reason for this probably has to do with how DirectDraw works.
Age ratings for movies and games (and similar) have never been a good idea.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.