Updating the pacemaker firmware does nothing

[myowncontrol]

I've hacked into the pacemaker and uploaded the cycle test. I've logged into the firmware update utility and selected the new cycle test dll and watched all the yellow bars fill until it said completed.... but nothing happens!?! I've even double checked by watching Youtube walkthroughs and I'm doing the right thing, it seems.

I've attached my save... I'm playing on OSX

[myowncontrol]

https://www.dropbox.com/s/wxzy2i4ccfg8t4n/save_mo0kid.xml?dl=0

[Loki]

I'm running into this exact same issue, also on OS X with yosemite.

[myowncontrol]

New update makes it even worse

http://i.imgur.com/Ee0szx3.png

[myowncontrol]

Not wanting to sidetrack, but this game won't even open on my Windows PC, as they've f'd up something with the Cloud Syncing.
This game is so broken in its current state, and all these little mini-updates are just bringing new bugs. The dev's really shouldn't continue taking people's money. Why are these builds allowed to be published without being properly tested.

[Orann]

Originally posted by mo0kid:

Not wanting to sidetrack, but this game won't even open on my Windows PC, as they've f'd up something with the Cloud Syncing.
This game is so broken in its current state, and all these little mini-updates are just bringing new bugs. The dev's really shouldn't continue taking people's money. Why are these builds allowed to be published without being properly tested.

I'm working on it. The windows build has a huge fix patch that's in testing now that should hopefully fix the issue. Sign up for it here and please report back if it works:

http://steamcommunity.com/app/365450/discussions/0/487877107150929886/

I'm not sure what the community wants. I was getting pressure to release quick fixes to some critical issues that came out, and I made some mistakes. I apologize for that - really. I don't have a big testing team or anything - it's just me - I've tested the builds on several setups, with several people's save files, and made sure they were running before deploying, but in my rush to get solutions out, it's fixing some things and making other bits appear worse, and I introduced some new bugs. That fix patch was for the Sequencer bug, and it included my changes for looking into your issue (which i'm focusing on now - but not a full fix for it yet).

A fix for yours should be out within the hour.

[Orann]

A fix was just put out in a patch. Unfortunately there's no good way to fix the file you currently have downloaded, as it's an issue with your save file itself - new games wont have this issue (this and the other file execution issues only affect some people that made saves between 2 specific patches, where I added in cross-platform save support, on some platforms. and is due to the random number generator being non-deterministic between platforms and patch versions in the mono runtime - I replaced it with a new one).

I've written in a fix that means you can now re-download the file from the original server and it'll work. Sorry for the inconvenience!

[ZeroBeat]

Hi,
I have run into the same problem as OP (also running OSX).
Started the Project Junebug mission today and did all required steps.
So I uploaded the PacemakerFirmware_Cycle_Test.dll to the folder for the firmware files on the pacemaker, but when I try to activate it, I always get "Invalid Firmware File" as shown in the screenshot in post #3.
Is there anyway around this?

Thx and greetings!

[myowncontrol]

Originally posted by Orann:

I'm not sure what the community wants.

Generally, some kind of assurance that there is some kind of QC on release builds.

Originally posted by Orann:

I don't have a big testing team or anything - it's just me...

There are plenty of fans here, including myself that would have gladly assisted for free in testing a beta build.

Originally posted by Orann:

A fix was just put out in a patch. Unfortunately there's no good way to fix the file you currently have downloaded, as it's an issue with your save file itself - new games wont have this issue (this and the other file execution issues only affect some people that made saves between 2 specific patches, where I added in cross-platform save support, on some platforms. and is due to the random number generator being non-deterministic between platforms and patch versions in the mono runtime - I replaced it with a new one).

I can't open the Windows version at all, I have no idea why, I'm assuning it's still trying to pull the Cloud Sync save files. Not sure how to get out of that loop.

Originally posted by Orann:

I've written in a fix that means you can now re-download the file from the original server and it'll work. Sorry for the inconvenience!

Which file from which server?

[Loki]

Thank you for your quick response Orann, unfortunately I'm now getting that the pacemaker test dll is invalid. I've deleted the dll from the pacemaker as well as my local machine and redownloaded it from the original server, with no luck.

[Yacker]

I've been searching about this issue all morning and just found this top post in the forum. I also have this issue with the pacemaker test dll not being valid and playing on OSX. Anyway we can modify our current save game file to get this working again?

[Orann]

--- UPDATE ---

Sorry for the previous version - It wasn't working for everyone. If you're having this issue, re-download PacemakerFirmware_Cycle_Test.dll and it should work properly.

This was an issue caused by the way I generate the software ID keys internally - the deterministic random number generator wasn't deterministic across versions as I thought it should be, so I had to re-implement a new one that would be, which broke all previously generated executables. I wrote a fix to allow their use too, but that patch unfortunatley triggered the RNG determinism to flip again, so old saves remained broken. I'm trying to clean up all the critical-path executables now, so people with the old-format saves can still finish the game (though they might see some leftovers from this still, like not being able to use ThemeChanger).

mo0kid - you're right. I got too stressed out about it all yesterday and was scrambling to fix everything straight away - I got clumsy. I'm still getting used to writing fixes to things that keep in mind that at any one time, there's so many systems running it, or at different points in the game - I cant make changes to the way things are generated without breaking all current saves etc. I'll take things a bit slower from here on out and run things past testers more.

As for the windows version, that's already happening. There's a huge patch in testing now that moves it all over to the new FNA framework. It also contains the fix for your issue. I'm waiting to make sure it's safe before I make it public, but you can help out a lot by testing the build on the beta branch (beta password "hacknetFNAbeta").

Thanks for your patience all, and sorry for the inconvenience.

[ZeroBeat]

Just tried it on my Macbook Air and it works fine now, just as you said.
Thanks for fixing this!

[Yacker]

Just tried it as well and I am still getting an invalid firmware. Anything I need to do to resolve this?

[ZeroBeat]

Have you made sure that you removed the existing copies of PacemakerFirmware_Cycle_Test.dll from the pacemaker and your home pc first, and then downloading it from the Eidolon server again (plus uploading it to the pacemaker)?
That's how it worked for me. Else it might be another bug since this is the way it's supposed to work...

[maxcorps]

OK! I found out what was wrong because I'm an idiot. Log into the Pacemaker. Type ls. Go to where the files are. The firmware has it's own folder. I had uploaded 7 copies of the Testcycle .dll to the main folder. Open the firmware folder and upload it there. Then it should work lke it's supposed to.