TEMPEST.114

You completely missed the point.

Are you certain? Because even they had admitted it's a fudge that they do based on player aircraft and position to specific other models. Just because it happens behind the tanker and over a runway, doesn't mean its really modelled everywhere else...

8700k o/c 5.0 Ghz 64GB DDR 3 4070ti Though that's utterly irrelevant to the sweet spot issue - that's the lenses.

I wish the burble was MODELLED and not a 'fudge' applied to just the F18. IS that ever going to be implemented?

Nothing simple. You're going to have to write a script that trawls all the units table structures to find what you want and then send the mission a trigger event. Not simple or quick.

What's wrong with a dual boot of two versions of Windows 11. One WMR with no updates and the other fully updated?

It beats the G2 in everything but audio and for the most part the audio is good enough. I'm running at 72Hz (recommended) and I have zero issues. Literally. There are more pixels so of course it's going to be more taxing. I'm getting over 70 in the air above the layers and a solid 36 in the weeds at Mach 1 with all the gfx on HIGH on a 4070ti with an 8700k Cpu. It's night and day in clarity over the G2. No sweet spot and I can really look around everywhere in the cockpit, even behind my hips and it's crystal clear. It's so very, very close to the Pimax Crystal but a much, much better headset overall. I wouldn't change to a crystal if you paid me.

