All Activity

Hi guys. I am sure there have been posts about this but I couldnt really find anything specific to my system. I am new to this and need some help. I have some flickering on edges. Not on the edges of the field of view but on hard edges on the terrain and other planes. Could you help me with a setting that will work with my system or do I need to upgrade? System: Pimax Crystal light NVIDIA GeForce RTX 4070 Intel Core i7 14700K 20 Cores 32GB RAM null

In the mission planner, before starting the mission, you can see your starting position and where it is located on the airbase. When you contact ATC they'll tell you active RWY number so you know which way to go (ex. RWY 09 means you should taxi opposite direction 270 to the end and take off heading 90). In the kneeboard you can find and reference the airbase chart for taxiing around.

What a cold-blooded and sophisticated guy you have to be to pull something like that off...incredible!

If you mean save during the mission then no, it's not possible. Campaign progress is only saved after you quit the mission after successfully completing it and click "End mission" in the debriefing, so the next time you run the campaign, you start with the next mission.

Did this project come to fruition? Love to see a caribou in dcs even if only AI...

So here’s a question for the techies among us. If I make a multiplayer FAC mission with the Bronco, does the other player need to have the complete OV-10 module installed as well in order to see the actual Bronco skin in game, or is it possible for him just to save only the Bronco skins themselves somewhere and the Bronco will appear correct in the game???

Yes , there is absolutely another picture

@HOKUM52 Thank your for your report. There is a new Thread for the new PIMAX-Tool. It would be nice, if you would use this Thread to collect all the issues there. The fix could be disabling Bloom in the DCS VR settings section and Flares and Dirt in the System settings. Strange if you have the issue only with the newest PIMAX tool. Cheers

Understood - I have not been aware that Eye Tracking Switch even makes a difference with the Super, but using Necksafer I just found out that having it OFF resolves any Necksafer problems with a blurry sight

Yesterday, I had my first flight in a campaign in the dark of night and unfortunately have to confirm that the Super is causing problems here. I have a bright corona around the aircraft, sometimes the aircraft disappears because the headset seems to dim on its own, and when I go into the cockpit, everything is gone until the headset brightens up again. It almost seems as if some kind of glare function is integrated. The sunrise looked disastrous and completely unnatural. I've only just discovered this thread and will try to change the settings tonight. If necessary, I'll have to revise my positive review of the headset due to its lack of nighttime suitability...

Same.

Welcome to the update Vietnam War Vessels 2.0.2! This update brings a few changes with it: First, the USS Enterprise got support for lights at night. Second, the USS Bon Homme Richard and Generic Essex carriers with SCB125 upgrade got updated parking positions, so planes drive in reverse to the parking. Unfortunately the result is not always great - some positions the planes wiggle for and back. We're working on further improvements to this, but with the carrier plugin gone from ModelViewer it's quite some work. Third, the livery names were normalized and start with the ship designation in brackets (e.g. (DD-728)). The update only contains the changed assets and not the complete mod. You need to install Vietnam War Vessels 2.0.0, then update to Vietnam War Vessels 2.0.1, and finally this update Vietnam War Vessels 2.0.2 can be installed. https://github.com/tspindler-cms/tetet-vwv/releases Alternate download on Google Drive: https://drive.google.com/drive/folders/1XHQWl6aq5nPYAeLnRnSViTqPBNsMcx7u?usp=drive_link Enjoy! TeTeT

No reason to have it in the autoexec.cfg file if that's the case. I wasn't aware of the buttons, and/or are just using an ever growing list of things to try and check when I hit performance issues, and this was on it. I'll amend the original post. Thanks fort he heads up.

What you have described is the issue you will get if you enable the Eye Tracking switch in the DCS VR settings. There is !!no!! need to enable this switch for Eye Tracking with a PIMAX OG or Super Headset.

Hello, I’d like to report an issue with DLAA in DCS when using a triple-monitor configuration. Hardware setup: Monitors: 2 × AOC Q27G4XF 27" LED Fast IPS QHD 180Hz 1 × AOC CU34G2X/BK 34" LED Wide QuadHD 144Hz FreeSync Curved Combined resolution: 8560 × 1440 (2560+3440+2560; screenshot attached). GPU: Gigabyte GeForce RTX 3080 VISION OC 10GB GDDR6X Rev 2.0.

I support I'd be great to also made NVGs fixed fov, which is dependent on the device. Last time I checked you could zoom in/out and the NVG cirlce stayed fixed relative to the screen.

That's something i didn't pay attention to, but will look at it . Thanks for the report. by the way , feel free to use "issues" to report what you think is wrong , or improvments https://github.com/landre-cerp/McduDcsBiosBridge/issues

Interesting. I get this with my QP. I will try your idea and see if it works for me.

OK, did some testing yesterday... My problems with Necksafer had nothing to do with the Eye Tracking Switch in DCS. In my case Nechsafer API has to be in #1 rank within the OpenXR API Layers GUI, otherwise it won´t work. So my API-order is: #1 Necksafer API #2 Motionsystems API (for motion compensation) #3 QV Companion API Only than I get Necksafer to run without a problem. However - the Eye Tracking Switch in DCS makes a big difference in Necksafer: Having it ON I have a very blurry sight when looking back. It seems that the Foveated Rendering Area stays at my actual head positioning of 110° while my view snaps to 160° and therefore is out of the high rendering area. Having it OFF it works perfect, the Foveated Rendering Area also snaps back to 160° while I am only looking at 110°

Thanks , I'll check how it works and if it's ok, I'll enlarge this area in the update.

You want to spoil that one for me too?

Not to play white knight for ED, but basically you have described it yourself. SRS is a standalone tool which has very minimal dependencies on DCS. Other than reading the radio unit switched location, SRS doesn't care about DCS and it's a radio app by itself. What ED is trying to do is to integrate all of that into the what everyone now knows is a code hell of a DCS so that's why it takes long whereas Ciribob basically has all his attention on the single app and that's it. On the other hand, latest VoIP is pretty much very good in itself and works mostly as SRS users would expect. There is no splitting of audio per sides (but to be honest, I'm not sure that's realistic setup in a first place) and IIRC MIDS radios aren't supported, but the rest works out of the box within DCS, it isn't supported by 3rd party apps. It's a shame that the current release of the VoIP wasn't the initial release as now there's basically no connection issues like before and radios work as advertised.

I'd also like to see something from the East as well. For example, the new version of the Hip, the Mi-8MTV-5.