Whiskey11

Actually, if you have the ability to measure them, and pictures, that'd be awesome I need to go through this forum again as there were a lot of other great photos. The one above is about 17mm (2/3rd of an inch) which I got by measuring pixels vs the known panel width. The height and stuff is all wrong because I'm just kind of winging the assembly of it all.

Something is happening here! I purchased some of those interlock switches mentioned above, but I'm also designing the switch set from the ground up because its unlikely that interlock switch set will actually be the correct size. It might be, dunno, if it is, awesome! If it's not, I'll be prepared! I just got my 3D printer today, so still figuring things out. For instance, this button was printed as it is seen in the picture and as a result it didn't print very well on the bottom part of the press part because it was printing into air. The next one will get printed on its side with supports, so hopefully that'll improve the quality of the print!

I've tried a few aircraft, the F-14 is just the one I fly the most. The only non HB modules I've flown since the 2.7 patch is the Ka50 and Huey and they both have the same problem. I can try and get some logs later this weekend with other aircraft. Dunno, I haven't looked at the other people having this problem to see if the 9900k is the problem or not. I do appreciate everyone's time and suggestions! I want to get back to VR flying if I can... trying to avoid the inevitable recreation of the Warthog's Project's simpit but an F-14 instead!

New patch, still having issues. Attempted to disable Force DX11 in WMR for SteamVR, no change, dropped clouds to LOW, no change. This crash log is from restarting everything after having played in VR for approximately 35 minutes or so, getting shot down, and then crashing after trying to respawn in multiplayer. dcs.log

Depending on time of flight remaining until going active, and the bandit's movement, you may still get a hit. The AWG-9 will hold tracks for quite some time and try and extrapolate the aircraft's position based upon last known good information. So long as the missile goes active, and they don't move, there is still a good probability of getting hits when they go active. If they move significantly, it'll probably miss. If it is safe to do so, it'd be worth staying nose hot until they are active (or the tracks disappear) and then turn cold.

And another log, this time no mods installed, after a repair, clean, and deleting of FXO/Metashaders and terrain shaders folders... dcs.log

Unfortunately, not only did this not work, the problem is now worse. I get about 5 minutes of gameplay in the "first" time around, and now it crashes SteamVR without DCS generating a log file, same exact VRCompositor error in Event Viewer. UPDATE: Was able to play for a short while, just like before, SteamVR crashed on respawn. Attached new dcs.log dcs.log

I'll change it, but this hasn't been an issue in the past on this machine in VR.

Symptoms: If I start DCS "correctly" by opening Windows Mixed Reality for SteamVR before putting my headset on, I can usually get one flight, approximately an hour and change in length before crashing. Crashing is a SteamVR Crash (Microsoft Event Viewer shows a error in VRCompositor.exe), blue screen in Reverb G2. It's about 50/50 if I get a DCS Crash as well. If I don't start DCS correctly, it crashes immediately upon attempting to spawn into an aircraft. Crash is the same symptoms with same Microsoft Event Viewer VR Compositor error. Computer: -Intel 9900k OC'd to 5.0GHz -MSI Seahawk 2080, OC'd +100 on core, +600 on memory -32gb of 3400MHz -DCS Installed on 2TB Sabrent Rocket NVME -HP Reverb G2 Problem started after the first hotpatch for OB 2.7. It was fine right after 2.7 Launched. Playing with TrackIR, I'll get a DCS crash once in a blue moon, but can usually play as long as I can stand sitting without issue. Things I've tried: -Removing mods (ReShade, Shader's Mod for VR, LANTIRN Pilot ControL Mod, and an English Cockpit for Viggen) -Reverting WMR and WMR4SVR to the non-beta versions -Reinstalling WMR and WMR4SVR, including wiping all folders in %AppData and their respective installs -USB Selective Suspend has been disabled since... well.. forever. -Deleted previous Samsung Odyssey+ drivers (although I was using the Reverb G2 prior to 2.7 without issue) -Reverted Windows Updates to previous known stable versions -Reverted Graphics Drivers to previous versions -Played USB hub roulette with the VR headset -Monitored both CPU/GPU temperatures (neither the CPU, nor graphics card get anywhere near max, OC's are still showing stable in respective stress tests) -Removed Graphics Card OC (and struggled through the frame time hit) -Removed CPU OC (and struggled through the frame time hit) -Renamed Saved Games Folder for DCS Windows Event Viewer Error at time of crash: This error, in spite of the SteamVR crash, appears to be DCS Specific. I can play any number of other VR titles and other video games on my system without errors for hours and hours on end. Hoping this helps @BIGNEWY and team track it down so we can get back to some good ole fashion VR flying! Last thing I want to do is for this to force me to build the F-14 Simpit I've been wanting to build for a year or more! Please ED, please don't make me do it! dcs.log

