skybaby68

I should also add that the connectivity is fine, no warning signs under USB ports in device manager, power saving boxes unticked, correct setup as per instructions and using USB2.0 instead of USB3.0. Power not an issue as I've a 1000W PSU. The Crystal battery 'always' remains fully charged.

This is good to hear because it's getting worse. You can depend on Eyetracking disengaging around 3 or 4 times per every 30 mins in DCS. Also there is no easy or sure-fire way to turn the headset on and off. As soon as I turn PC on, the PiPlay software asks to connect which I allow it to, then sometimes I have to manually turn the geadset on by holding the power button down for 4-5 secs and 'eventually' it 'may' connect; other times it just will not connect, causing a PC restart (I regularly check device manager to ensure a tick hasn't been put into the power saving box). And shutting down ... it just will not stay shut down no matter what I try ... to select 'shut down' on piplay before sutting down, physically powering down, it will just come back on after a few seconds. For £1500 (plus the plethora of extra accessories you 'have' to buy to gain a relatively non-painful experience), it's a complete mess of a headset ... it's becoming unenjoyable now with so so many shortcomings.

March 2024 - Still happening. Spent hours creating a detailed map at Nevatim and on testing I couldn't work out where the mass firebomb was coming from until I noted 3 AI aircraft air spawning over the runway and not from their allocated park slots of 01, 03 & 05. When you say Priority Highest. Do you mean ... within the 1st couple of years?

Also I've disabled all mods from JSGME, deleted contents of metashaders & fxo folders etc & ran the repair. No difference.

Hi Flappie. Yes I've done that and keep periodically checking that it's still an exception.

I have 3 home PC's, 2 running DCS in VR and 1 running in 2D PC 1 & 2 are indentical: 19 14900K with 4090, 64GB DDR5 RAM, but PC 1 is running Pimax Crystal & PC 2 is running Quest 3 Both are running OpenXR and since 2.9.3.51704, both of the above PC's will, at around 60% of the time, cause the entire PC to run at a snails pace when DCS finally gets to the main menu. I have the OpenXR FPS counter running and it plummets from the usual 91.0 down to 2, sometimes rising to 30 or so then back to 1-2. Most of the time it takes the PC with it, having to exit DCS via task manager & hope the PC gains enough momentary speed to be able to exit DCS and try again. Invariably it will also do it coming out of a mission, back to the main menu. My 3rd PC running DCS in 2D is an i7 11700K with a 3080Ti & 64GB DDR 4 and is unaffected. It's worth noting that this is an all new problem since the last update. All PC's were running fine beforehand. If anyone can relate to these problems and can guide me out of this hole I'd be most grateful. dcs.log-20240305-185237.zip dcs.log-20240305-145615.zip dcs.log-20240304-210515.zip dcs.log-20240303-004138.zip dcs.log-20240225-152737.zip dcs.log-20240227-042437.zip dcs.log dcs.log.old

I have 3 home PC's, 2 running DCS in VR and 1 running in 2D PC 1 & 2 are indentical: 19 14900K with 4090, 64GB DDR5 RAM, but PC 1 is running Pimax Crystal & PC 2 is running Quest 3 Both are running OpenXR and since 2.9.3.51704, both of the above PC's will, at around 60% of the time, cause the entire PC to run at a snails pace when DCS finally gets to the main menu. I have the OpenXR FPS counter running and it plummets from the usual 91.0 down to 2, sometimes rising to 30 or so then back to 1-2. Most of the time it takes the PC with it, having to exit DCS via task manager & hope the PC gains enough momentary speed to be able to exit DCS and try again. Invariably it will also do it coming out of a mission, back to the main menu. My 3rd PC running DCS in 2D is an i7 11700K with a 3080Ti & 64GB DDR 4 and is unaffected. It's worth noting that this is an all new problem since the last update. All PC's were running fine beforehand. If anyone can relate to these problems and can guide me out of this hole I'd be most grateful. dcs.log.old dcs.log dcs.log-20240225-152737.zip dcs.log-20240227-042437.zip dcs.log-20240303-004138.zip dcs.log-20240304-210515.zip dcs.log-20240305-145615.zip dcs.log-20240305-185237.zip

I'm running the Flight Sim version of the crystal (no lighthouses or controllers) and although eye tracking is enabled & calibrated, auto IPD adjustmenst on, Pimax XR & Quad Views set up etc, I check eye tracking's working by running the calibration tool but it seems that I have to recalibrate every time I restart a VR session as it's no longer working after switching off (even though in device settings, eye tracking is always enabled and green). Also, the clear black lines around the eye tracking box in DCS (especially external views) is shockingly obvious; really very noticeable to the point it's a total immersion breaker. Running the latest firmware as it asked for a firmware update as soon as I got it up and running at the weekend and have also double checked that I have it running in PC mode not standalone. So far ... really not impressed with it at all. It's even a total nightmare turning the headset on and off. It comes on 60% of the time when holding down the power button for 4-5 secs but switching it off, it just boots back up and comes back on again when it feels like it (even if you also select 'shut down' on the pimax software screen).

Hmm ... strange indeed. 4th attempt after tonight and all is now well once again.

Down again for me. 13.02.2024 @ 22:40 UK time.

Ah ok I was fearing this. So I guess there is no way at all of achieving this without the use of scripting? Ok many thanks for your help and thank you so much to both for your time & input. Very much appreciated indeed. I will certainly take a look at the above links

ind_unit_messages_test.miz OK ... is there at least, a script floating around somewhere that can perform this? (I've tried in vain, multiple times, to understand DCS mission editor scripting but my brain just doesn't understand it in the slightest). I've included a very simple example of my attempts. Two client spitfires on the ground, 3 targets on the airfield. I am trying to have only the player who takes out the target to receive the message.

Hi. So the scenario: A very basic WW2 target range. Max. 2 players in warbirds taking out stationary targets. A points system has been set up using the 'Define Mission Goals' and messages will appear on screen to the player that destroys the target. My wish: For only the individual that destroys a target to receive a message ... (i.e. Opel Blitz destroyed - 10 pts). I've been using the condition 'unit dead' (specific target) then the actions 'message to unit' (individual client plane) & obviously cloning the trigger once again with the same conditions but on actions, a 'message to unit' for the other client plane. Obviously with the above setup, when a player client takes out a target, both players will receive the message as there is nothing telling the sim who made the kill. Is there a way (without scripting as no matter how hard I try, I just cannot understand it), that the client kills can be differentiated and if so, how would one go about it. I've tried the condition 'Unit Hits Successful' but again it only correlates to the target. I've tried creating a 'Target Range Zone' and having an individual flag turn on when the target is destroyed by one of the players but both players 'still' gets the message. Any help would be greatly appreciated. Thanks.

+1

Thankfully this looks to have been resolved with the Dec 19th update.