shrimpy_dikdik

I'm one of those looking to replace my G2 but I am not sure the performance without DFR on a 3090 would be worth the cost. Better visuals yes, but that isn't good enough for me if the performance is lacking.

No eye tracking means no DFR which means you loose the previous FPS gains in the original Crystal. It will have FFR but you can get that with openxr toolkit and the gains are very small in my experience, a couple of FPS maybe.

Deal breaker for me too. I will just stick with my G2 until the 5090rtx comes out and I upgrade my machine and see what is available then.

I've been on the fence for a while about upgrading from my G2 to a Crystal and one of the things holding me back was the additional standalone stuff that I would never need, paying for it with both additional cost and weight. So the news of this core version has interested me. It depends on how much stripped back it is, I would give it a pass if (probably unlikely) they also removed the eye tracking. The removal of the battery is of course a good thing but wouldn't that influence the comfort? Maybe requiring an additional counter weight instead? But a pcvr only Crystal for say €1000-€1200? I'd take that. Also read that some users face audio issues and that should be removed in a core version as the audio will not be handled by the snapdragon processor which caused latency.

I will try that with the openXR toolkit thanks. Have also noticed some odd shadow behavior with DLSS, namely flickering at certain angles underneath parked aircraft, and dancing terrain shadows similar to those dancing clouds we had about 3 years ago! In VR when you turn your head the shadows rotate. I loaded the V for Victory campaign and F2 viewed to one of the static balloons with a view over Dover and you could see very clearly the odd rotation of shadows, but with DLAA it's not there.

Using a g2 in VR I've never found a game where I've been 100% happy with DLSS and always revert back. With this update its OK but as others have said it does compromise the image. Is it worth it for a gain of 10fps over DLAA? For us to decide individually but at least we have the option now. Biggest improvement for me is the shimmering. Much much better in both DLAA and DLSS quality. Minor issue but disappointed that searchlights are still broken, although no one from ED has even responded to the bug and I guess they have bigger issues to sort at the moment. As a couple of others have said the Spitfire cockpit is looking fantastic! Hope the other warbirds get the same treatment soon.

<posted to wrong forum>

Here's hoping its fixed in the 2.9 update or very soon after, very immersion breaking. I dont understand how it worked previously as shown in recorded missions on YT and not now. What did they change and why? I've tried it MT, ST, N2 maps, Channel map, Causacus Map, high GFX setting, low GFX setting, extreme visability range, pretty much everything. Theres a user created mission that flies some B17s towards some lights using the Causacus map which is handy for testing although you cannot see inside the cockpit. You do see however the zoom effect work.

Seen a few videos of Sortie 2 and the searchlights look fantastic with the beams visible from some distance. I fly it ( and any other mission with searchlights so not just for this mission or campaign) and the visibility of the beams are very limited. The effect on the aircraft both in the cockpit and using F2 view are present but the beams draw distance is so small flying directly over them at 25k I still cannot see them without using zoom. Anyone else experience this, have the beams draw distance changed? It is reported in the WW2 assets bug but only 2 of us have commented. Night flying, low level raids etc are the reason I bought the Mossie and the V for Victory campaign. Sortie two is very atmospheric but I feel I am missing out on something videos have shown others experience.

If you watch the YouTube video of Sortie 2 from V for Victory you clearly see the beams from a distance searching for your aircraft. Looks great. That video was uploaded 2 months ago so has either something changed by the developers since then (and if so I hope they change it back) or is there somehow (doubtfully) wrong with mine and it seems your client or setup? It's something ED need to investigate and give comment on.

Also suffer from this. At first I thought it was a VR issue but tried with a user created test mission in both VR and 2d and its the same. You get the effect on the aircraft in cockpit view and external from a long way out but cannot see the searchlight beam unless you use a zoom. I just flew Sortie 2 in V for Victory which has many searchlights but I cannot actually see any beams of lights whilst flying at 25k unless using zoom, including ones I am pretty much flying over. Its very immersion breaking! All my settings are maxed.

ED said recently on FB one release does not affect the other. Of course what actually happens behind closed doors might be different.

I read somewhere that the mask isnt applied until later on in the rendering process thus is in fact useless at the moment. If true, hopefully it gets fixed soon.

This is exactly what I get in VR. Odd image in the mirrors and the map greyed out. Changing the livery through the ground crew fixes it.

