shadowborn

Hey @Lord Vader Okay, it's not the replay of that flight, but I managed to replicate the issue in air. See "ch47_gain_alt_with_engine_off.trk". Short flight where I tried to loop the ch-47. This led to a power cut-out (generator overload? no idea). I then cut the fuel pumps and engine levers to "off". Notice how I can keep flying for some minutes and gain altitude (from roughly 7080ft to 7740ft) at some point, minutes into the engine shut-down and could keep flying indefinetly. The helicoper only starts to fall as I eventually reduce my throttle/collective from full to idle, but even then behaving very strange for my gut feel. I also notice that after shutting down the engine after other flights, on the ground, the rotors take wildly different amounts of time to spin down. Sometimes it goes fast, sometimes it takes way longer (as also reported here). They seem to be affected by wind in general, but wind does not serve as an explaination why sometimes it takes minutes for them to stop, and in one instance, they never did (sorry, don't have a track file of that one). As for wind effect on the rotor blades in general, I have seen one instance of them spinning the "wrong way round" at a setting of 30kts wind in the mission editor; not sure if the gearbox on the real thing would even allow for that. I have a feeling that the modeling of air through a falling helicopter makes the rotors spin, and they spin so fast that the heli gains altitude and can fly seeming indefinetly with engine powered down. This is just a gut feeling of what may be happening in the replay. Which just can't be realistic, as that would be a perpetual motion machine I also attach "ch47_20kft_engine_cutout_weird.trk", if you want to take a look at that. Maybe you can explain to me what's happening here. It's just another flight that seems odd to me. I took the ch-47 to 20k feet (service ceiling according to google). Shortly beyond 20k feet, I lost engines (altitude cut-out? I don't think I ran out of fuel ...). Initially, all displays cut out except one without master caution lamp. Then they came back, cut out again, this time with master caution lamp. The co-pilot's display stayed on all the time. Then, the helicopter falls almost gentle like a leaf, I was able to do a soft landing from a fall from 20k feet despite the rotors being near standstill at various times. Helicopters with engine out (as per the display) and nearly no energy in the rotor system, tumbling over at some point, should not recover to falling soft and gently at only a few feet per second in my mind. Plus, again, the rotors behave weird. It spun up when I reduced throttle, and down (i.e. braked) when I increased throttle, almost as if the rotors are wind milling, but giving it thrust reduces that windmilling effect. Cheers! ch47_20kft_engine_cutout_weird.trk ch47_gain_alt_with_engine_off.trk

Hey @Lord Vader, wish I had one. I will fully agree that this was a stupid thing to do, but I didn't save a replay that night and started the next flight. So unless there is anything else but the last replay in %userprofile%\AppsData\Local\Temp\DCS, it's gone. Sorry .

Necroing a thread for a good reason: 14 years later, and I have had the same exact problem. SU-33, the virtual stick in the plane on screen would move like molasses, leading to extremely sluggish controls and massive over-corrections. I checked for any conflicting controls - none. No curves, everything 100% range, no deadzones. I cleared and rebound my axis controls multiple times. Eventually, one last try of clearing the category and setting everything up again AND then exiting the mission, and restarting it, solved it. edit: FC SU-27 has the same problem, can still replicate it with it. Also, the stick on screen only moves on the pitch OR roll axis, whichever input is greater on the physical stick. It never moves "diagonally". Looks like there is some weird controls config artefact for FC3 planes lingering somewhere.

Bought the CH-47 today. Flew around a bit. Landed. Cut the engine levers to "stop", cut all generators, battery. The rotors would go down to idle, but still spin at idle for several minutes. I even started pulling a bunch of circuit breakers. While I was doing that, the helicopter took flight (with everything still powered down), which is when I started recording the video. It rose to 7.500 feet when FINALLY the idle noise and the rotor blades stopped. Even then, during free fall, it ganied RPM and very briefly even gained a few feet of altitude (at 4630 ft in the video). Guys? This is ... wrong, no? I'm not going crazy, am I?

Hey. Unless I had a stroke of improved flying ability over night (unlikely ), the Apache is much improved by the latest patch. I can finally transition between flight and hover reliably with urgency, without either rising over the horizon like a buffoon, or with occasional funky things happening and then crash. So yeah - thanks, ED! Happy new year!

Revisiting this topic some weeks later, I agree: Winwing needs to get their act together. There is a new version of SimappPro, but it still wants me to disconnect the grip. I, too, had issues with the connector, with bent pins, and the cable is really short. It's a major hassle to take apart and I'd rather not. Here's hoping that someone from Winwing stumbles over this and reacts.

Meanwhile in 2024, after the big patch landed I set up two F-4 to fly a route across northern Israel and land back at Haifa, because I wanted to check out the map update while leaning back and relaxing. They landed in perfect formation, which I found kinda anti-climactic and somewhat reckless

Do you mean 1.8.22? I can not find any SimAppPro 1.82. It seems like a very high version number. I updated today and it gave me 1.14.6 beta. It has the same issue where it wants me to disconnect the stick from the base. Which I don't want to do, cause it's very fiddly to get the PS2 connector connected again with the too short cable inside the grip and the pins will eventually wear out. Fwiw, I tried downgrading to 1.9.29 (an old version I still had in my downloads folder). However, since 1.14.6 doesn't uninstall cleanly when installed over 1.9.29, I had to use Revo Uninstaller to wipe all traces of Simappro, then install 1.9.29. Pro Tip: DO NOT LET SIMAPPPRO UPDATE ITSELF, it will leave traces of the old version in the registry and mess things up. UNINSTALL the old version using "Add Remove Programs" in Windows, then install the new one. However, 1.9.29 has the exact same issue as 1.14.6 and wants me to disconnect the grip in order to update the base. I guess I'll wait for Winwing to get their act together in a new version then. Oh, and another pro tip: My Winwing stick and throttle work superbly on an USB hub. However, SimAppPro will NOT recognize them through the hub for the "Device" tab. Cost me another hour to figure that out. Quite a mess, this software ...

Today's patch change log for the AH-64D says: "Game Flight Mode disabled." Anyone know what this means? Was it an optional arcade mode that's been removed? If so ... why? Or is it just some pun on making the sim flight model harder?

Thanks! Not the answer I was hoping for lol, but good things take time.

Hey. I like to hop onto multiplayer servers for some "PvE" helicopter training. Any servers I tried, I can only select AH-64D without FCR. Do the server operators need to change something, or can I enable it? I read somewhere that it supposedly comes with the rearm and refuel-dialog, but I can't see an option there to mount the FCR ...? Thanks!

Photo Credit: Author (original post).

That's great news! I'm in Germany, too. Wrote to them about six months ago inquiring about shipping from inside EU, but they pretty much only responded "no we don't". So it's good to see they made that decision after all.

Oh, quite on the contrary: Since he also bundled two desk clamps and an MFD, he included way too many hex keys. Suspect there might possibly be even extra ones from the odd IKEA furniture item. "Too many" presented the same issues with proper hex key identification as "too few" though

Wow - thank you all so much!! You must be psychic or something I truly believed it was engaging, but it was the wrong hex key indeed. Tried a slightly bigger one, took some poking around but I can now perfectly adjust the tension. Also very glad to hear about the speed brake switch, this makes sense. I'm very happy now that the purchase does not have any defect - thanks!