RealDCSpilot

Who knows... Maybe the flight model got rejected by ED or Bell. Obviously, PC wouldn't share such information. On the other hand this would mean that quality control is in place this time, to prevent another debacle like with the Gazelle. Good for us, the customers.

Yes, the gimbal alone is a piece of art. The motors come from Alien Power System: https://alienpowersystem.com/product-category/brushless-motors/50mm/

@propelerThanks a lot!!! (x1000) Can you share info about the belts?

@propelerI really appreciate Maksim's mission to bring back FFB to flight sticks: https://www.youtube.com/watch?v=Ta0F9OSAW0o

The funny thing is, there is a LeapC.dll already in DCS's bin folder. So somehow Leap Motion support is already in there, maybe in combination with the Varjo HMD...

Auch sehr praktisch: https://www.digitalcombatsimulator.com/de/files/3126659/

Thanks for the info. I'm also eyeballing the Komodo cyclic, which seems to work the same way and i like that they are selling single components instead of a whole set like the PUMA system.

The interesting thing about pricing is that engineering can make it possible to reduce costs for the final product. For prototyping you always tend to overengineering, simply to make sure everything is stable and working, even if you get past the limits of a certain part. For production you try to identify those parts and if a bit cheaper solution is able to do the same job, you get the chance to lower costs and meet a certain price range. I find Bergison's approach is a true masterpiece right from the beginning, i've never seen such a feature-rich solution in a such compact form.

@Raven (Elysian Angel) Just found this topic and have some questions about the PUMA cyclic. For me it's still a bit unclear, is it self-centering or a friction based springless mechanism (move it off center and it stays there)? If the second is the case you should try the springless stick trim option for helicopters. The trim button has still to be mapped and used, because the implemented FCS functionality in the sim (force trim behaviour) will register it and apply it to the constantly calculated flight model. Very important for the Ka-50 for instance, because trimming tells the flight director's logic what your intentions are. In the Mi-8 with it's AP and the Huey with force trim only, you are also influencing the flight model with trim commands, but only in a much less sophisticated way. The correct procedure in all 3 of the good helicopter modules is always press and hold trim button when moving the cyclic, release when done.

Yeah, i posted it publicly because i want to read other opinions about price range.

@Bergison Great news! I'm really looking forward to this. Completely out of the blue and wishful thinking: A1) I would possibly buy a fully assembled and functional unit and am willing to pay up to 2.000 € for it. B) EU C) 1. support for mounts of Virpil/Fanatec gear and Forcefeel pads (Realtus Forcefeel, Gametrix Gameseat etc.) 2. integrated solution for VR motion compensation

If the stuttering starts, check the state of dedicated GPU memory (task manager or afterburner special option). If it shows nearly 8GB on a card with 8GB it means DCS is going to swap memory from disk to RAM to VRAM which overloads the CPU main thread. It just can't keep up the fps when this happens.

Ah nice. Thanks guys, it really was the fuze setting, must have messed around with it when i was first testing high drag bombs.

Thanks for the hint. I'm pretty sure i've tested all options, but i will test again.

MP session, i'm the pilot: F-14B drops snake eye and AIR in high drag mode, F-14A drops both in low drag, like standard Mk 82.

Hmmm, look below your thread:

My hope is, 2.7 is a big enough engine overhaul that will get this covered.

Also ran into this issue on a server yesterday, but it isn't caused by the module or the hotfix. Just choose another m-2000C slot to spawn correctly. In my case the known mp spawn bug was the issue, a player spawned before me in the same spot - another player spawned on top of him - result: both explode and their wreckage remained on the spot. After that i spawned in their wreckage and was stuck several meters deep in that mess. I simply choosed another slot and spawned in a clean hangar.

@IronChancellor At what daytime did you play the mission? As far as i remember, the shkval's locking capabilities are simply bound to a fixed daytime/nighttime cycle which doesn't make sense sometimes, especially at summer dusk/dawn. The trick for now is using illumination rockets above the target during dusk/night/dawn.

Just as a side note, i'm flying with a FFB stick and have the advantage of the FFB trimming system. My pedals do not support FFB and trimming during flight can get confusing after a while, because they will still work like the none-ffb trimming mode. That's why i disable the rudder trimmer option and prefer to hold the pedals in position if needed.

Thanks, will try. What i find pretty cool, the engine sound details, never recognized this before (wasn't flying at these low temperatures before). You can actually hear if something is not right, a mechanical rattling noise will appear if you raise RPM too early. Seems to appear on all WW2 birds.

Ahh, what a relief. Everything worked perfectly this time, managed -6° celsius with cowl flaps closed all the time and readjusting the oil cooler shutter at 0-20% to hold the perfect oil temp. Many thanks for pointing me in the right direction.

Alright, will test this. Thanks. Cyl temp never reached more than 180/190 if i remember correctly, even after a long wait for warmup with cowl flaps already closed. I will definitely check the oil temp much closer.

I have troubles with the engine dying or losing power on me during starts on a server with -4° celsius. I tried one with +2° without problems, but at below zero temperatures the jug doesn't seem to like it at all. If someone could provide a step-by-step guide and which one of the temp gauges is the most important here, it'll really be appreciated.

https://youtu.be/sZbR8wOLNJA?t=2157 Another good video, at minute 36:00 it perfectly explains the biggest issue, direct rotor control through cyclic input does not exist. If the Gazelle module would feature this correctly, like the other DCS helos, nobody would have a problem with it. We also wouldn't need to mitigate the problem with axis saturation, because if the Gazelle would feature correct rotor dynamics based on blade element physics it would start to act and fly just naturally by intuitive control inputs. @tugais I don't get from where you extrapolate your exaggerated depiction about my point of view about realism in DCS. For me it's very obvious that DCS features a very high standard when it comes to depictions of flight models. I only refer to what is there and what is not there in this particular module compared to already established standards of other modules. That isn't an opinion, it's a fact (proven so many times). You surely can have an opinion about a fact, don't mix it up please. As we all know by now, certain RL pilots share a very contradictory opinion about the same fact. In my opinion(!), it's a shame how this module was turned into a religious subject for the community by some people, splitting it up in "believers" and "unbelievers", "high priests" and "renegades". I, for myself, believe in physics and appreciate every simulation aspect that gets correctly modeled into any DCS module.