Jarhead0331

Why the hell would Magnitude 3 post a clock when the release is entirely dependent on the patch and the patch is entirely dependent on ED? Seems like a recipe for getting peoples' hope up and then seeing it crushed.

Technically it is not really a rollercoaster. It has pretty much been all down hill for us.

This just blows. ED needs to release a public statement. I don't know who is giving them their legal advice, but this has been a PR disaster and with the removal of all Razbam products from the store, it is only going to get worse. It would be wise for ED to get ahead of this latest development and issue some kind of a press release. Parties in litigation make public statements all the time and it is missing out on an opportunity to take control of the narrative. It all begs the question, why, after a year, would Razbam make this request now? Furthermore, why would ED agree to it. There must be some contractual basis or development that led to this event.

"We cannot continue to support the platform or maintain our modules..." If I'm not mistake, they have not been supporting the platform or maintaining their modules. My intention here is not to opine whether they are contractually in the right, or not, but just stating a fact. What is the point of this post other than to remind us of the obvious? There is still no resolution in sight.

^I knew that! Not sure how i managed to flip that around. lol

Thanks for the insight.

What is the average cruise speed for you guys? I've read that Avg speed for the OH-58D is around 125mph. However, I really struggle to keep it above 90 on the indicated air speed, which I understand is displayed in knots. That would mean I'm actually cruising around at less than 80 mph. It seems painfully slow to be getting around from point to point. Am I doing something wrong? What is the trick to getting some more consistent speed out this helo? Thanks.

I checked in the Varjo discord and this is not an isolated issue. It is impacted a lot of users, and many who are not using 50xx nvidia cards. Apparently, its been an issue for months and Varjo is yet to do anything about it. Some have had success by rolling back to earlier versions of the Base software, but this has not helped me yet. Long story short, there has been some software change that has bricked hundreds of these headsets.

Thanks for the quick reply. My Nvidia drivers are up-to-date and my Base software is too. Running 4.7.1.10. No dice. Any other suggestions?

It has been a few weeks since I fired up my rig that is connected with my Varjo Aero. Last time I used it, everything worked fine. Now, the Varjo Base software says that the headset cannot be detected. I've tried updating the Base software, I've plugged the display adapter into several different ports, plugged the USB adapter into several different ports and I've tried disconnecting and reconnecting the USB-C from the little hub. When I disconnect and reconnect the USB plugs, I hear the window's "ding" so I know windows is detecting the device. Also, I can hear the headset fan and see the backlit display. There is just no image. I've made no changes to hardware or software other than routine windows updates and a few Varjo Base updates that have been rolled out over the last few days. Any thoughts on what could be causing this? Thanks in advance.

I'd like a keyword search feature for the User Files section. If one exists, I haven't been able to find it.

The title of the subforum is "bugs and problems"...I had a problem. Where else should I have posted about it?

May have tracked the problem to an old aircraft mod. Is it possible for an update to DCS to create a problem with a mod that could lead to this?

I'm not sure how and I'm not sure when, but at some point all carrier based missions seem to have broken. This is across the board in the Hornet and the Tomcat and in all training missions or single missions. The mission loads straight to the F10 map and within seconds my aircraft falls into the sea and the mission ends. I've installed no new mods and tried full repair. i took a long break from carrier ops with the release of the various helos and F-4E, so its been quite some time since I have tried a carrier mission. Any thoughts on what could be causing this? Thanks.

VR requirements have changed so much over the years with DCS updates and new headsets and software that I sometimes lose track of what is what. I apologize in advance if this is a stupid question. For quite a long time now, every time i have updated DCS, I've bin replacing the following three files in the bin folder: D3DCompiler_47.dll opencomposite openvr_api.dll I'm running DCS with the Pimax Crystal with OpenXR Runtime set to Pimax OpenXR, since this feature was released. Do i still need to replace the above three files in the bin folder. At the risk of embarrassing myself, I've forgotten why I have been doing this process for all this time. Thanks for clearing this up for me.