Maverick806

I have to disagree Even sitting at the correct height with the backup sight is vertically aligned, symbology can still get cut off. The video I posted earlier might start lower than OP's screenshot, but moves significantly higher than any screenshot in this thread and doesn't show any symbology disappearing at the bottom of the outer glass. Also the darkness of the hangar makes it easy see the circles where symbology is being shown. Here's another example with a camera well above where the pilots head should be, and the steering line doesn't have a gap in it

It's already being investigated

Looks like it was updated in the patch Fixed: RWR BIT logic improvements It seems to work if you press and hold the button

The F-16Cs radar can acquire targets when NO RAD is displayed on the HUD and HMCS The simplest way to test is: Enter Dogfight Override Mode Press TMS FWD to enter BORE mode Press and Hold TMS FWD - Note HUD and HMCS both say NO RAD. Hold the HMCS Cross over a target within range for a couple seconds. The radar will lock the target while you're still holding TMS FWD. This causes issues if you're trying to lock a specific target out of a group and the radar just grabs the first one it passes over This even works if your F-16 is on the ground (although the radar stops tracking immediately) F16_NO_RAD_Ground.trk F16_NO_RAD_MultiTarget.trk F16_NO_RAD_SingleTarget.trk

This is definitely not correct as is. The issue still happens even when you're sitting at the correct height, and it doesn't happen in the real jet: Looking at: \Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\HUD_AVQ32\indicator\Pages\HUD_Base.lua DCS treats the upper half of the large glass like it doesn't exist at all.

From Page 107 of the manual: To toggle between Automatic and Manual steerpoint sequencing, use the DCS Up/Down positions to place the DED Asterisks over AUTO/MAN data field and press the 0/M-SEL button on the ICP.

You should be able to accomplish this without editing any .lua files. There was an update earlier this year that lets you bind the _OFF versions of joystick buttons.

Kind of sounds like you might be looking at the wrong model. There's F-15E.edm that's been in the game for years (~188K Triangles) and there's Razbams F-15E_Suite4.edm (~1.1M Triangles)

I find side buttons on the mouse are great for show/hide pilot body as well as flashlight

Is the waypoint elevation at ground level?

Looks like its in standby mode

I would also really like to see the On Release bindings.

There was a similar thread about this: Deleting the Num5 binding from General - View Center didn't seem to work for me. However, binding something on the keyboard for UI Layer - recenter VR Headset fixed the issue for me.

Yeah, This would be a nice improvement. I also tend to bind show/hide pilot body to my mouse As a temporary work around, deleting the Mouse folder under DCS World\Mods\aircraft\F14\Input\F-14B will allow you to bind mouse buttons like other modules. However, the updater will reinstall that folder every time you update the game

I believe the Recenter VR controls got moved out of individual aircraft controls and into the UI Layer a few patches ago. I’d recommend checking if it’s bound to Num5 there.

@Deano87 There are multiple videos of real world hornets in this thread that show this doesn't happen on real F/A-18s. Just because you haven't encountered it doesn't make it any less of a bug.

While not game breaking, it can be a pretty annoying issue if you're flying at night and your velocity vector disappears in the gap. It's not really a glass or shadow issue, but more of a configuration issue. The HUD is configured in 2 parts: an upper half for the smaller piece of glass, and a lower half which only covers the bottom half of the large piece of glass. When you raise your point of view, you see a gap above the lower half and below the upper half. I've been running a modified HUD_Base.lua and replacing the values for HUD_lowerHalfGlassVerts with the values for HUD_largeGlassVerts. It makes this issue go away, but probably breaks integrity checks

They seem to be working for me. I'd recommend checking if you have a key bind for Exterior Light Switch - OFF which could be causing your issue

I don’t think this is a bug. IDM uses steerpoints 71-80 while L16 uses steerpoints 500-600 according to this thread

Hi Folks, Here's a track file showing this issue The track shows the below steps being used on a target at ~4200ft elevation. Steps: Select A/G Mode, and the Gun from the SMS page Put the pipper on the target and wait for the In Range Cue Enable Active Pause to make comparing before and after easy Pull the trigger and verify the rounds land close to the target Select and Unselect JDAMs Test accuracy again - The pipper is no longer in the same location. but firing the gun will result in the rounds landing in the same place The deviation between where the pipper is pointing and where the rounds go seems to increase with elevation. The deviation is pretty minor when your target is at 250ft elevation, but very obvious when the target is at 4200ft. F18_Gun_bug.trk

While playing in VR, if you enter the F10 Map, the lighting for the F10 map scene affects your vision when you return to the cockpit view I'm not sure how helpful tracks are for solving VR issues, but I've attached one anyways. To easily reproduce the issue: Turn on your NVGs Open the F10 Map and look up (the higher you look, the more obvious the issue is) Press F1 to return to the cockpit view You'll notice several bright spots in your NVGs that follow your vision. These spots are visible without NVGs and in external camera views - It's just more obvious with NVGs on. To get around the issue, go back into the F10 map, and look down at the ground when you press F1 to return to the cockpit LightingBug.trk

This also affects: AIM-9Ms (I didn't check any other variants) F-16C has the same issue

Hi, Can this be reconsidered? Here's a couple video examples HUD's in real hornets: (not a USN hornet) (screenshot at 4:18 ) Neither video shows a gap in symbology as the camera is moved up and down Thanks

Sure, a bit of distortion is understandable, but even in that photo, the distortion isn't hiding any symbology. I'm actually impressed by how hard it is to even notice the second pane of glass

If you raise your viewing position above the default position the symbology directly beneath the second pane of glass is not rendered. As you move higher, the amount of symbology not rendered increases. The first screenshot shows the Mach Indicator and 0* on the pitch ladder being cutoff. Second screenshot shows a larger section of the G meter being cutoff This does not happen to any symbology above the Mach Indicator when moving your head lower than the default position Screenshots and Track were taken in version 2.5.6.44266 HUD_Bug.trk