[dsjameyson]

I’m curious about the axis force settings.

To @bnfbmk, could you share what you’ve used for these axis force settings?

One peculiarity of the profile sharing system, is that it is restricted by hardware. And I can imagine some good engineering/safety reasons for it being that way.

I’m using the CLS-E stick, and what I’m trying to do is a bit conceptually different. Rather than directly reproduce/simulate the GA plane experience, I’d like to model a sort of “active sidestick” with control loading feedback, which references some of that physical experience.

[dsjameyson]

I put some more time in, and it does seem to be working well after the 1.12.13.0 update.

However, I am still seeing one minor issue, which is the flight director turning on and off, after using the autopilot. It’s actually not very bothersome, except on the 748, where it makes a loud clicking sound.

[dsjameyson]

Hey folks, I updated to MSFS 2020 1.12.13.0, and the USB rudder issue appears to be improved/resolved.

This was literally just a few minutes ago, and I haven’t tested anything more beyond noting that — figured folks following this topic would want to know.

[dsjameyson]

It’s definitely a valid question, to ask what the developers intend for the software.

As of right now, I’d call it a survey or framiliarization type of simulator, which is a valid and important niche to continue developing. It’s also an entertainment product, and focusing on the entertainment value is likewise important.

But are they intending to support study level add-ons, or commercial use as a certified training device, for example? That’s more getting into the area where control loading seems like a higher priority.

When tens of thousands of users want to pay for prettier buildings, thousands are spreading memes about gaping holes in Brazil, and several hundred are demanding an exacting simulation of the Goodyear Blimp… I can understand that satisfying a handful of specialized hardware owners isn’t at the top of the list.

Sure, I’d rather have the USB rudder problem fixed. But still… who wouldn’t want to learn a blimp, land it on their home or office, bump it into historic landmarks, and try to fly it through a hurricane?

[dsjameyson]

I’m am having the ever-toggling flight director problem in the 747, and the ticket #220 workaround (turning off “On overpower disable…) is not resolving it. This is with the beta CLS2Sim.

[dsjameyson]

To dovetail off airmanmd, and the others with the same problem, I am having this problem also, with MFG Crosswind pedals.

I looked at the external views while this is happening, and the external flight surfaces were indeed moving around.

I tested it with the cub planes (conventional tailwheel landing gear), and the effect is seriously significant there. You have to apply some rudder to counter the engine torque, and while the tail lifts up, the glitch is literally punching that elevator up and down. That’s the most extreme example I’ve found to demonstrate the problem affecting control of the aircraft.

[dsjameyson]

I can also confirm that the CLS2SIM and CLS-E Stick seem to be working now with MSFS 2020.

I had a few minutes to test it with the Skyhawk, and a non-hydraulic profile. I had to turn off the autopilot position setting option, the default minimum force of 20 is too low (needs a 2-3x increase to be usable, for centering and autopilot), and the turbulance effect needs to be dialed down… but that’s all just profile tuning, all the core functionality is there.

I will probably have more time available to work on profile ideas later tonight.

[dsjameyson]

During my experiment (in post #1898), CLS2Sim was reporting the connection as 90 events per second.

[dsjameyson]

I was experimenting with my CLS-E stick and FS2020 last night, with CLS2SIM set to connect to FSX, no forced vjoy mapping, and a profile with the X/Y axes disabled.

FS2020 loaded, but all the controls (keyboard, mouse, etc.) were locked out (this is on the opening UI screen). I alt-tabbed to CLS2SIM, disconnected, and everything unlocked again.

I started up a flight, and while in the render screen, I alt-tabbed to CLS2SIM and clicked connect.

All other controls locked up again (mouse, keyboard, trackir, etc.) but CLS2SIM was showing connected to FSX — the CLS-E stick had centered, and was outputting a ground/engine type of effect. Movement of the stick did not move the 3d cockpit yoke.

I alt-tabbed back to CLS2SIM, disconnected… everything unlocked again, and the system was pefectly stable for the remainder of the session (several hours). No problems at all when reconnecting the CLS-E stick as emulated USB.

[Author]

Posts