Q-Ball

:megalol: That's a good idea! :pilotfly:

I feel like I've experienced this since the beginning (unable to trim when holding pitch with the stick). Since it's been fairly consistent for me, I was wondering if that was perhaps intended.

So I'm not sure if it was me or the beta update, but things appear to be working correctly with PseudoATC now. Thanks everyone for the feedback and sorry if it was a PEBKAC on my part.

The clients are definitely set to client. I wasn't aware of the F10 bug but I will attempt to re-test that tonight.

Thanks guys I appreciate everyone taking a look at it. I understand these things can take time to troubleshoot.

Thanks for looking. Should I DM them or is there a better way?

@Hardcard - thanks for the response. I have attached the original mission file, the mission file with MOOSE linked (I used ..\MOOSE_INCLUDE\Moose_Include_Static\Moose.lua) and my mission .lua script. VFA103MAINBASEV1.24.miz VFA103MAINBASEV1.24_MOOSE.miz VFAMainBase.lua

Hi, I am having a bit of trouple with the PseudoATC module. It looks as though I was able to instatiate MOOSE and the PseudoATC correctly via: pseudoATC=PSEUDOATC:New() pseudoATC:Start() pseudoATC:DebugOn() However, I do not get any F10 menu entry, and I also see the following in the log: 2019-06-02 03:32:51.022 INFO SCRIPTING: Error in SCHEDULER function:[string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:66433: attempt to index field '?' (a nil value) 2019-06-02 03:32:51.022 INFO SCRIPTING: stack traceback: [string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:6062: in function <[string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:6058> [string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:66433: in function 'PlayerTakeOff' [string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:66338: in function <[string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:66323> (tail call): ? [C]: in function 'xpcall' [string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:6360: in function 'onEvent' [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11> I am using the latest version of MOOSE from git.

Winwing, For DCS community reviews I would also suggest Spudknocker, since he flies with the Hornet a ton: https://www.youtube.com/channel/UC1Rsn65d8Qzy4T9A8435sYw

Have landed on a dead engine. It's definitely modeled.

I had thought I was doing something wrong as well, but it looks like this is as-intended. See here: https://forums.eagle.ru/showthread.php?t=237264&highlight=AIM-9+seeker The Jabbers video was pre-release, and so would not reflect the new (and presumably correct) functionality.

He did better than I would have, with my fuel gauge that low :joystick:

Man, after they missed December, I predicted it would probably come out while I was out of town. I was right! Oh well, extra few days of waiting before I can fly her. Just super stoked that the day is almost here!

Graywolf dropped a few solid Top Gun jokes, too. Great video.

I got sweaty palms trying to do carrier night landings. Good times.

Is that you, Mike? :megalol:

How is missing March 20th a "breach of contract"? There was nothing in the purchase agreement guaranteeing that we'd have it *by* March 20th. "Winter 2019" was an estimate, and so far they're on track to meet that estimate. Yet, if there is something that delays the release another few weeks, HB has no contractual obligation to those who pre-ordered.

Why can't the pod be functionally complete, but the shader set not be finalized? Heatblur updated the radar in the Viggen to improve the image and usability without altering the function of the radar system. I suspect that Heatblur plans to update the shader stack for the LANTIRN at some point in the future, but froze development in order to get to EA release. However, I think this week is out for release, at this point :doh:

Y'all got any more of them...Tomcats?

If only this forum had a like or thumbs-up button! :thumbup: I mean, I pre-ordered with "Winter 2019" as the only guide. Knowing how software projects tend to go, I set my expectations low (i.e. end of March). :unsure: But Cobra tried to be optimistic and said they were shooting for December. Then they didn't make December (something about the RIO pit not syncing with the pilot, IIRC) and the pitchforks come out. :protest: I'll be disappointed if they miss the March release, but if HB feels confident enough to put a RC into ED's hands for final GO/NO-GO (insert "Master Test" joke here), then a release is imminent, barring no show-stopping bugs. If HB is testing with Not At All Two Squadrons of Tomcats, then it seems like they are pretty confident in the module's stability. But if they said Feb 27th (which unfortunately, doesn't look like that's happening now) and things fell through, there'd be a(nother) riot. :chair:

This thread (and pretty much all of the other release date threads) are a prime example of why devs are loathe to give firm release dates.

What would the Internet be for other than to argue about minutiae on a very specific sub-forum? :smartass:

Good point there Never give up hope... even though the ED weekend newslatter didn't even mention the Tomcat BTW those sounds... I hope they're not postedited this time :hmm:

IIRC it's pretty much in ED's hands at this point as they are reviewing the module (last I saw). I'm sure Heatblur wants to get this thing out the door as much as we want to fly it.

I saw that, too (Jester VAICOM plugin). Does anybody have any details at all about that? I asked Jabbers on FB if he was using an early build of the Jester plugin and he said it was just the vanilla VAICOM plugin. So good to know there wouldn't be much extra setup required out of the box to interact with Jester (at least in a basic fashion), but I'm very interested in details on the Jester-specific plugin.