AggressorBLUE

Yes! The convergence of space simming (expands the market enough to hit just enough critical mass) and the maker-for-hire movement has allowed the cottage industry of simming hardware to flourish. Only thing we're missing now is an affordable force feedback stick

My ST arrived about 2 weeks ago and had some minor, albeit noticeable stiction. I used some multi-purpose synthetic grease I had 'laying around' that I use on my lawnmower spindles (AirTech/LubeShuttle G200 EP). It worked the trick and stiction is 100% gone, although now the friction level is less effective at the top range. Before I could just about lock the throttle completely at full forward, now full forward provides just a touch more than perfect (to me) resistance. Overall I'll take loss of stiction over loss of friction any day Interestingly, the metal box that enshrouds it has no function other than essentially being a dust cover and a stand to mount the assembly on if not using the WW mounts (or a similar mount like monstertech that takes advantage of the mounting points that WW mounts use); the WW based mounts actually bolt onto the throttle assembly itself; one could hang this 'naked' from their desk without any issue other than dust accumulating faster.

To me it's not even the mechanical aspect that's the issue. That thread has lots of great input there, and the assembly looks straight forward enough. It's basically "but this stuff / have a metal shop make you these bits / 3D print these other bits". Based on the documentation /posts/responses in the @propeler thread, that's pretty well figured out. The tricky part seems to be the electronics and/or finding documentation on how to assemble the electronics in a straightforward way. My head is spinning trying to figure out how to wire everything up, and what parts I'd need for the custom board or how I'd use an ODrive instead.

Quick bump on this: OP did you wind up getting said Laptop, and if so how did it work out? I'm looking at the Best Buy Sku of the Asus ROG Zephyrus G15: R9 5900, RTX 3070, and 16GB of RAM. RAM is my biggest concern; my current desktop has an older i5, 1070, and 16Gigs. It does 'ok' in DCS, even in VR, but I'm hoping this laptop is a bit of an upgrade, but not expecting sliders-to-the-max-in-VR performance. (to make a very long story short, I'm at a point in life were portability factors in strongly to my Simming/gaming 'needs'; so I'm moving away from a desktop build for this round. I plan to play other games when away from home on it, but then 'dock' it into my sim rig for DCS/BoX/MSFS)

Surprised and disappointED hasn't 'returned your calls'; this mod wouldn't directly conflict with anything they're doing (eg you're not releasing a flyable F-16...), and this instead builds on work they're already doing. To them, I say, Why can't this be sold alongside other mods on the main DCS site? I mean, over the shoulder go-pro videos on youtube showing folks flying Hornets off aircraft carriers with a battery of tablets and screens in front of them shows how serious this simulation can be. In any event, devoid of direct support from ED, my $0.02: -Plan to release a new major version each year (I'd even name them by year, eg. instead of MFCD 3.0, call it "MFCD 2020") -Essentially treat that yearly purchase as a subscription that gets a year of 'support' in keeping up with DCS updates as best able. -At close of the year, Version 2020 will still work, but will be locked to supporting whatever the last stable build of the year is(or at least that's the plan). If it breaks, V22020 remains broken... ...And V2021 will start the support cycle again. with a fresh round of funding to keep your work going. It's a guarantee that some overly-entitled folks will b***h about it, but I choose to hope that the more mature among us will 'get it' that constantly evolving software isn't free. And I'm willing to pay more than $0.02 ;) where do i sign up for the beta :D Sorry, one random question: why do you need to spend the hours of starting at matrix code? does the 'normal' lua file fiddling to export not work? I always thought the app was 'just' a WYSIWYG type interface to automate that.

soooo...not for the hornet then? *edit* Looks like you posted the wrong link.. For the Hornet specific app: https://itunes.apple.com/us/app/virtual-cockpit-f-a-18c/id1406855345?ls=1&mt=8

Given we've not heard any additional details, I'd personally pickup the Warthog now, and get the Hornet stick when released. The stick used on the WH is more universal, in that it has more buttons and an additional hat switch, and there's volumes of profiles out there already using it's button layout. Don't get me wrong, I'll pick up the hornet stick myself when it's released, but fame a pure functionality perspective, the F-16 style stick handle is arguably the "better" option. Having both at hand would be the truly best option though :)

Perhaps a decent middle ground would be a modification to the GUI, similar to how one can pull up the control position overlay (usefull in Helos for no FFB stick users).

There's a tanker variant of the S-3 Viking in the game that uses a drogue system. IIRC, Razbam had screen shots of M3Ks tanking off that on their facebook page. Not ideal, since those have been decommissioned. That said, modding the current KC-135 to use the drogue system would be nice (and accurate, as that's what France uses).

So, bumping this after a few months, because I want to point out that if the sensors can't slew to me thats fine, but if a cross-hair or indicator could be projected over where the pod or Mav is looking, that would be awesome. Especially given that weapons like the Maverick can "hunt" for targets, it would be great to "see where the camera is seeing". Only way to do that now is put the Hud over the right area. Yes, you can get a rough idea by looking at where the Lightning pod is looking, but it's more difficult with the Mavs, and not exact with either pod.

+1, having the same issue. Does it matter where this installs to?

Is there an up to-date-read me floating around anywhere that walks someone new to Helios through how to do a basic setup? My head is spinning trying to figure out what to put where...

While I appreciate the effort, I'm still really confused here. And yes, step 6 doesn't make sense. I also think something is missing from Step 2. Where are we supposed to copy those to?

Yup. The motto of the DCS series: Keep calm and keep on waiting. I'm biding my time by trying the new physics mod for the Light and Medium Helis in TOH. Done by the same guys that did the HTR mod for FSX (Hovercontrol). http://forums.bistudio.com/showthread.php?145171-Advanced-Flight-Model-based-on-HTR At least getting me back in shape.

Personally I'm looking forward to a simpler aircraft than the systems laiden DCS modules. A refreshing change of pace.