Mt5_Roie

While I won't get to test this until tonight. It would be nice if we had a JSGME version of this.

So I'm going to give you a quick answer: It's being looked into. There are things I can't discuss because of NDA agreements. As soon as we can tell you things, we will (as we've shown in the past).

Can you provide the mission file so I try to replicate it? I've landed on many ships soft and hard and haven't damaged much. So want to see if I can replicate it with your mission file.

Can't take any real credit since ED did all the work. But I would like to again thank you for using the template since it made it easy to replicate.

You've been busy again Hawkeye! Great list. When I get a chance I'll see if I can test them all out...maybe even make a video.

Just updated to 1.5.4.577288.170 and it seems ok. On virtual aeruobatic server now testing.

De-sync issues are still on-going. Working with ED to try to resolve them.

I'll test again this weekend with latest version. Will let you know. I know where to find you.

Bug template: https://forums.eagle.ru/showpost.php?p=2780295&postcount=1 Fill it out and post in Bug Report section.

Were working with ED on it. Since multicrew in heli's is new to DCS World...it's all groundbreaking work. Just takes time.

Please fill out bug report template: https://forums.eagle.ru/showthread.php?t=166931

Thanks for filling out the bug report template! I did a quick test tonight after I upgraded to 1.5.4.57114 and was able to replicate your results going to the virtual aerobatics server. I also had the same issue with the L model going to another open server. Wasn't able to test Mistral version. But I did host a server with all version and from when I was hosting I was able to connect to all three versions ok. So it might be only when you connect to another server that the issue happens. Either way, its reproducible and I'll start looking into it. Thanks.

Everyone is entitled to their opinion. I'm just trying to get people to use the bug report template so we can address them better.

All I did was ask them to fill out the bug report template and to be civil to each other. If you look at it from a programming perspective: a bug is reported. But the information I need to resolve the bug is somewhere in four pages of the thread and between people arguing back and forth. So that's not conducive to me finding the answers I need to resolve the issue. So again, lets keep the thread on topic and be nice to each other please.

In my test map I have KA-50, A-10's and some bombers - all AI. I was able to take all of them down without issue with the Mistral. I'll create another one with more A-10 and UH-60 this weekend and test again. Where you in 1.5 or 2.0?

Always fun to read these threads after a long day at work. So here's a couple tidbits. First, keep giving us bug report...don't stop. BUT make sure you use the template provided in the sticky for bug reports: https://forums.eagle.ru/showthread.php?t=166931 The reason the template was created is because I have over 20 years in software design and I know pin pointing issues is key to solving them. So instead of us having to ask you guys a zillion questions to get the information we need - the template get most of it for us. It saves us time and helps us resolve the issue faster. I happen to notice this thread doesn't have this template anywhere in it. As for the negativity, I would prefer if were all a little more civil on these threads. At the end of the day, we all just want to fly a fun helicopter. So what I like to do is for every minute I spend on these forums, I do about 10 minutes in the pit flying. Because after all, flying relaxes me and makes me feel good.

I have this series on my iPhone. It's a great documentary and shows just how much training real pilots get.

I was able to land ok without damaging the ship. It did slide a bit after landing. But no damage to the ship.

First of all...hard to take a person seriously when you have a Donald Duck avatar...that dude is hilarious. Am I the only one reading Fredo's threads with a Donald Duck voice? Anyways, nobody said the FM is finished. There are just parts of it that take longer to work on then others. Sometimes getting to 90% is good...but that last 10% can take twice as long as getting to 90% took. It's the same thing in this case. The current FM took a long time to get to, so making updates is going to take time. Also keep in mind that we also check everything with people who actually fly and work on Gazelle's. While it's easy to sit back and say something should do something, we want to get the pilots view and mechanical view of it. So it takes time, because most of the these people are actually working to protect their countries. We've documented all your concerns, and we'll work on them once we get the information we need to fix them. TLDR: Be patient.

Being worked on. It's one of those issues where ED needs to help out as well, since a laser effect more then just our module.

Should have been already done in the last update.

Please put all bugs in the bug report section and fill out the template.

I have the DK2 and the CV1, and I just use the default VR settings and turn the grass stuff to 0.

Please fill out a bug report in the Bug Report section using the template so we can get all the information to replicate the issue.

So just some history about how things get developed. We pour through lots of manuals to learn everything we can about the aircraft - this includes both flight and service manuals. This helps us determine when a pilot turns on X it's suppose to do Y. There is a lot of that even in a small helicopter like the Gazelle. Then the FM starts. We take any flight data we can find (and usually we have a lot before we even start) and work to convert that to DCS. DCS itself is a bit different then other simulators, mainly X-plane, in that the FM is programmed into the aircraft. In X-plane, you model the aircraft and engines and the real world determines the FM. In DCS you could have a C-130 with a FM of a Gazelle because that is whats programmed into it. So we program the FM. Now at this point, we need pilots who fly the aircraft to tell us if it feels correct or not. If it doesn't, we have to translate what they tell us into FM code. Not as easy as somewhat would think. We fix, and re-test, and fix, and re-test. Sometimes the pilots are busy and testing takes longer...so you get some gaps between FM tweaks. Currently we're working on fixing up the multi crew side of things. There are a lot of small things that need to be fixed. Also the FFB needs a bit of work as well and we are working on that already. We're also getting the snipers ready for their version, and working on the BO-105. So a bit busy. So, yes, we hear you. Keep the issues coming, but if you can please limit it to the bug report section so it can be classified correctly and so we don't have to search half way through thread to find it.