Britchot

The dots are there and the same, yes. I'm referring to the disappearing LODs for MiG-21 and F1 that I posted a video on. It no longer happens with Anisotropic Filtering OFF. With it set to x16 they still disappear.

The issues I recorded above are fixed in the version released on 19.12.23.

Just adding a video to show where some aircraft LODs disappear (MiG-21 and Mirage F1) before the spotting dot and others overlap visibility (MiG-19, AV-8B, F-5E, M2kC). Settings are DLSS on, Sharpening at 1.0, LOD at 2.0, and Antistropic filtering off. Posting the link as HD is processed (need to step out). You may need to wait a few for a clearer image.

Yep, verified I was in NAV mode in my recording, been flying RIO in the F-14 lately, just went to NAV by habit. I'll update the title and the OP, thanks for finding a workaround, though NAV should work.

Going back to verify it wasn’t operator error. Maybe I didn’t put it to NAV?

Conditions are a proper alignment completed with INS placed into NAV instead of IFA. In any of the flight modes, the HUD steering cue is frozen to one side of heading tape with the appropriate course indicated, even if it should be a line only. VSTOL mode waypoint, heading 083° with course cue at 058° but on the right side of heading tape when a left turn is required. NAV mode waypoint, heading 068° with course cue to the right indicating 057°, even though it should be just a line on the left. AG mode waypoint designated as target, heading 058° with steering cue far right still showing course of 061°, though should be a line slightly right, under heading. Makes it quite difficult to track during attacks: AG mode TGT designated, heading 117° with a steering cue right to 111°

It is used to draw virtual gun tracers on the HUD.

Thank you. The discord invite on the website at the bottom is invalid. However, I managed to search for the training servers and get connected that way.

Just saw this event in the newsletter and tried to track it down in the website's calendar. Is it still being held?

Since we're throwing personal opinions on the matter, I appreciate the realistic constraints, @AlphaJuliet. I'm sure we'd see a lot more of these, otherwise:

Your responses were lightning fast, thank you! Had to manually set 16000-32000 on both SSDs (indicates 32MB, now) and clean DCS for some Vaicom scripts showing red IC. After that, I was able to spawn in a Hind on the MP server and not crash. I don't have time to get a full flight in, right now, but it made it much longer than the previous issues. Thank you, very much @Flappie You, should get a raise. CS of the year, for real.

Link to .zip (over 5mb): https://drive.google.com/file/d/1pmf1evA42ky6NWQ-aWRf8ab00o5YCudy/view?usp=sharing dcs.log DxDiag.txt

Getting CtD with the Mi-24P almost immediately after spawning and MiG-21bis a bit later, maybe 5 minutes after spawn. Doesn't seem to happen on all MP servers. 203520 is the Hind and 025353 is the MiG-21. dcs.20221222-203520.crash dcs.20221222-025353.crash

Crews practice using pilotage and maps in the event their GPS is jammed.

I'm not sure what your reference is based on but a public video by C.W. Lemoine contradicts every bit of your statement. At 7:46, specifically. By limiting the NVG's field of view to a "soda straw" in the VR HMD, it will allow us to look under the green image to read the cockpit instruments, like Simultaneous' Pimax 8k or anyone on a monitor. The mods that have been referenced above all do this, and it's usable, it is something that should be in the base game.

I have been using these for years. However, it doesn't take away from the fact that I believe this customization should be a setting in the core game. This also shows why individual customization is required; there are numerous HMDs out there, it can't be a one-size-fits-all setting.

Just chiming in to place my wish for ED to make NVGs in VR more realistic, or customizable, to get to the level 2D monitors get with the ability to see around the goggles. This shouldn't rely on player modifications. In the meantime, I'll continue to mod my game every update, thanks to those players that have figured that out.

+1 All controls in VR seem to be locked out except for fire. I would also love to set these controls to a gamepad/joystick or even the mouse.

Any plans to add skins for 1-10th ARB or 6-6 CAV, which are still flying Delta models, today?

It'll be on the top row of the PCA once you go to rocket sub-mode (Weapon CMD FWD).

Depending on how long is "looong", a lot has changed. Like, a lot a lot. First! Revisit your control mapping. Some buttons were redone/named and previous controls were lost. Is your loadout without 530s? They cause an error if equipped with air to ground. Is TAS and/or RS selected in the PCA? Rocket External and/or Internal pylons selected (I believe they default on)? It's probably a typo, but to clarify, it is the "Weapons SystemCMD FWD". By reading your post, it sounds like you did everything correctly. There must be something small, like you said.

This is amazing! Thank you, so much.

Fixed mine to be 3-positions. This is the scripting I use for the flaps: MapKey(&Throttle, FLAPU, FlapsCruise); MapKeyR(&Throttle, FLAPU, FlapsAuto); MapKeyR(&Throttle, FLAPD, FlapsAuto); MapKey(&Throttle, FLAPD, FlapsSTOL); These are my definitions: define FlapsCruise PULSE+R_SHIFT+'f' define FlapsAuto PULSE+R_CTL+'f' define FlapsSTOL PULSE+R_ALT+'f'

Are you using the GUI or the Script Editor? In the Editor, I use MapKeyR for my switch from up to middle or down to middle. When I get home today, I'll post the code.

Thank you for completing this correction.