I'm in the same boat as you. Doesn't matter if I have SteamVR and WMR for SteamVR set to Beta or not, still getting crashes when attempting to fly a second mission or respawning in multiplayer or pressing the F10 map, etc. It just seems to be constant problems. It is weird, because I did NOT have this issue when 2.7 came out, it happened about 2-3 weeks after that I can't play in VR. Stuck using Track IR and hating every living minute of it... Beyond irritated.

So, I think you have the same problem many of us are having. Out of curiosity, does your SteamVR crash with a blue screen in your Reverb? Can you check the Event Viewer for SteamVR related crashes? VRCompositor.exe is a common fault on my machine, I can play ONE mission, but if I try and load another, or respawn in multiplayer, the game will crash. If I play for a while and hit F-10 or Rearm/Refuel, it will crash. This has been a bane of my machine effectively since about a week or two after 2.7 came out. Only been able to reliably play in TrackIR which SUCKS compared to VR.

Help me out here, does the 1997 version of the AAA-1 which shows the dual row TID have any information on the tapes at all?

KEK 1-1 and KEK 1-2 on TALD mission, 09 May 2021, 107th Liberation Dynamic Campaign. - Photo Courtesy of Mr. Nobody (Mission was a success by the way, TALD's attracted Mosvka's attention while JF-17's and Viggen's destroyed the battle group!)

Maybe if we could get the UH-1N or UH-1Y as a more modern variant with it... sure. But if all we are doing is updating graphics, it'd better be pretty inexpensive.

So what you are saying is those of us in the Tomcat gang who already give Hornet drivers grief for needing three bags of fuel to get off the carrier deck are about to have more... err... fuel for the fire? I'm glad the F/A-18C's engines are getting looked at... before the Tomcat, when I was flying Bugs to scratch the naval itch, I used to hate the response of the engines behind the boat. Took a LOOOOOONG time to get comfortable with them. The F-14, even the -A has been a fresh breath of air in comparison.

Neither is sweeping the wings back to drop the nose and to pull BACK on the stick to get airflow over the rudders to rudder into the turn. And yet, some things work to quickly recover from a flat spin that aren't in the boldface and probably should be.

Without diving into BU No's for VF-301, these are all F-14A's from the late 1980's to at the latest, 1994 (VF-301 disbanded then), so hopefully, if we can find the relevant information, this would be something which could be applied to all of our F-14's except the early! Appreciate your response Naquaii!

I'll have to do some digging when I get up tonight (night shift things... yay!). I messaged Ward Carroll on his YT channel to see if he can assist in any way. I'd love to have all that information available to the RIO on one display if possible! Makes call outs much less awkward since they currently have to wait for it to cycle the information!

It's definitely early, some A-7's still on deck. The F-14's at the end definitely appear to be VF-301's F-14A's based upon the arrow on the tail (seen at 11:42). Patches on their shoulders definitely match. It could also be VF-103 which had a similar livery with the arrow on the vertical stabs but the patches don't look anything like the one on the crew's flight suits. Wikipedia says VF-301's first carrier landings were on Ranger in 1988 and it'd make sense to document that somehow. VF-301 was disbanded in 1994 and VF-103 stopped flying -A's in 1989, so regardless, our birds are newer. At any rate, I'm really quite curious about the TID and it displaying all that information. If anyone has details, that'd be awesome!

Mixture of pictures from myself and Nightwolf. SALTY 1-1 and SALTY 1-2 during the 107th Liberation Dynamic Campaign, 03 May 2021. (If you want to watch the full hour and a half mission: )

So tonight I was flying with the 107th during the Liberation campaign and during the debrief, one of the RIOs brought up a TID Upgrade which involved having both the range/altitude and bearing/course information displayed across the top of the TID when locked onto a target. I was able to find ONE picture of the TID Upgrade: And a video showing the information across the top in STT at around the 6 Minute 58 second mark. Does anyone have any information about this upgrade? This video is from around the 1990's (A-7 Corsair still on the deck of the carrier). Is there a way to get this to display like that in our F-14A or B?

I don't use reprojection or motion smoothing, no. Disabled in Steam VR, and in the config file for SteamVR for Mixed Reality.

I tried this out yesterday in multiplayer and didn't see a loss of FPS between on and off or any change in frame time. I was able to tweak both the in game settings and the shader settings so I could do .1 in PD and gain a few FPS, actually. The F14 Cold on the Ramp mission is my go to test mission, was sitting in the low 40s with 2.5, mid 40s with 2.7+shader mod and now upper 40s, low 50s with reshade. System is a 9900k@5GHz, 2080 OC'd open loop water cooled, 32gb of 3400mhz DDR4 with DCS on its own NVME drive. No MSAA but 16x AA and low shadows. Wouldn't mind more FPS because the deck of the SC drops me into the low 30s consistently in MP.

DCS is limited to two cores only. If you check task manager, you'll see two cores constantly maxed out. The reason you see CPU load at 20% is because none of the other cores are loaded much and drag the near 100% of the other two cores down. I'd still recommend OC'ing the CPU, since the game is CPU bound.