Kazputin

Hey all, I no longer have time for flight sims (sadly) and am looking to sell off my stuff. One item that will probably prove tricky to sell is my stick - it's a custom made (by me) FFB desktop stick. Sidewinder 2 base, CH Fighterstick grip. See images! It's got quite a heavy base due to the motors etc. Basically I took the grip apart, replaced the internals with a Teensy board, and then routed the USB cable out through the base. I also added an on/off switch for the force feedback that bypasses the sensors in the old stick, meaning that you can go hands off if need be, or turn off the motors to prevent the stick shaking around on your desk! The grip is held on with a screw and friction, and it doesn't have any yaw-axis anymore. In-game you have to bind x/y to the sidewinder, then bind the buttons on the grip separately (it shows up as 2 controllers). Happy to provide the source code for the Teensy board although it's basically a simple button matrix and there's nothing to really 'go wrong' with it. I used it loads when I was still flying, it's amazing for rotary stuff! This is an affordable way to get a force feedback stick but with plenty of buttons - the sidewinders only have about 4 so for anything more modern than the warbirds you quickly run out of buttons. This let me bind everything for the Huey, all the important stuff for the UH-60, and plenty for the Apache. Honestly, it was a lot of fun, but I just don't have the time. Would anyone be interested in this at £150, shipped in the UK? My wife would be pleased if it went rather than taking up space!

Yeah, so different button IDs for front/back seat, and I think you can have 2 routes stored at a time in the F15E, so it needs to know which to update. There’s a checkbox to save what you tell it I believe.

What aircraft are you in? An F15?

You can only load the tools internal format, so something you’ve saved yourself. It may be possible to write some code that translates from other formats, but that’s not supported yet.

Given the other ED helis have had this, it should be simple for them to add from the get go. I hope so at least!

Hmmm, weird. Best of jumping on the discord, people are more able to help there! I'm using the latest (1.4) on 2.9 with no issues. Hell, I've even got my dev version working fine. It looks like something didn't unpack or load correctly, or is in the wrong place.

Basic is actually on 1.4 now, added in frequency hopping for the ARC201. Have you tried deleting the whole folder from your saved games/Mods/aircraft folder, then unpacking again from fresh?

Is this on one of the armed submods? Default UH60L has no weapons. Wags has a video for the Apache, I’d expect it’s similar at least?

Yeah, the command bars just tell you whether to pitch/roll/change collective, they’re aids but not an autopilot.

Or open source it for others to take on?

I’m having a lot of fun by turning force feedback to 0 on the axis menu, setting “unsprung cyclic mode”, and then using SimFFB with the same buttons bound for trim and trim reset. Not ideal, but works well!

From Discord: ** PRE-RELEASE ** UH-60L 1.4 **NOT RELEASED YET!!** Scheduled Release is ~~Saturday 16.09.2023 at 10:00 Zulu Time~~ **DELAYED UNTIL FURTHER NOTICE!** Edit: There is a bug that cause the FM radio to not work. Changelog: **Fixes** System Fixes Fixed: ASN-128B would decrement from waypoint 0 to waypoint 69 - credit: Sniporbob Fixed: ASN-128B would always edit the waypoint being navigated to instead of the waypoint selected to edit - credit: Sniporbob Fixed: ARC-186 MAN and PRE mode would not match the position of the AM/FM/MAN/PRE switch - credit: Sniporbob Fixed: Key binding for formation light decrease had invalid logic preventing use - credit: Tanuki44 Fixed: Situation where key binding for Stabilator Auto - ON and Stabilator Auto - OFF could have inverted functionality - credit: Sniporbob Fixed: HSI course deviation bar only worked flying towards VOR, not away - credit: Sniporbob Fixed: HSI km readout digits could all turn independently of each other - credit: Sniporbob Fixed: HSI km readout digits would spin backwards when crossing from 9 to 0 - credit: Sniporbob Fixed: HSI displayed true north instead of magnetic north - credit: twanmal Fixed: Ground crew would only talk to the pilot through the pilot's door instead of other open doors - credit: Sniporbob Sound Fixes Fixed: Typo in APR39 sound file names caused errors to appear in DCS log file - credit: Sniporbob Fixed: APR39 was not properly classifying and calling out SAM threats with their SA number - credit: Lynx13D Fixed: Filename conflict caused certain Combined Arms and WWII Asset Pack vehicle sounds to be absent - credit: DD_Friar and DD_Sid Fixed: Exterior noises were only heard when the Pilot door was open - credit: Sniporbob Complete ARC-201 Overhaul - credit: Sniporbob -- Fixes -- Fixed: ARC-201 MAN preset could be changed by simply pressing the CLR key Fixed: ARC-201 display would remain on when function switch set to LD Fixed: ARC-201 frequency input was not left justified Fixed: ARC-201 allowed input of invalid frequencies Fixed: ARC-201 was willing to wait forever for user to input a frequency **New Features** Added: ARC-201 Self Test function (decorative only, does not check for damage) Added: ARC-201 editable single channel presets Added: ARC-201 single channel offset feature Added: ARC-201 Zeroize and Stow functions (be careful!) Added: ARC-201 SINCGARS frequency hopping mode, enabled by choosing FH or FM-M (SRS compatible) Added: ARC-201 hopset clearing, loading hopset from preset into working memory, storing to preset, and editing NET ID Added: ARC-201 sound effects (beep for self test and for certain hopset manipulations) Added: ARC-201 full implementation of single channel preset scanning and all relevant commands** (SRS compatible) **NOTE: Scanning feature REQUIRES use of the UH-60's "SRS PTT" key binding as well as selecting which radio the player desires to transmit on via ICP panel knob. The SRS key bindings should NOT be used to control the radio. Failure to use the in-cockpit controls will result in broken and unintelligible transmissions on any radio actively utilizing the scan feature.

