qman787

regarding the PlaneFM::weight_on_wheels logic. I don't think we need the complex logic to find out whether the plane is on ground or not. The weight_on_wheels could be retrieved by implementing the void ed_fm_suspension_feedback(int idx, const ed_fm_suspension_info* info) info->acting_force[1] is basically the weight on wheel. So, you don't need any extra logic for it. idx = 0|1|2 is the wheel index NOSE|RIGHT|LEFT

Hi Sérvalpilot, I've figured out what's wrong with the flaps handling. The enum assignment for flapsup/flapsdown is wrong. They have to be exchanged. flapsdown is to be = 145 flapsup is to be = 146 this is conventional DCS command enumeration. in the void ed_fm_set_command (int command, float value) the the flapcommand logic seems to be ok. but in the void ed_fm_set_draw_args(EdDrawArgument* drawargs, size_t size) drawargs[9].f = (float)limit(ACTUATORS::flapPosition_DEG, 0.0, 1.0); if ACTUATORS::flapPosition_DEG is indeed in degrees, then I think we have to divide this value by MAX_FLAP_DEFLECTION_DEGREES factor. This can be airplane specific ~20-25 degrees. And then we actually limit the animation value within [0.0, 1.0]. best regards, Valery

btw, thanks a lot for sharing the source code of your EFM, this is indeed very helpful for the community. Yesterday, I've made a short test of your EFM with minor code analysis. Pretty impressive, however there are some points I'd like to clarify with you (if I may): void ed_fm_set_draw_args(EdDrawArgument* drawargs, size_t size) relies heavily on the model specific animation arguments and may potentially lead to a memory violation if the size of drawargs array does not match the maximum required by the function implementation. I refer to the latest commit 91a5939f I see on the master branch. On this commit the index goes all way up to 1128 and there is no check if that does not accede the size of an array provided by DCS. There's something weird about the flap animation, seems to be reversed or something. I couldn't figure out what this is. The rolling behavior of an aircraft seems a bit unnatural. I didn't check the code, but it looks like the MOI about X axis is not accounted for. Please correct me if I see it wrong. Basically whenever we bank aircraft it acquires a rotational momentum about its longitudinal axis (in case of DCS's convention it is the X axis). When the stick is returned to a neutral position the acquired rotational momentum will continue to rotate aircraft until it vanishes aerodynamically or it is compensated by the flight-control system that applies an opposite momentum by commanding a required aileron/flaperon input. If this is on your TO-DO list I'd be happy to help you to implement that, however this isn't an easy task. The implementation of ed_fm_suspension_feedback seems to be missing. I'm not entirely sure, but I think we will fail to provide correct ground behavior and gear animation without this function. I believe the suspension mechanics is provided by DCS itself, but I'm not sure. overall your EFM looks very promising to me. Of course, and I hope everyone understands, that in order to achieve somewhat correct behavior of an aircraft the EFM is to be highly adapted to a specifics of an aircraft. There's simply no way to provide generic EFM to be suitable for all planes. So, in that case I'd recommend to all who might be interested in any further development of this EFM to actually branch out of main/master of https://github.com/IGServal/Basic-custom-flight-model-for-DCS-World/tree/main and NOT to fork from it. That way we will be able to merge the code and keep track of improvements and bugs.

Hi Servalpilot, the reason regarding the problem with landing gear you describe most likely lies in the absence of collision-segment objects. These must be present within the collision model of an aircraft and named properly e.g. FRONT_WHEEL|LEFT_WHEEL|RIGHT_WHEEL. Btw, the pivot points of those must go all way down to where the landing gears are supposed to touch the ground. I had the same problem a couple of days ago with my model until I figured out the cause for these explosions. Basically the absence of a properly build collision model results in all sorts of unexpected behavior. With the cold/hot starts this just results in the aircraft falling through the ground. I hope this will help to solve your problem.

Hello, I've been using my 2 monitors DCS setup for months with LEFT/RIGHT_MFDs exported on to second display. This works great for all mods I have so far. However, exported MFDs of F-16C mod seem to only being rendered/updated in F1 (Cockpit view). Whenever I switch to F2 (External view) the exported MFDs of F-16C mod are re-rendered (freezed). Unfortunately I was unable to find anything helpful in regard to that issue so far. Any help is greatly appreciated.