Horns

Would be great if you can, but either way ED has the choice to alter the schedule. @Silver_Dragon Would you know if it be a lot more work for ED to release the patch for a new module and the regular planned update separately?

I guess you mean that the patch that introduces a new module doesn't have to conform to the six week window, yeah? You weren't suggesting that they could do the release without releasing a patch. I hope you're correct that they are prepared to vary the window. I'd hope ED are aware of the updated timeline for the F-4E, so if the patch schedule would prevent that timeline being met I hope they would have informed HB and we would have heard about it before now, along with a newly revised ETA. Please note however that hope is not a strategic position.

We’ve got pretty OT, maybe that’s natural because we seem to have covered the range of positions re the original topic. If anyone else wants to say something in response to the topic I suggest you do so quick because I don’t know how long this will stay open…

That would be me. They succinctly phrased more or less what I was thinking, therefore I was grateful.

No alternative I'd bother with, which is why I'm still on board with this. I was just pointing out that if people would have chosen not to preorder the Heatblur F-4E had they known about the extra wait they have an out. Personally I think it's worth the extra wait for sure.

Agreed. I think it bears repeating that HB have offered a refund ('No Questions Asked' I believe) to anyone who is dissatisfied, so if anyone is so uncomfortable with the situation that they want out all they need to do is tell Heatblur. I don't know how that could be fairer.

Got my t-shirt today, Western Australia. Looks great, thanks!

FWIW, I can confirm DCS starts for me after the update.

Ok, thanks for replying. Given the circumstances, if users need assistance employing the workaround mentioned in this thread, they are welcome to DM me and I’ll do my best to help.

Anyone know if the update got delayed?

You have the choice of doing as suggested in the post marked as the solution here, or waiting 24 hours or so - hopefully the next DCS patch will be available then, and that should contain a fix.

Glad you weren't completely cut off! It is indeed interesting that DCS works on your second rig (and kudos for having two DCS-capable rigs to begin with). Would be great to know if this crash problem (and the issue with the PTC build this appears to stem from) is specific to Windows 11. At this point I'll reinstall Windows 10 if it means I'm less likely to get issues like this in the future.

Sorry I couldn’t offer anything more effective, would have been good to get you up and running before the long weekend ends. Fingers crossed the DCS update gets pushed on Wednesday and it’s the solution to your problem. FTR yes, pancake means flat screen

The only other suggestion I have is to ensure you don't have Public Test Channel enabled in Settings on the Beta tab. If you find it was enabled, when you first disable it it will download an update. Let it do its thing. Bad news is that, if it doesn't work after that, you should probably copy the files you downloaded in the fix back into the relevant folders (oculus-client, oculus-diagnostics and oculus-runtime). I have no doubt this situation is frustrating, and before I found the fix for the issue I had most recently I was furious (I may have vowed to kick Zuckerberg hard enough to make an outie an innie). However, the silver lining would be that the problem that prevents users loading the game based on the make of headset they have is one that we have a fix for. As ruprecht says, this seems to be a different problem that isn't being experienced broadly, so once you find a fix, hopefully this problem will stay fixed on your system.

There are some zip files among those downloads that need to be extracted, did you do that too? I mention it because I wasn’t sure myself at first