ColdFront_WI

Just found this thread, and just wanted to say an enormous THANK YOU! I hand-modeled all the knobs for my Hornet pit. It was fun and I learned F360 in the process, but I was not looking forward to doing it again now that I'm at that point with my 'Hog pit. Really appreciate the work and especially your sharing! CF

Nice! Have you tested if VAICOM works with your repaired version of the RadioCommandDialogsPanel.lua file? Your file seems to work for me. It gets the radio menus working, but I haven't done enough to be able to tell whether it's in auto mode. Will do more checking tomorrow. Thanks for working on this!

I've scoured and can't seem to find an answer...is it possible for DCS-BIOS to execute non-aircraft tasks? If so, is there documentation somewhere? Examples would be pause, active pause, toggle labels, recenter headset, etc. Thanks!

I am having some issues as well--possibly since the 2.7 update. In my case field ATC and JTAC instructions are being captured, but SuperCarrier instructions (Case I, II, or III) are not showing up. Anyone else? Thanks!

Hi, folks, I'm pretty familiar with the ME, and have done a lot of programming. MOOSE seems awesome, but as I'm starting to work with it (very basic test scripts to this point), I'm seeing some behaviors that I don't understand. First question is timing. I'm using the following code to spawn a group and then change its waypoint. If I schedule the SwitchWayPoint after delay it works fine, but without the scheduler it doesn't work: -- Spawn the group and make a group object local HS1 = SPAWN:New('Huey') HS1:InitRandomizePosition(true, 1600*5, 0) -- ~5 mile radius HS1:Spawn() local HG1 = GROUP:FindByName('Huey#001') -- Try to switch waypoint...THIS DOES NOT WORK HG1:SetCommand(HG1:CommandSwitchWayPoint(3,5)) -- But if I schedule the waypoint switch it works HG1:ScheduleOnce(5, function() HG1:SetCommand(HG1:CommandSwitchWayPoint(3,5)) end, {} ) I have also found that the unscheduled WP switch works fine if I put in a separate script that runs later, or if I it is applied to a group that is present at the start of the mission. What gives? Does it take some time to "finish" the spawn process, and it's simply not done by the time the subsequent code is run? Second, why do some things have to be within SetCommand() while others can be done directly: HG1:SetCommand(HG1:CommandSwitchWayPoint(3,5)) -- This works HG1:CommandSwitchWayPoint(3,5) -- This does not work HG1:CommandSetCallsign(3,2,0) -- This works HG1:SetCommand(HG1:CommandSetCallsign(3,2,0)) -- This works, but throws an error in the log I feel like there are some basic things I'm missing here. Any help appreciated, thanks!

Happy to help, glad you found it useful! Let me know if you have any questions as you build your pit--there's a lot to figure out as you go through this.

I have a bunch of Hornet STL files available, including the lighting knobs at my GitHub site. From the front page, go to STL Files --> Knobs. I think the ones you're looking for are named "...Quad," "...Triple," and "...Flat Sides." All are designed to fit 18-spline 6mm potentiometer shafts.

To other examples: Note indicates 11 comments, but only two show up: https://www.digitalcombatsimulator.com/en/files/3308226/ They are NOT the most recent, as I have seen the counter increase from 8 to 11 in the past few days, but the two comments showing have not changed. Note indicates 6 comments, but only one shows up: https://www.digitalcombatsimulator.com/en/files/3306757/ Have tried two (Chrome and Edge) and have tried an incognito window in Chrome to rule out a cache issue.

Glad to see I'm not alone! Thought I was going crazy...

Yes yes yes, a million times yes! WTF does flag 37 do again? Am I still using flag 19? Eric

I'm noticing some strange behavior with Uncontrolled / Perform Command-Start / AI Task Push on the Supercarrier. Hornet flights all set to "Takeoff from ramp." If I have both AI flights and a Player flights on the Supercarrier, the AI flights will normally startup, taxi, and takeoff with no problem...generally long before the player can finish startup procedure. If I delay the AI startup via Uncontrolled / Perform Command-Start / AI Task Push, the AI flights will start engines at the specified time, but will not taxi until the player flight starts to move. It is not that the Player flight is blocking the AI because 1) the AI can taxi just fine when starting as controlled without delay, and 2) this does not occur if there are two AI flights (and no player flight) on the carrier. Thanks, Eric

Hmm...the curved extensions are much trickier. You can't have them screw directly onto the base because the alignment most likely won't be right. It requires a separate collar for tightening to allow you to align it. Not sure my skills are up for that, but if I figure anything out I'll PM you with the design info.

Good luck, and let me know how it works out! See the update above about print settings and strength...I've had them crack when printed with 2x side walls and 20% infill.

UPDATE: I have found that these have a tendency to crack at the male threads when printed with my default print settings (two side walls, 20% infill, 0.2mm layer height). I printed a "solid" one yesterday...5 side walls and 100% infill and will see how it holds up. --------------------- Hi, folks, In case anyone is interested, I have published STL files for various lengths of Warthog/Virpil extensions on my Hornet cockpit GitHub site. This started because I was using a 75mm extension in my setup, but found I really needed a 50mm. I wasn't thrilled about spending >$50 (with shipping) and waiting until one was in stock from Virpil or another supplier, so I decided to design design my own, a few pictures below. I did find that the 36.0mm female threads on the initial design were very tight (may be my printer), so I created versions with 36.5 and 37.0mm threads. This are indicated in the names of the files. Let me know if you need other lengths...it's extremely easy to make others. Thanks, Eric 50mm design side-by-side with a 75mm from Virpil The female threads. I have made a couple of tweaks to the design since this was taken. Installed between WarBRD base and TM Hornet grip

Great looking design! For mine, I'm not thrilled with the wing fold. There's no push/pull...it's just a rotary switch, and the position between Hold and Extend toggles the push/pull. So to fold the wings after landing, the first left rotation pulls the handle, the second moves to hold, and the third moves it to fold. It's not great, but it works for as often as I need to fold/unfold. The parking brake uses a push-pull potentiometer combined with some custom Arduino code and a 3D printed collar to restrict the movement. The STL files are the "Hand brake..." parts on the GitHub page. you can also find the Arduino code that I use to control it on the site.