jaylw314

Quad Views ALWAYS renders the peripheral (low resolution) view on the desktop mirror. The whole reason it helps is by only rendering a small portion of the focus area. Since it never rendered the whole FOV in focus resolution, there's no mirror to display. What may have changed is that Pimax Play may have changed the Quad Views settings of Balanced, Performance and Quality. We don't have granular control of those, nor can we even see what they are. FWIW, as an alternative, mbucchia's QVFR layer still works, and you can still customize the resolution settings with it. Keeping the peripheral resolution above 40% or so is usually okay for recording or streaming

Thanks for the links, I reviewed them and they seem to refer to lighting when looking AT the environment, and it seems limited to only certain lights. AFAIK this is the first report I can find of this happening due to being NEAR a light. Granted, at it's root, it may be the same bug , but it's hard to imagine people would not have noticed blinding light doing hornet case III's before. I figured it was worth documenting the video evidence. As noted above, lens effects and other settings are off.

Do you have a link to specifics? I searched for a while and couldn't find anything specific

I tried searching to see if this has been a previous report. There were a couple references to this lighting issue, but minimal screenshots, no video and no tracks, so I'll file this as a new report. I noticed this while starting to work on night carrier landings. On the Supercarrier, if your eye position is within about 20 feet of one of the centerline lights, the light blooms in the focus area. This causes blinding flashing in the focus area as you run over the centerline lights in succession. Hardware - Ryzen 5800X3D, RTX 4080, Pimax Crystal Layers - PimaxXR, mbucchia's QVFR, recorded with the OpenXR mirror OBS plugin. Note that this configuration is required for videos and screenshots of the composited Quad Views rendering in the headset. The desktop mirror does not show the focus rendered areas. It's worth noting that I did see the same bug using Pimax's native OpenXR and Quad Views implementation, but the OBS plugin does not work so there is no way to obtain video and screenshots, but my experience was identical DCS - Stock F/A-18C Hornet Supercarrier Case III Landing mission. Lens Bloom, Global Cockpit Illumination, Volumetric lights, SSAO, etc all turned off (see screenshots) Video: jump to 25:18 Screenshots: Track: OpenXR Quad Views bug.trk Edit: Be aware that the track replay will not have proper player-to-AI ATC comms, since I use VAICOM. Also note that the mouse will be tied to the upper left corner since I use PointCTRL.

I don't know about numbers, but I went to school around NAS Miramar in the 80's, and those Hornets did a TON of training there. We had to stop classes every 15 minutes or so because of the noise from Hornets and Tomcats presumably doing pattern work. At least those Hornets got a lot of landings there, although a lot of them were probably A models.

That you've flown a lot of airliners?

If you review the internetly available (but not postable) NATOPS for the F/A-18C, the rationale for having NWS on during the rollout (and minimizing rudder use in crosswinds) is laid out in the landing procedures sections. What isn't in there, that is simply my speculation, is that the CG is much farther forward of the main gear than other typical aircraft, resulting in excessive directional stability once the main gear touches down. As such, if you've been tracking the runway centerline correctly, the plane gets yoincked into alignment with the runway when the mean gears land.

FYI, the "Save Cockpit Angles" function (usually default RAlt+Num0) saves all the snapviews, but that also includes your default head position in VR for each individual module. If you ever need or want to adjust your default position in VR for any one module, just use the Cockpit Camera controls (usually default RAlt+numpad) to tweak it the way you like, press "Save Cockpit Angles", then every time you press VR recenter, you should be there moving forwards.

Yeah, I think it was actually you who first mentioned that. Was I correct there was no reference, just something you heard?

LOL, sorry, I meant the two bolt heads on the RIGHT side, you can see there is one behind the other. You adjust your eye height to make those two line up. I've found it puts the HUD a little too low for my taste.

It's not a very big HUD. Where I sit, the gun cross is just out of sight above the top edge. I find that gives me plenty of room to see the bottom of the HUD where more of the important stuff is. If I need to see the very top, it just takes a little leaning forwards. Note that on the ground, this means the top of the HUD is just about on the horizon, since the Hog sits fairly nose-down on the ground. Once you're up in the air, the typical AOA will have the horizon going through the middle of the HUD. I've heard you're supposed to line the two bolt heads on the top of the HUD frame, but not sure where that comes from.

Could it be to allow for "towing" during refueling? It's referenced as a normal procedure, is this not done in other aircraft?

You don't need super fine controls--some guys do it with Xbox controllers. Don't try to hold a small deflection, just briefly tap the stick in that direction and do it repeatedly. If you need more, tap faster, don't move the stick farther, that just invites overcontrolling. And yes, 170 KIAS is super slow. Tanker speed should be set to 220 KIAS, which equates to between 280-300 knots groundspeed in the Mission Editor.

This looks like the KC10 from the Military Aircraft Mod, which is known not to work.

IIRC the DDI's in the Charlie ARE color displays, they're a weird combination of 3 vector displays (red, green, yellow) with a raster display (green) all packed in one CRT tube. Seems like pretty bleeding-edge stuff for the '80's. Anyone who's played vector graphics arcade games knows how bright and legible text can be compared to the scanned raster displays of the day. It's really only been in the last 10-15 years that LED/LCD can compete, and that's far past the age of the our Charlie Hornet's development.