Joch1955

It is really made for BVR, I have been practicing 1v1 against veteran SU27 AI and when fired head on at 30-35 miles out at 25-30k altitude, I am consistently getting a one shot kill 3 times out of 4. You just have to know it’s strength and weaknesses.

We are all in the same boat, perfectly happy with my G2 as well and no current plan to upgrade. No issues so far if you stay with 23H2, I installed all the 23H2 updates and no issue with WMR. As to how long we have, it is hard to find a firm answer. The drop dead date will be the final “end of service” date when MS tries to force everyone to update to 24H2. We should have at least a year to Nov. 2025. I have also seen a Nov. 2026 date. Based on the experience of 21H2 and 22H2, it could even be longer. There are also rumours that MS is planning to reverse its decision and produce its own line of WMR headsets which may mean a reprieve for existing WMR users. Bottom line, no one really knows.

I think part of the frustration players have with this map is that FPS seems to vary depending on what plane you fly. FPS in the F/A-18 is high and smooth even landing at Kandahar. I get similar FPS to the Nevada or Persian Gulf map. OTOH trying to land the F-14 at Kandahar is a stutter fest.

So another issue I have noticed is that the dot appearance seems to be very aircraft dependant. If I play some of the included F/A-18 SP missions, for example the AIM-7 practice mission on the PG map, enemy ACs show up as very black large squares easily spotted at 20+ miles in the air and against the ground. This is obviously wrong. However if I play some of the F-14 instant action BVR missions on the PG or Syria map, enemy ACs show up as very tiny greyish dots, again at 20+ miles (if you zoom in) but which are easy to miss and are hard to spot when against the ground. These actually look really good. As anyone else noticed or reported this? Tagging @BIGNEWY in case. This with a Reverb G2, pixel density 1.0, no Anti-Aliasing, graphic settings mostly high.

I re-tried the auto-throttle, works fine for me, but reminded me why I do not like to use it. It keeps the plane’s speed too low for my taste. The plane feels mushy and on the edge of a stall. I would rather keep it on manual, come in slightly hot at 145-150 and adjust the AOB on the final approach.

Yes, 1) throttle 75-90% and 2) gear down should do it, but auto-throttle is a bit finicky and sometimes does not engage for no apparent reason. I find engaging it on the downwind leg in level flight and stable speed around 150 seems to work best.

Jester has always been a bit hit and miss. Being doing a lot of landings lately, trying to get used to the weaker TF30 engines in the F14A. Sometimes Jester is quiet, sometimes he makes useful calls, sometimes he criticizes my landings…hard to know what the logic is. Jester is great in combat situations, but I wish he was more useful in landings, calling out when to break, when to turn on final, etc. Sometimes he will make calls when on “180” or “90” on approach, but usually not.

Picked this up recently, been flying around, landing at various air bases. The map is very nice, performance is on par with other maps. Terrain is very nice, especially the mountains. The air bases I landed at: Kandahar, Camp Bastion, Shindland all look nicely detailed. No complaints here.

Just a guess, but I think this has more to do with adjusting/tuning the “spotting dots” and spotting in general since the user experience seems to vary a lot based on the HMD.

I have a 5800x3D. Great CPU for gaming and still very high up in CPU rankings. If your MB is compatible, it or a 5700x3D is a great upgrade. There are newer x3D CPUs, but you have to change your motherboard and get DDR5 RAM which is a more expensive proposition. Important to choose a AMD “x3D” CPU and not a regular “X”. The X3Ds have a large internal cache, i.e. extra internal memory which makes all the difference in gaming. https://www.tomshardware.com/reviews/cpu-hierarchy,4312.html

I have been using a Reverb G2 for 2 years, still works with no issues, good performance and clarity, so no plan to upgrade for at least another year or two. If I was forced to upgrade today, I would probably get the Pimax Crystal Light.

Yes that is what I see on my G2. The issue is not just the spotting at huge distances, but it kills any SA of what the bogey is doing. The huge black dot stays the same size and hides the plane so you have no idea if the plane is getting closer, moving away or maneuvering right to left until the actual model pops into view very close by. With the previous 2.8 ‘off’ settings, when planes were within say 2-4 miles, there were enough visual clues, including engine smoke that you could tell if the plane was getting closer or moving away and within say 1-2 miles, you could make out enough of a shape that you could tell if it was maneuvering right or left.