Air-to-Air refuelling. I love flying the Huey, I find it to be the most stable to fly, although not tried the Soviet birds yet. I agree that the Gazelle is a bit bonkers, followed by the Apache - the Apache I mostly struggle with the trim settings, but having re-read the manual I'm getting more used to it. I like the simplicity of the Huey and can pull off some pretty aggressive landings now having had some practise! There's a littlebird mod in development, should be interesting to see how that flies. I have high hopes for the Kiowa, looks like it'll fit perfectly into my want for something slightly more agile/aggressive than the Huey, but not as bonkers as the Gazelle. Plus: buddy lasing!! Also autohover in the Gaz does work at the mo: get it fairly stable then hit the switch and you can hop seats, only having to make the occasional correction

Nvm, can see them in source code so I probably need to update.

Are there any keybinds for the HMD? On/off in particular? I couldn’t find anything when searching for AVS or similar…

This mod doesn’t have weapons. There are sub-mods (MH60, armed SH60?) that have weapons. This is just transport/utility.

This happens in the UH1H in-game- if you drop off the Burj Al-Arab landing pad too fast, you put negative G on your rotor and it makes a fast exit from the helo It doesn't like negative Gs!

Just chipping in - this is the thing that I hate about head tracking outside VR. HMD is super natural to use in VR, but my VR headset is big and hot and heavy. Sometimes I want to fly 2d. But with an ultrawide monitor, when I'm looking at the edge of the screen, the JHMCS is still in the middle. If the HMD placement was attached to the TrackIR X axis with a percentage difference, or a curve, then it would 'drift' to the edge of the screen when you moved your head that way - at least until it hit a limit at the edge of the screen. That way, you could set it up to move no more than say 30 deg to the edge of the monitor, whilst TrackIR allowed you to continue to move your head to look behind you (for instance). Effectively, a separate axis for HMD position based on input from TrackIR would solve this.

Yeah, same - just copy the 'Inputs' folder from your saved game directory and store it somewhere safe, any time you get something set up just right

Would be great to be able to bind axis to the lo/hi radar altitude knobs, and compass sync. That way I could start the huey from HOTAS/panels without having to click anything at all! This, plus the throttle axis fix. Loads of other modules have detents that work fine, why not this one...

If it's like the Huey - you have to use the Radio menu to go to Cargos and then select your cargo. That'll trigger a smoke flare on the cargo, and then you can hook it. In the huey the copilot calls out positioning too (e.g. left 10, right 30, in position, you are hooked, take tension, cargo hanging, take it away)

Apologies if this has already been asked - are there any plans to update how Force Feedback trim works in the UH60? I'll try and check this evening, but I think at the moment it's similar to how the Gazelle used to (up til this week) function, where hitting 'trim' ends up doubling your input because the position of the stick is calculated as an offset from the trim point, which is wrong for FFB sticks. Can post more info later if needed!

Thanks for the reply - I was in VR, I don't use hand controllers, and the FFB box was the magic switch! Need to spend more time flying the bird as currently way too heavy handed with the stick - used to the Huey which is a bit more forgiving, so I need to tune axes and train muscle memory...

Just logged in to try this out - sad to say FFB trim is still broken. I've tried with cyclic trim set to 'instant' and 'none': none doesn't set position at all (so stick just stays imitating a spring-centered stick), and 'instant' is the same as my previous post: I get in a nice hover, I hit the trim button as I would in the Huey, and can see the controls indicator immediately set my trim position and at the same time offset the current stick position from that new trim position, effectively doubling my input in both axes. This immediately knocks me out of the stable hover. As I said before: the trim position in 'force feedback' mode should NOT affect the actual cyclic input position. It just tells the stick to center in that new place. No calculation of relative position is required... Maybe I'm missing some settings somewhere, but certainly for me force feedback trim is NOT working, despite it saying 'fixed' in the patch notes... Disappointed! I will shortly have a second FFB stick available, so if I need to ship my current one to a dev for testing, please contact me... would love to get this fixed as the helicopter is otherwise great fun to fly... FOUND IT! I had to check the 'module specific force feedback' option in special settings. With that, instant trim, and gain curves set to zero - trim working as intended!! Woohoo!

Looking forward to trying her out tonight with the new FFB trim, thanks devs!