Penshoon

Unique issue for sure! You use no curves for the y/x cyclic axis I guess? Weird how it changes your input response. Hopefully the BIGNEWY can point someone at ED to this thread.

Think you are mixing up AFM with EFM, see https://forums.eagle.ru/showthread.php?t=122801 Guess it simply could be a misprint in the product page naming it AFM instead of EFM. Take what you will from it, I'm not here to argue. :pilotfly:

Have anything to back up that statement with? Why say that PFM is "generations beyond an AFM/AFM+" if what you say is true? I believe the AFM system was developed by An.Petrocich in the flaming cliffs release era who have since then went on to be IL2/RoF flight model engineer. No other module since has been released as AFM/AFM+ so I am a bit skeptical to why they would advertise the Gazelle using that description though. I speculated that the software suit was carried over with his change of employment.

Now I think i understand what Razorback means. He uses a ffb device plugged in to trick DCS into thinking he is using a ffb device and DCS then disables the artificial trimming method that aren't compatible with his non spring cyclic. But DCS has recently patched away this behavior as some people were complaining that they lost this artificial trimming method on their spring centered sticks when they had secondary ffb devices plugged in like racing pedals from a ffb steering wheels to control rudder. I thought that simply checking the force feedback setting box would force this behavior regardless of device used but I guess DCS makes a lookup on the main connected joystick device driver before applying this trim behavior? Maybe there is some way of forcing this through controls.lua file in saved games folder?

What play in center position? Without springs there is not center position in regards to forces? It should move freely throughout the axis? I use a FFB stick and spend 99% of my DCS time flying the Huey. 99% of the time I have force trim turned off as it makes flying so much easier and smoother. Having a force gradient limiting my stick motions is helpful in some situations sure but I think having a non linear response due to artificial trimming with a non spring stick would be much less intuitive overall.

Then why the need for trimming if the stick isn't spring centered? What am i missing? Trim changes the virtual centered position for the stick but as op's physical doesn't have any springs it has no physical force center anyway? Just don't use trim for flight like the real Huey is mostly flown? I just don't see any benefit of using the artificial trim without springs?

If you don't have any springs on the stick, why do you need trim at all? For autopilot systems? Don't the ka-50 and mi-8 have a setting called something like non spring, non ffb trimming in the special tab of the settings menu just for sticks like yours?

I'm just saying that the handling discrepancies between Uh-1, Mi-8, Ka-50 vs Gazelle could be explained by this. From https://forums.eagle.ru/showthread.php?t=122801 "Advanced Flight Model (AFM) and AFM+. An AFM uses multiple points of force application and calculation on the relevant flight surfaces. This simulates edge of envelope conditions well and avoids scripted behaviors as used in an SFM. This system also partially implements the aircraft's flight augmentation systems. DCS aircraft that use AFM includes the Su-25T. A further evolution of the AFM is what we term the AFM+ and this uses the same calculations as AFM but adds limited modeling of the hydraulic and fuel systems. Examples of AFM+ in DCS include the Su-25 and A-10A. Professional Flight Model (PFM). This is generations beyond an AFM/AFM+ and is based upon: • Use a wider array of wind tunnel tests CFD methods for aerodynamics parameters calculations. • A higher level of aircraft construction details for forces calculations. For example: our landing gear model includes individual kinematics of retracting/extending is used to calculate its movement, servo-piston forces, etc. In such cases, we truly use real lengths, arms, etc. This also includes such items as a realistic simulation of airflow along the airframe due to the propeller or helicopter rotor thrust. • Realistic simulation of Flight Control, CAS and Autopilot systems. • Realistic simulation of Hydraulics, Fuel, Electrical, Engine and other systems influence flight characteristics. • Unprecedented access to test data packs. This is combined with much more detailed and accurate accounting of the physical forces on the aircraft and airfoils. DCS examples of the PFM include the A-10C, Ka-50, P-51D, UH-1H, Mi-8MTV2, F-15C and Su-27 (in development) for DCS Flaming Cliffs, and the Fw190-D9 (in development)."

It's right on the purchase page:

Remember that the Gazelle is AFM and not PFM like the rest of the Helicopters in DCS.

Thanks for taking the time making the videos NixNB, hopefully Polychop can respond to this.

The rpm warning siren would only heard through the headphones so you wont hear it on youtube videos.

Google books? https://books.google.se/books?id=h3k-AAAAYAAJ&source=gbs_navlinks_s

PPPBoHjWSj0

Had troubles spawning the Huey on the aircraft carrier spot last night. The ship kept bumping up and down and flipped the helicopter before I had a chance to take off. Guess it's a DCS problem and can't be remedied in server mission? Anyway, I appreciate your work on the server Mirknir! The Skynet commands makes navigation possible despite F10 map and keeboard not being functional in VR, love it. Question, do rescue tasks affect the battlefield in any way? I like flying around and having things to do as a slick heli anyway but interested to know. PPPBoHjWSj0

That shouldn't be the case in forward flight right, only in hover?

No SLI support for VR, just fyi.

Its works beautifully! :thumbup: For convenience' sake I packed it up as JSGM mod format (if you don't mind) available for download here: https://www.dropbox.com/s/8o0814qcyba9bdt/UH-1H%20windshield%20wiper%20bounce%20by%20Tim_Fragmagnet.rar?dl=0

This look's great! Can't believe I haven't found this before, will definitely try it tonight!:clap:

I'd love to see the windshield wipers wobble as speed increases! xvKLcMwOg90

From testing on my system i get: CPU dependant = Civ traffic, Visib range, Shadows, Tree visib, mirrors GPU dependant = rest of settings

Have you tried the old view .luas? On low visibility setting with those you probably wont even see the city from the harbor as it limits rendering distance to just the closest buildings, shouldn't drop your framerate remotely as much as before.

Right control+Rshift+numpad keys moves your viewpoint. Not sure what the key to save the new position as default is but if you search in the keybindings for "angles" you will find it.

Glad it improved for you! Not sure if you have to replace it each update, don't think so. I have it installed with JSGME, I can upload a JSGME formatted mod tonight.

https://en.wikipedia.org/wiki/Bell_533 "The Bell 533 was a research helicopter built by Bell Helicopter to explore the limits and conditions experienced by helicopter rotors at high airspeeds under contract with the United States Army during the 1960s. Initial testing During the first phase, a general clean-up of the airframe was performed to reduce drag. New aerodynamic fairings were developed using fiberglass honeycomb sandwich for the rear fuselage, a cambered vertical stabilizer was developed which, in cruise flight, aerodynamically unloaded the tail rotor. The skid landing gear also had streamlined fairings applied to it and the rotor mast was replaced by a mast that could be tilted in-flight. The reconfigured helicopter was first tested in the NASA Ames Research Center wind tunnel, which confirmed the modifications had significantly reduced the aircraft's drag. The 533 made its maiden flight on 10 August 1962 at Bell's Fort Worth, Texas headquarters utilizing the two-bladed UH-1B rotor. Before beginning the program flight testing, the helicopter was fitted with a gimbal-mounted three-bladed rotor. Modifications to the flight controls allowed either rotor to easily be fitted to the aircraft in a short time, and the three-bladed rotor could be mounted on the gimbal or rigidly to the mast. In this configuration, the 533 achieved a true airspeed of 150 knots (173 mph, 278 km/h) in straight-and-level flight."