#27 Testing Executable Not Saving Properly to misc.cfg
When I go to test my map, I'm asked to find my executable.
For me it's '/usr/game/prboom-plus'
I select that files and all works well until I exit Eureka.
After exiting and restarting the program Eureka I'm asked again to find my executable.
I've checked and it is being put into the misc.cfg, but is cleared out when Eureka is started.
I think it's possible that it's being put into msic.cfg improperly,
as it seems to be broke into two lines.
It looks like this (I've also attached a full copy of my misc.cfg)
port_path vanilla_doom2 |/usr/games/prboom-plus
Runnning this on Debian Linux
Originally I experianced this with Eureka Version: 1.24-2 installed from the Debian SID repositories.
Today I download the Source Code from here and compiled it myself and still had the same issues.
I'm not much of a C programmer and I tried looking at the code but couldn't find what would be causing this.
Thanks for looking into this.
I have looked at the code and can confirm the bug. The bug is triggered because the chosen source port is "vanilla", so you can workaround the bug by telling Eureka you are using a different port (anything else should work) though it can be the same executable.
Got it. The work around worked. It took me a few tries, I would go into "Manage Project" and change it to "boom", exited, and it wasn't working. Then I realized I had to change it there and then SAVE the project (doh). I also changed it to "boom" in "Preferences", to hopefully that will now default for new projects.
Thank you Andrew. This is very helpful. My 6 year old is learning to make levels for "Chex Quest" and I had to keep going over and re-entering "/usr/game/prboom-plus" for every time she decided to work on her level.
I personally have had Eureka running 24/7 for a few months now on my machine. :)
Fixed in the git repository, commit 5513bcd7f35f.