Yes, this does not work. I never liked the 2.9 “improved spotting dots” which are too large and can be spotted from too far away. Personally, I turned it off, but now that does not work and we are forced to use unrealistic large dots even with the setting to “off”. I have no problem if some players prefer to use arcade like icons to make their game “easier”, but it should not be forced on the rest of the players. The previous 2.8 “off” settings, while not perfect was much preferable. This is on VR with a G2. Standard res so any AA, DLSS or DLAA.

Thanks for that, exactly what I was looking for. So the Mig-29 cockpit has been updated? Wonder why it was not mentioned in the announcement.

Well they updated the FC3 A-10 even though there is a A-10 FF module, so that is not a good argument. I am not really interested in speculation, this is really a question for the Devs whether anything is planned.

I see the Mig 29 was not on the list for updated cockpit/skins in the recent FC3 update and was wondering why? I searched the forums but could not find anything.

Thanks! Found the Docs. Second try was a lot smoother once I saw you can access all the Nav Info through the F10 radio menu. Very nice missions, very immersive.

I picked up the campaign, but having some trouble getting it going. 1-Mission 1: I startup , take off and then it’s not clear how to get to the engagement zone. The waypoints seem to go around in circle and when I look at the map in the Kneeboard, there seems to be a lot of “1” waypoints. I looked through the mission briefing, but not obvious what to do? 2-Mission 1: when I take off, a AI F15 closes up and sticks close to my right wing. Am I supposed to follow him? Not sure what that is about. Is there additional documentation that I am missing or is it just what is in game? Any help would be appreciated.

MR can be confusing. With MR on, you should always be running at 90 fps. If you cannot run natively at 90 fps, MR will generate say filler frames in between so that your eyes will always see 90 fps, even though the fps counter says 45. I would not worry too much about what the counter says, what counts is how it looks to you. The issue with MR in certain games is that the ‘fillers’ are noticeable and it looks ‘choppy’ or with micro pauses. That is usually not an issue with DCS.

The trim has been changed, so you have to get re-used to it, it took me a few tries to get back in the groove. It seems less mushy than before and seems to require less input for the same results. It also seems to react quicker than before which is a plus.

Been spending more time with the new FM and quickly getting used to it. Pitch and roll input still feels twitchy, but I am getting the hang of it. In flight, it does not feel that different from before. I have not had any issue with the landing gear. No damage through multiple CV/airfield landings, even one at 40,000 pounds. I did finally manage to break the gear on a CV landing, but I came in crooked and tried to recover instead of going around. If you land correctly, there does not seem to be an issue. I have not had an issue with regular CV/airfield takeoffs with half-flaps.

had a chance to do some CV/airfield landings, lots of changes to assimilate: -pitch and roll inputs are twitchier/more precise; -you can pull much tighter turns, I have to go easier on the break turn to get the same amount of Gs; -trim feels different. My old settings no longer work, it does not seem to require as much input as before. Trim also feels less mushy and you can feel the input right away. OTOH, the trim changes feel more abrupt. Not saying the changes are good or bad, but it will take some time getting used to and getting the optimum performance out of it.

Yes, as I recall because of the FBW system, the AC will try to auto trim to 1G when you are at around 250k? On final, gear/flaps down, you should be around 135k. Personally, I do not look at the speed, just the AOA indexer and that the FPM is the the middle of the E bracket. If those two are within the limits, you should be fine. The trickiest part IMHO is properly trimming the AC which can take a lot of practice and get right since it is more art than science. When the AC is properly trimmed, it will more or less land itself since the FPM will stay in the middle of the E bracket and you just need to concentrate on your throttle inputs. This is another very good video to understand the trim concept:

Win 11 23h2 is fine. Make sure to block automatic updates. This really pisses me off. No word at all on the HP website and they are still selling the G2 with no mention at all of the problem.

Good choice. I have had mine for over a year now and am very happy with it.