Callsign JoNay

Server side tracks are reliable for me. You won't have any in cockpit views though.

Edit: Actually upon further testing, the attack mode commands do not work.

Yeah the HUD and E-bracket are very accurate in DCS. I reference it all the time.

So follow up... I've noticed that almost the entire GRID category is FUBAR. Even when I jump in the back seat to enable the NAVGRID, and jump back to the front seat, setting things like coverage and scan rage after enabling the NAVGRID is a complete mess. Jester is entering all kinds of incorrect values in the wrong places. Anyone know if this will be fixed at some point?

Is it a bug? Bomb mode still automatically sweeps the wings between 55-68 degrees. Maybe it's supposed to be that way?

Are you using a datalink host to an E-2 or E-3? I have not noticed any Link-4 contacts blinking out of existence, unless I use a ship as a host. Then the datalink seems to blink on and off and back on again every 3 or 4 seconds for some reason.

Well 1 usually indicates True, so I assume there is some sort of radar correction mechanic implemented, but as to how it actually functions in the sim, I have no idea.

F/A-18C, F-16C, and A-10C II are all full/waitlist as of the date of this post. Still recruiting for: A/V-8B, AH-64D, F-14B, and LOTATC.

Can we get a binding for the red filter for the VDI? We have one for the HUD, but not for the VDI currently.

Yes, it's all broken again.

I noticed a mistake in the AIRIO PDF: After enunciating "enable grid" for three hours and having the software hear "Able grade, enabled great, enabled grade, enabled a raid, and Mabel grade" and anything you can think of except for "enable grid", I noticed in the Editor Tab that the correct voice command is "GRID ENABLE". So that was frustrating. You know what's even more frustrating? Even after telling Jester to "grid enable" he won't do it, even though he says "Roger". Is this a bug or is there some way to use the NAVGRID that I don't know about? Some other things that could make AIRIO better... If I STT lock a contact I am no longer able to change the scan range. It gives me some text in the upper corner that it's N/A since I have a target locked. That's pretty dumb. The RIO should be able to re-scale the TID regardless of using an STT mode. Can we get that fixed? Also, how do I get Jester to set Manual Mode for bomb delivery? I only see commands for "Attack mode Target" and "Attack mode Pilot". Having access to Manual mode is kind of important for GBU deployment. Is there a way to still have access to the Jester wheel while using AIRIO? Considering that it still has some obvious problems it would be nice to have a way to use the standard Jester wheel to augment it.

When I RIO for a human driver and I'm using a ground stabilized TID mode, or the NAVGRID, I don't just set it and forget it for so long that I allow my driver to fly us off the edge of the screen like Jester currently does. It would be a much appreciated quality of life improvement if Jester could automatically re-center the TID once in a while. Every 10 seconds or so would be . Also, it's annoying to me the player how I have to re-request Jester to center the TID/NAVGRID on the aircraft again every single time after I temporarily switch to an aircraft stabilized mode. Again, it would be much appreciated if Jester remembered that the user likes to have the NAVGRID centered on our aircraft and could appropriately re-center the view automatically when the user requests Jester to use the NAVGRID after using an aircraft stabilized mode.

Manually sweeping the wings back to 68 before pulling the handle out of the detent is what breaks the oversweep. Instead go to bomb mode, then pull emergency sweep out of the spider detent, pull back to 68, wait for the warning panel light to go out, and then you can pull all the way back to oversweep and push back into the detent. Edit: Actually you can disengage the lever from the spider detent from 20/auto too, and then pull it back to 68 deg while detached. Wait for the warning light to go out, then sweep all the way back. As long as you are disengaging the handle from the spider detent from an auto mode (bomb mode shows auto flag now), it will work. If you disengage from a man flag mode you won't be able to pull the lever back to oversweep after the warning light goes out.

Removing the UH-60, civvie traffic, and range mods, seems to have solved it (so far). Will continue testing.

No, I actually just updated to the newest drivers that came out a few days ago, but I still got a freeze afterwards. So I removed my UH-60, Civvie air traffic, and range mods, and I'm doing some testing this weekend to see what's going on to see if it's a conflict with the mods.

Wow good to know. It sounds like I'm not alone.

Good suggestions, I'll do some checking.

Well, I meant Tomcat mods, as in I haven't messed with any of the available Tomcat audio packs. But true, I forgot I had those Civi and UH-60 mods installed. Do they look like the culprit to you, or are you just pointing it out that I do technically have mods?

Another crash, another log, with a clean and repair in between this one and the last. dcs.log

I'm not sure about anybody else, but I've been freezing a lot ever since the last update. It's to a point where it's more likely for me to freeze than not before RTBing and completing a flight. The game freezes, and if I mouse click anywhere on the screen I get the "program not responding, wait for it to respond or close the program" window. I've attached my most recent log file. I see a lot of errors towards the end about invalid source params for wave files. Could that be the cause? I don't run any mods. Latest Open Beta. Any tips and feedback welcome. Should I try a repair? EDIT: This was supposed to be posted in bugs and problems... Sorry. EDIT 2: Changed the words CTD to Freeze since it's a more accurate description of my case. dcs.log

Agreed. That alone would be a huge quality of life improvement.

Well written post Exorcet, but I disagree with setting pre-flight parameters for what kind of targets Jester will look for based on mission objectives. That might work well for scripted single player story based missions, but not so well in PVP or PVE when the human factor can create situations that you never expected and can't plan for. I definitely would not want to see a system like that implemented. I'd prefer better base logic for Jester that can get the AWG to operate in intuitive ways that would be useful for most general situations.

I think you're generally not supposed to use flaps for field takeoffs. Try using maneuver flaps only.

It sounds like HB is extremely limited by the old/current API. If they make small tweaks to how the missile behaves in descent it has a big impact on other things. The new API can't come soon enough, because every patch it feels like a completely new missile.

Is it supposed to come up to 170k, though? Most mainstream sources say 100k ceiling.