You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently mednaffe and mednafen must be in the same folder to work.
Furthermore mednafen always creates a lot of sub folders which are not necessarily relevant (e.g. for savestates, bios, roms etc.).So it would be convenient if mednafen can be placed in different folders like a "mednafen core folder". Also a system or data folder for mednaffe itself would be great (for the data files).The benefit would be an improvement of the structure and overview of mednaffe and the root folder.
The text was updated successfully, but these errors were encountered:
Next version will not need to be in the same folder than mednafen.
If mednaffe does not find mednafen executable it ask you for it. This means that mednafen could be placed into whichever folder.
I'm not sure what you mean about 'data files' from mednaffe. Executable is the only thing needed to work.
Sorry my fault.
I thought you have further data or library files (e.g. dll, cfg...) which could be packed into a folder.
But these files belong to mednafen.
Actually you only have one executable and a ini file, which will be created after the first boot.
So the implementation you did is great and fully sufficient to create a folder structure. :)
Thank you so much.
Currently mednaffe and mednafen must be in the same folder to work.
Furthermore mednafen always creates a lot of sub folders which are not necessarily relevant (e.g. for savestates, bios, roms etc.).So it would be convenient if mednafen can be placed in different folders like a "mednafen core folder". Also a system or data folder for mednaffe itself would be great (for the data files).The benefit would be an improvement of the structure and overview of mednaffe and the root folder.
The text was updated successfully, but these errors were encountered: