Phantom711

Two more pictures. Pic 4: shows the boundery from poorly to crisp shadows (righ/left) going through that golden wing on the carrier island (vertical) Pic 5: this also works on the top and bottom peripheral vision. Boundary again going through the golden wing there (horizontal) When I move my head around, I can see, that there seems to be a round part in the center of the screen, which covers the most part of the whole image, where the shadows are rendered poorly. I tried this now with Quad Views on initally but also turned it off. I tried with Oculus Link, SteamVR and Virtual Desktop (all with the OXR runtime). It happend in all of them. Everything else looks equally good through the whole screen...it´s only the shadows that seem to have a reversed logic. If someone wants to replicate the conditions: Marianns, CV heading ~030, Time 09:30ish, Date: 10/5/2024 (if that is the 10th of May or the 5th of October, I don´t know).

An issue that bothers me for while now is, that some shadows in VR ar blurry or sometimes flickering. At least for the blurry ones I have screenshot now. But the funny thing is, that this is not even consistent. If I move my head, so that said shadows are in my peripheral view, they become absolutely crisp. Just as one would want them. Pic 1: blurry shadows on the carrier island. Pic 2: shadows now very crisp in peripheral view Pic 3: my DCS settings (which I think could not be better with regards to shadow quality, right?) Specs: i7 13700 / 4090 / Quest Pro via cabled link at 500mbps

I am not very familiar with how it works in the other jets (i.e. F-16, A-10), but once you got the hang of the logic in the Hornet, it makes perfect sense. EDIT: Just watched a video how it works in the F-16. It´s not that much different from how it works there.

I just did some tests. As far as I can tell, if you designate a target via another sensor (i.e. HUD...thats what I tested at least), the MAV is uncaged automatically. This is also indicated on the MAV display top right corner. So maybe you have designated a target with HUD already and now pressed the CAGE/UNCAGE button agin and thus accidentially caged the missile again, which would look like it moves uncontrollably. Or also, if there is no heat source to lock onto it will go crazy. Another thing I´ve noticed: If you have designated a target with another sensor, and you now switch to the MAV screen, you have to UNDESIGNATE (NWS button) in order to be able to move the MAV reticle. Now I think the MAV should not be used as a poor-man´s targeting pod. You should acquire the target by other means first and only finetune the seeker head if needed. So, if you acquire the target with your own eyeballs: Assuming you are A-G mode, MAV selected, Master Arm ON - SCS forward to make the HUD TDC priority - make sure MAV is still CAGED, so the MAV triangle is on the boresight line on the HUD - point the triangle on the target as good as possible - TDC depress to designate target (missile is now automatically uncaged and more or less slewed to target) - SCS left to make MAV TDC priority if MAV is not perfectly locked on target: - NWS press to undesignate - use TDC depress slew to move MAV crosshair on target - closed crosshair on target -> SHOOT I have not tested this now, but the principle should remain the same with other sensors (TGP, HMD).

Uhmm...no. Turbo Mode might interfere with motion reprojection, it doesn´t disable it.

You are correct about the number of cores. I read somewhere, that disabling the 8th core helps. But it could also be, that it doesn´t matter which of the P-Cores to disable. In any case, it worked for me. What I can not recommend is to disable all E-cores as some videos on YT suggest. Severely decreased performance for me. You can do all that with just the Windows Task Manager, but then you have to do it every single time you start DCS. I use Process Lasso, so it is automated.

64GB RAM is certainly better for DCS but it is no guarantee to solve your issues with frequent stutters. There can be various reasons for those. I have a 13th gen i7 and for a while I had some serious issues with the game freezing for several seconds. What solved that for me was to disable the 8th core for DCS. As far as I know, 14th gen sometimes has imilar problems. Or maybe you have some conflicting settings somwhere between NVidia, OXR, DCS, Oculus.... Turbo Mode comes to my mind....

If the drift of your INS is a concern, then you must use certain methods to update the INS position. What you are suggesting sounds somewhat technically feasable, but I don‘t know if it is done like that on any aircraft. Never heard of it. Usually INS updates are done by overflying a known point or identifying one on the radar.

No…this is not how it works. When you are on the ground, wind is an airmass that is flowing over the ground. So that airmass is moving in relation to the ground in a certain direction and speed. As an aircraft in the air, you are simply within that airmass. The air is not „blowing“ against the surface of the aircraft really, the aircraft is being moved by the air, because it is within it. So a sensor would be useless. The aircraft systems calculate wind, by comparing the aircraft heading vs its resulting track. This works with GPS but also reasonably well with just INS (just less accurate over time).

On your picture in your marked red circle, you see, that there are 2 green lights. They are hidden buttons on the throttle axis. You need to assign one of them (because F-16 is single engine only) to something like „IDLE detent“. I don‘t know the exact keybind name. when you pull the throttle all the way back, there are another two buttons, assign one to „Engine cutoff“ or „Idle cutoff“ or something like that….

The new FFB base from MOZA will most likely also be compatible with TM sticks. Technically yes. I tried this for a short time, but it always felt like the TM stick is really not meant for that kind of stress. It didn‘t break, but I am sure it would have at least developed play over time. I went ahead and got the RS stick instead.

Depends on how you want to use it. Unlike the F-16, the Hornet has a center stick, so basically your leg is the armrest. I have a Hornet stick from a different company. I fly in a virtual squadron…so lots of formation flying etc…I never felt the need for a handrest/armrest. And yes…I also have an F-16 stick.

No such thing as "TMS" in the Hornet. You probably mean SCS (Sensor Control Switch). Nitpicky...I know...

@Muchocracker True…and it is much better now, I think…

Problem is, that you will find lots of outdated information out there on youtube etc on how TOO mode handles. It gets even worse when it comes to how to ripple JDAMs at multiple targets at once. Even though this goes beyond your actual problem here, this video might still give you a good explanation of how to handle TOO correctly.

If only the DCS keybinds menu had a search function… oh…wait a minute…

Well…then don‘t select A/A guns if there is multiple aircraft in front of you! Select AIM9 or AIM120 first. It doesn‘t even matter, if you have any on your jet. Now you can use boresight or whatever ACM mode you like with or without the HMD. After you have acquired the lock you can now select the gun.

Why would that be the case? You can ripple up to 4 JDAMs at separate targets (reasonably close to one another) just fine. There are lots of outdated YT vids out there…I only know ONE good one.

The G2 has some annoying flickering at 60Hz. If it doesn‘t bother you or you don‘t see it at all, then just go for the 60Hz. There are some claims out there, that refresh rates below 90Hz can lead to motion sickness. But again…if you don‘t get motion sickness at 60Hz…who cares. When I still had the G2, I also tried 60Hz at the end and I was about to simply accept the flickering, because everything was so much smoother at 60Hz (because I could match it with 60FPS most of the time).

Hmm…aber kein neuer Super Taurus…

Compared to the motion reprojection of WMR or Virtual Desktop, I find ASW the absolute best. It still shows some artefacts/wobble sometimes though. I‘m also on a 4090 and my philosophy is a little different: I leave ASW on AUTO, so that it‘s only acting as a fallback option for the 5-10% of situations, where I can‘t maintain 72FPS (Trying 80FPS/80Hz lately though). It‘s mostly just at airfields or at the carrier. Compared to the others, ASW is also very smooth at kicking in. However, I fly the F/A-18 almost exclusively (and the F-4 lately), so your use-case might be different.

What are your settings in DCS? Graphic settings and VR settings in DCS.

Und wenn ich das richtig sehe, ist da auch noch eine neue F/A-18 throttle im Anmarsch...

MOZA bringt wohl eine Force Feedback Base auf den Markt. Zumindest kursieren diese Bilder im Internet…hab aber keine Ahnung, wo sie ursprünglich herkommen. Also keine Gewähr meinerseits. Ihr könnt also aufhören zu basteln…

Ja…“Signaldämpfung“…hatte ich doch schon erwähnt. Das ist aber eben Vorteil und Nachteil zu gleich, da somit ja auch weniger Störsignale auftreten. Zumindest bei Flugsims hab ich selten meine Hand vor dem Gesicht, aber das kann bei anderen Games natürlich anders sein. Es kann also am Ende ggf so sein, dass das nicht für jeden Anwendungsfall passt, aber das wird man erst wissen, wenn das Ding auch auf dem Markt ist.