You asked, here's my mini review of the Pimax Crystal. It's currently 1799 on Amazon UK but for some reason about 3 weeks ago it dropped to 1345 and I nabbed it. I'd just upgraded my PC from a 1080ti to a 4070 ti and my headset is a G2. Before I used it I went through the painful 3rd party (talleymouse) setup of DFR and then tried to put it on, here's where I have some major complaints. 1. There were sharp, and I mean razor sharp and also very rough parts on all the plastic, especially on the strap parts. So much so that every time I put it on/took it off it ripped my hair out (I have long hair and I don't think women were ever really used to test your implementation) or cut my fingers. 2. There were SO many light leaks, on both sides, around the hinges. 3. Yes the visual quality and the more rounded rectangle FOV was exceptional, except the bottom 1/3 of the display that was constantly blurry no matter how I tilted or tried to adjust the headset. 4. Eye tracking was sporadic at best and would judder around despite my eyes being stationary. 5. It was never possible to get it comfortable and it is utterly horrible to adjust 6. That for the price you charge, you then 'nickel and dime' the top strap and the DMAS headphones I feel is unethical and disgusting. 7. It's nowhere near worth the price I paid, even the discounted price, let alone full retail price, so I returned it. Instead I tried - against my ethical and moral objections - the Q3. The quality is almost identical in visuals, smaller more scuba diver FOV but nothing to complain about. The fit is quite comfortable although not as comfortable as with a 3rd party headstrap / clamp. The colour passthrough is a game changer for kneeboard / texting and even using the WinWing MIPS in anger. The built in speakers are as good as yours but the fit, finish is much more like Apple rather than some cheap, crappy 'Droid phone - which the Crystal I got, I feel was an apt comparison. Yes, the DFR game me higher frame rates than I can get in the Q3, but I'm still getting >70 at altitude and a rock solid 36 down in the weeds with all the gfx settings on max, so on a 4070ti I can't complain. I'm now purely CPU bound on my 5GZ o/c 8700k and I expected that. TD;LR There is no way, no reason or legitimate benefit that means I could ever recommend the Crystal over any other headset on the market. The downsides are too many to compare to the G2 and the Q3 beats you on everything except a few pixels and a few degrees of FOV, and let's not forget it's a 1/3 of your price before you gouge on the add-ons. Oh, and on the subject of PIMAX in general... on two different discord groups run by Pimax I asked questions and never had a response. Despite being approached in the first instance, by members of your staff asking if they could do anything to help. Since I never approached or asked any questions to begin with, I falsely assumed that having then been approached it would seem you really cared about customer feedback and interaction. The two ignored messages and then the very curt and unhelpful ones I received from a senior team member left a very bad feeling in my mouth; another reason I could never recommend you. Hope that helps.

I say this as a loather of everything Zuckerburg, but Q3 is miles better than the crystal. I've had both this month (thanks amazon) and I really wanted to love the pimax (I HATED it) and hate the Q3 (I love it). The difference in quality of the image is virtually zero, yes the wider FOV in the pimax is nice but it's not worth the light leaks, discomfort of the entire headset and the cheap arse manufacturing of the headset (sharp plastic everywhere). Q3 is way sharper than the G2 and it has literally no sweet spot. I can glance with my eyes all around the cockpit and the gauges are sharp, in the G2 I'd have to move my head to each in turn. The Q3 is *almost* as sharp as the pimax - you'd really need to hot swap between to two to tell any difference. It's light, the strap is really quite good but I did buy a 3rd party better strap, and the sound is actually good. Not as good as the G2 but possibly better than the pimax. Plus, if you play the piano, you can get Piano Vision. Killer app. Best VR headset on the market; I loved my G2, but after trying the Crystal, I wouldn't swap even if you paid me. Huge POS in my opinion. Q3 is brilliant... and don't forget the colour hi-res passthrough. Game changer. I can text or use my ipad as a kneeboard without taking it off.

I had the Crystal for a week. I consistently got 40 - 70 fps. Unfortunately the headset I felt was appallingly cheap, too many light leaks, blurry at bottom edges and the headstrap fit was awful and ripped my hair out every time. But no, you don't need a 4090.

Couldn't disagree more. I don't know what settings you've got but this is 100% not my experience. I LOATHE Meta/Facebook and I never wanted to give them a single cookie, let alone money, but I used Amazon to 'try' it out and I was blown away. Not only are the visuals sharper than the G2 (in fact so close to the Pimax Crystal that I also tried a month ago and returned because it was no where near worth the money) but there is literally no sweet spot. I don't have to move my head to read gauges one at a time, I can, like in real life, just move my eyes to see them and keep my head tracking the bandit. Also, unlike the G2, when I look down by my hips to see the back parts of the side panels (like the refuelling switch in the F16) it's just as clear and sharp as looking straight ahead; in the G2 I had to physically tilt the visor down because everything was blurry when I looked at those panels. I don't know what settings these two have used, but out of the box it blows the G2 away.

Thanks Grimes. Never seen the 'type()' command before. Should have guessed but thanks for that.

That's all down to implementation, and I agree with almost everything you said - that's EDs job to actualise. My overall point was that after all the effort that goes into a mission or campaign design, having to remake the whole thing for each different type of wx to fly in (or day/month/time of day) is a waste of time and disk space. Having the ability to run a mission and not know the wx and time of day or season, brings another level of challenge and replayability to our missions/campaigns.

That would actually make things way more fun and challenging. You don't not fly IRL because the wx isn't CAVOK. You deal with the muck as it is. Something DCS pilots should really be doing too.

So I'm using the scripting engine env.log to write out data to my own little logging system. However I've never worked out how to make it handle anything I throw at it, or when it gets something I wasn't expecting, e.g. I think I'm going to get a string and its nil instead, or I think I'm getting a string and it gets a table. Does anyone have any code that can handle these kind of curveballs nicely?

At the risk of self promotion:

Can we get a confirmation this has been logged? We're posting bugs with no response from the dev team/community managers, so how do we know you've even read them?

I seriously cannot believe there are no upvotes... that's just crazy to me.

A question about the ready room; will we be able to play videos / gifs / audio as part of the briefing or is it just as bare bones as the current mission briefing (still text and static images)?

Only tried decimal point because I'm not crazy.

Thanks. The weird thing is that I can be sitting, hands off all controls. Not touching mouse or keyboard and I can look down and see the knob changing constantly. So if it's getting an input that it's not bound to, then I don't know how. I am wondering if I'm over the connected devices limit? I have two joysticks (centre and side), one throttle, 1 x WinWing PTO 1, 1 x WinWing PTO 2, 2 x WinWing PCR 1, 1 x WinWing TopGun MIPS, 1 x WinWing F16ICP, 1 x TM TPR Pedals. Is that too much for DCS to handle?

Odd because when I put a value in the ME of less than 1 second, it rejects it as a bad input into the box. And I wasn't talking about the miz I was talking about the image on your post that isn't valid.

That's interesting, never thought about keyboard bindings - I'll check. Thanks! EDIT - the RADAR Switch has no keyboard bindings.

Regardless of whether you pick a high cirrus or an overcast 4 wx preset, when you look at the table (env.mission.weather) the cloud 'thickness' is always reported as 200.

It's much better if you just get used to it. No human pilot you fly with in DCS is going to be locked perfectly solidly the entire time, plus winds change etc. If you're trying to get better at holding position, it's more about you than the lead. As long as they're not throwing it around in BFM then just learn to focus on them and make micro changes. It's just practice. If you need 1:1 training, DM me, we can go fly.