My ROF install has been consistently stable until today. I suspect it might be update related. I requested the 'update' on the start menu which should have brought me to 1.022. I verified this by logging off and starting the game again. On checking for 'update' I was advised that I was current.

However, the 'Start Game' then 'Start' selections brought a black screen indicating a launch, but promptly ended in a crash to desktop.

How can I repair this catastrophic failure?

In response to myself, I decided that the only way to address a fundamental failure was to eradicate the FFU. To this end, I launched setup in my Rise of Flight, Iron Cross Edition, and completely re-installed the program from C++, to DirectX to custom skins. This process culminated in an installation of a 1647Mb update which appears to brought the ROF install uptodate.

However, even after this lengthy exercise, the program refuses to engage in a launch sequence. The Start button responds, bringing up the ROF Settings agenda, but on pressing Start the screen goes black with some greenish script appearing in the upper left corner for a second, then a collapse to desktop.

The system in question is an Intel Dual Core (3.3Ghz), Nvidia GTX285 (1GB VRAM), XP S/P3, 4GB DRAM. This "does meet spec." Yet a complete rebuild fails to launch. Has the newest patch brought the graphics demands to the SYSTEM7 range, like DCS A10 or Cliffs of Dover, where a 3GB Boot.ini switch is now required ?

Before engaging in more program proctology, I would very much appreciate guidance from someone more experienced in resolving ROF FFUs (Jason & Cie!)

not sure what exaclty what the problem is. I would try changing the settings to very low and see if the game launches, then slowly up your settings a bit I don't think the game is any more demanding with the new patch.

Green text in upper left hand corner is ENB mod. Not sure why you would have that if you did a clean install. What does the green text say?

Jason

I have to admit, I had a minor issue with update this time around as well (update failed 1st time), but managed to get it resolved without too much heartache.

Maybe b/c it is Thanksgiving weekend in US with increased web traffic causing corrupt DL???

I like Rise of Flight very much as a gaming as well as simulator experience. Unlike DCS A10 or Black Shark, or even BMS Falcon, I do not have to become overly obsessed with switch selection sequence. I was frustrated and concerned that somehow ROF had died on my system.

In parallel, I contacted ROF Techsupport. Viktor S promptly responded. The first question on graphic settings had already been considered, having instigated my Boot.ini and Selective Start workarounds necessary to get DCS A10 and Cliffs of Dover to work 'well' in XP. I had feared that 777 Studios was creeping toward 64Bit territory. Fortunately I was wrong. These setup techniques were dead on arrival.

Viktor also suggested something I suspected: "One thing - try to run "recovery' from updater tool, as it can be that something went wrong during update." A 'Recovery' operation failed in my case. This led to the thought that the failure was a patch FFU as I did suspect and would require a complete reinstallation with everything obliterated.

So while my other turkey cooked, I proceeded with gaming proctology, a complete reinstallation from C++, to DirectX, to custom skins and finally 1647Mb or 562 files of update material. I believe I am current. At least the updater indicates so.

In the end I am back to 96% graphics memory utilization and a functional Rise of Flight. My only thought is that the newest patch setup suffered from either a cosmic or ethernet fart. This misapplication was fatal to the existing application. I now have a older Volition ROF
folder with a new Rise of Flight directory.

I hope that my new installation is stabably stable.

Good luck and glad you got it working.

Man! I was having a problem too, the update failed ! I tried recovery and it failed again.So first place I go is to this forum to see who else was having problems. I read 5555's posts.. reinstall?? repatch?? OMG I dont have time for that. I decided to go
back a try update/recovery again.. Here's what happened:

21:38:29] Checking for updates
[21:38:34] Started update
[21:38:34] Downloading update files
[21:38:34] Estimated update size: 314 Mb
[21:38:35] Estimated update size: 312 Mb
[21:38:53] Performing update
[21:38:53] Failed to perform update, see update.log for details
[21:40:27] Starting recovery...
[21:40:31] Started update
[21:41:13] Downloading update files
[21:41:13] Estimated update size: 311 Mb
[21:41:45] Performing update
[21:41:45] Failed to perform update, see update.log for details
[21:56:09] Starting recovery...
[21:56:11] Started update
[21:57:04] Downloading update files
[21:57:04] Estimated update size: 311 Mb
[21:57:31] Performing update
[21:57:31] Failed to perform update, see update.log for details
[21:58:11] Starting recovery...
[21:58:14] Started update
[21:59:00] Downloading update files
[21:59:00] Estimated update size: 310 Mb
[21:59:26] Performing update
[22:01:13] Performing post-installation actions
[22:05:26] Recovery finished successfully

Whew. That was a relief. Sometimes I guess it pays to keep trying.