Nealius

Alignment should be uninterrupted as I'm on the deck with parking brake set, however when I'm hooked up to the ground crew (rearming/ground power/air, etc.) I constantly get "hey what are you doing" despite not moving at all. Deck jumping bug back, perhaps? I'll try a ramp hot start and see what happens.

Dedicated server with Jester, cold start on the carrier with stored alignment checked in the mission. After WYPT01, all waypoints and special points are way off on the HSI, but work fine with LANTIRN. Flight time until issue noticed ~30minutes. In 2.7 I never experienced any INS issues with Jester+cold start carrier+stored alignment. Jester selecting IP for navigation. HSI shows IP at 205 for 25nm. Jester slaved to IP with LANTIRN, actual IP is 245 for 8.7nm. CCIP is also way off but that may be due to high winds in the mission. Will need to check with lower wind speeds.

Since the update/hotfix, has the IP/ST waypoints been way off for anyone else? Telling Jester to slave LANTIRN to the IP or ST puts the pod in the correct place, but the HSI is showing IP/ST 60+nm in a completely different direction.

Supercarier liveries are affected as well, which causes VR playability issues with the standard deck being way too bright and reflective. This was not the case in 2.7.

This is my observation as well. I only recall it happening to E-2s and occasionally Hornets depending on the livery. Now it happens to almost everything except unofficial mods like the Military Aircraft Mod, A-4E, etc.

I have an issue getting the P-3 to orbit when started from the ground. If an air start with the spawn point set to orbit, it works fine, but when flying a full flight path from the ramp to the patrol area, it ignores the orbit command and simply flies through the route and RTBs.

With the gyro sight properly dialed in it's easy to shred the 190's engine/fueltank/cabin and turn it into a roman candle in a turn fight with just a short squirt of guns.

On 2.7 I never really had problems with ball brightness, but since 2.8 I've noticed the ball itself suddenly pops into view somewhere between 1/2 and 3/4 mile, while the datum line is visible well out to 1nm or even more.

Oh my god how stupid of me to use "click" instead of "flick" /s End result is the same and the result is the only thing that matters.

I have to disagree with this point. IRL pilots click switches they can't see all the time. With the Tomcat's canopy specifically I recall someone mentioning they had to wedge a pen cap or something in there to reach it more easily.

They couldn't be raised to be more in-line with the canopy rail and out of the way of the other hitboxes? And on that note, more separation between the hitboxes on the two TACAN channel dials would be nice....

I wish we got a clickbox for it. In VR you have to either use the keybind (annoying), rely on Jester (limited), or rely on VoiceAttack which sometimes thinks you're ordering a McDonald's set instead of telling it to open the canopy.

Probably a business decision. There are five maps made directly by ED: Caucasus, NTTR, PG, Channel, and Marianas, in that order of release. Of those, the payware maps are NTTR, PG, and Channel. Channel is exclusively WW2 at the moment, leaving NTTR and PG where sales can be thought of as funding the development of things like new lighting that the majority of players are going to actually interact with. PG was and maybe still is a very popular map as well until Syria came out; I'd argue it sold more than NTTR ever did but that's speculation on my part. Ergo, logically PG makes the best test bed since it's payware (funding) with high popularity (more players to see and give feedback on it).

Forrestal being an HB module unrelated to the Supercarrier, I have no doubt HB is working on the bridal to work with their upcoming Phantom, and probably with the upcoming F-8 and A-7 as well.

Have a nice day. I don't argue with people who rely on straw man fallacies and insults.

"But while Pagan is not abandoned, it certainly isn't in common use. The A/FD lists it as "closed indefinitely". Not that the state of the airfield makes any difference to where the trees are though." So removing obstructions is okay because Pagan being closed doesn't matter, but reducing grass is not okay because Pagan being closed does matter? You also made a distinction between "abandoned" and "closed indefinitely" there, but in this discussion that differentiation is now gone?

I can confirm this as well. Single player showing proper Iranian skins, multiplayer client side showing default skins despite skins also installed on server+client:

Ah, that's weird yet kind of makes sense considering AA mode defaults LDDI to STORES, doesn't it?

I have a lot of good Hornet liveries that have been abandoned since the helmet textures were changed, causing the helmet to look awful. Is there any easy fix to this through a lua edit or drag-n-drop generic helmet texture files?

This has been the same for me for quite some months. Cursor/Enable will command Boresight with heaters, but will not with Amraams. Depressing cursoer/enable, uncage, and pickle button and the Amraam will not fire.

I can't seem to get the AZ/EL on the LDDI. It keeps cycling between HSI and SA pages. DCS-ism or me doing something wrong?

Then why have it at all, particularly with labeled parking slots? The tall grass is a wider-DCS issue. It's been requested that Channel and Normandy fields have their grass mown as well.

I get this in Syria and Marianas as well.

Dumb question after my first night flight in a while: Is there no illumination for the turn/slip indicator? I thought that would be somewhat vital given its prominent position (and standard/half-standard rate turns in CASE 3 Marshal), but the console/instrument/ACM lights don't seem to light it up. Normal or bug?

I've been flying a lot at night recently and the brightness/bloom of the mouse cursor is so massive it obscures the switch it is hovering over, making it frustratingly easy to click the wrong switch. It would be great if there were a brightness adjustment through the settings.