I noticed greyed moving map and yellow and blue texture in the mirrors. Think it was OK on the quick start missions but not custom ones. If I select a livery, any will do even the existing one, the problem goes. I will try post a screen shot later. Edit: This is only since the MT patch.

G2 user with a 5950x and 3090. Can see the CPU timings improve from 10ms to 3.5ms or so going from ST to MT but my GPU is the bottleneck at around 20ms. Like many users on here no FPS improvement as GPU bound but still getting 45fps on the ground and 55 in the air. Worst 40fps on the ground in the Apache Mariannas Dawn Invasion quick start which seems a good stress test. Still very happy with the performance despite no gain with MT.

Not seen any improvement with a G2 5950x 3090 64GB system. Cpu frame times have halved (roughly) but even on complex missions I have always only been GPU bound so MT hasn't improved my FPS. Using openxr with FPS ranging from 35-55.

The Tornado is an aircraft dear to me having worked on them for 10 years so an obvious day one purchase for me. Hope other variants are offered in time as I would love to have a go with a JP233 which I think only UK and Saudi Tornados used. I imagine its one of the most frightening weapons to use in real life so should provide an exciting in game experience. Not sure when they left service it was before my time due to the land mine treaty.

Sadly ED did not let people know, or at least not me (unless unlikely an email went to my spam). By a sequence of conincidences I clicked on the BS announcements discord page and found that the winners were announced on 25th June. They are: COLMAR 1-1 Black-Sheep Crazypony SW-91 Midair Ugly 2-1 WeNSon Shrimpy (yay, that's me) It seems there was a cut of date to contact the BS team to claim your winnings and I was told to contact Obi at ED. Despite being told he would verify and get back to me ASAP I am still waiting for news if even my win is verifed or not. I do not know if anyone else is still waiting for the results, or if any of the winners like me haven't collected their prize but the lack of communication from ED doesnt exactly endear me to participate in future prize offering tournaments.

Often in MP I go out with x4 120c (or x2 and x2 9x) and a couple of HARMs. Kill a radar or two then switch to CAP duties. The MRM override is very useful to quickly switch between A/G and A/A. If my HARMs are spent then I change the A/G back to nav. Very simple. I no longer use the A/A manual button, although an alternative I used to do was have A/A mode enabled in RWS and use the MRM switch to easily go to A/A TWS. Set it up how you like on the ground or in the early stages of the sortie.

Mulitplayer is a challenge no doubt. When there's fixed wing about you'll not last long if you remain exposed. But surely that's the way it should be? Get on to comms and ask for CAP in your area. Personally I love the position, expose, fire, reposition, repeat nature of it whilst trying to keep an eye for those pesky fixed wings. Against ground troops it's no different to SP apart from the lack of IFF issues. It isn't nice when you fire on your own troops i admit, on SP it doesn't matter that much. On MP there are situations of single Manpads deployed in trees that are impossible to see which is also frustrating. Mark it, go back and clear is my only suggestion. I have had the Hellfire not firing a few times, not sure why. I've tried to replicate it but not found a common trigger. if they could get George to act a bit more like Jester, as in call outs, identifying targets etc (in progress already), even some of the wit too to make him sound less sterile then it would be an even greater module in MP than it already is. I

Play often on the Buddyspike servers and see a few others with Apaches too. No issues whatsoever.

Feel your pain. It's been a long time since I've had an opponent have to evade my missiles let alone hit someone. Must be around 30 shots now with no succes. Seems most people on here are testing against AI which is fine if that's their thing but seems to be little about multiplayer. My F14 sadly is now retired. Having a lot of fun with other modules however and if I see an F14 on my EWR I know I'm in for an easy kill.

Works well for me too. Important for me to get the trim nailed on first. I never had trouble before the update but this makes it a little more comfortable with just minor torque adjustments. There's a tiny little sway but nothing concerning.

What was the issue? Did thr missile keep track and was simply out maneuvered or did it lose track? I've played on GS a lot (having a break from the f14) and found I lose track on nearly all Phoenixs after only a few seconds flight with the target reappearing instantly. Happens on Buddyspike servers so not just GS server problem. If they are being out maneuvered then you must change the way you engage as its very different to 1 year ago. I wouldn't advise below 30k, over 45Nm and below Mach 1 on a hot target. And only 1 missile at a time.