Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated Commander Genius #2074

Merged
merged 1 commit into from
Aug 7, 2017
Merged

Updated Commander Genius #2074

merged 1 commit into from
Aug 7, 2017

Conversation

gerstrong
Copy link
Contributor

Version 1.9.9.2 might be beta but it is usable enough and has great features and bug fixes.

@joolswills
Copy link
Member

thanks.

@joolswills joolswills merged commit 90b1484 into RetroPie:master Aug 7, 2017
@HerbFargus
Copy link
Member

I'll have to try this out. The reason I had used an older version in the first place was the newer versions had issues building so hopefully those have been resolved

@gerstrong
Copy link
Contributor Author

gerstrong commented Aug 8, 2017 via email

@joolswills
Copy link
Member

I didn't check sorry. Can roll back if needed

@HerbFargus
Copy link
Member

HerbFargus commented Aug 26, 2017

@gerstrong hey sorry, I just got to testing this on my pi3. It failed for two reasons, one was some folder changes which are easily fixed through the module (due to the vfsroot changes with the downloader)

the other issue is a compilation issue which I don't currently know the cause I think the compiler is crashing, I'll test with more swap to see if I can get it to build successfully. It's also possible this may be resolved once we switch to raspbian stretch which has gcc 6 instead of 4.9

Here is the build log:

https://pastebin.com/bhYcYfAe

If you prefer I can add this to the tracker on the cgenius repo if you feel thats a better place for compilation discussion

seems to be the same error as gerstrong/Commander-Genius#254

It compiles fine on my xubuntu laptop though I had to change the script to

        'vfsroot'
        'src/CGeniusExe'

@gerstrong
Copy link
Contributor Author

Hi HerbFargus, thanks for compiling the CG sources. Not sure why the compiler likes to segfault at this part, but I saw it before somewhere else and same method it was. Did you observe how much memory the build process consumes?

Anyways, I did some modifications on that part, cleaning up a bit. There is new Tag called "v1995beta". Can you try it with that one. I also threw out a lot of files that weren't used anymore.

I can't say for sure, but you might have different results now. Let me know if it works better now...

Because I want to bring up a stable nice version 2.0, I'm in the process of cleaning up the code a lot lately and fixing bugs.

P.S.: Compilation log can be kept at pastebin :-)

@HerbFargus
Copy link
Member

HerbFargus commented Aug 26, 2017

I'm not sure of the memory but I've increased the swap and it still crashes at the same point regardless.

I've tested v1995beta and unfortunately got the same results.

log for reference:

https://pastebin.com/LxtqZMM6

I suppose I could test forcing 02 optimisations in the script module as a workaround til we update to stretch.

also just as an aside this is the module I'm using to install it https://pastebin.com/twRqvjUb

@mmatyas
Copy link
Contributor

mmatyas commented Aug 26, 2017

You can avoid the segfault by renaming the two serialize functions to something else. Looks like it's a bug in GCC 4.9.2; updating to 4.9.3 should fix it too.

@gerstrong
Copy link
Contributor Author

I don't understand how renaming would change the Situation. Let me try to simplify the save system by also changing these methods around a bit...

@mmatyas
Copy link
Contributor

mmatyas commented Aug 26, 2017

This is not your fault @gerstrong. I assume the word serialize triggered some incorrect behavior in this particular GCC version. Unfortunately it'd take about a day to finish compiling the whole game on my Pi 1, but with renaming the functions I did made it past the segfault. Someone with a faster Pi could check if there are any other problems further along the way.

@HerbFargus
Copy link
Member

@gerstrong I wouldn't worry too much about patching for an old version of GCC. We can just do a local patch in the module for older versions as we will be moving toward stretch which I just tested and it compiles fine on. We can consider this resolved. I'll submit a PR an update for the folder changes though and will tweak it when get further along with stretch.

@HerbFargus HerbFargus mentioned this pull request Aug 27, 2017
@gerstrong
Copy link
Contributor Author

Well thanks, I agree completely. Still I might change these methods because I want so as being for the topic of general cleanups. The code design requires a lot of improvements also at that part. So, sooner or later this will be fixed the one or the other way...

Thanks for contributing and best wishes for a nice RPI Application

@mmatyas
Copy link
Contributor

mmatyas commented Aug 27, 2017

Using Clang (eg. 3.9) instead of GCC also fixes the problem, without modifying the source code.

@Jondark
Copy link

Jondark commented Sep 9, 2017

Hi;

I'm brand new to Retropie--and am a complete newbie and not a computer programmer--

Is there an "easy" way to get the Commander Genius working? I'm a big CKeen fan--as are my grown kids, and would love to get this up & running...

If anyone can give "Simplified instructions for installing Commander Genious on Retropie v4.2 for Idiots", that would be great...

:-)

@mmatyas
Copy link
Contributor

mmatyas commented Sep 9, 2017

I've just sent a patch which should temporarily fix the problem. If it gets accepted, you should be able to install the game as usual after updating the RetroPie script.

@Jondark
Copy link

Jondark commented Sep 10, 2017

That would be awesome... I'll anxiously await update notification :-)

Would this port also be able to play other similar old Apogee games--like Cosmo, Secret Agent, etc?

@mmatyas
Copy link
Contributor

mmatyas commented Sep 10, 2017

My patch has landed, and now the game builds fine. There's still an error during the installation step, but #2099 fixes that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants