exil

Worked perfectly today in MP for me. Hope you can figure out the reason.

This is perfect, thanks! I played around with some random triggering before using it to spawn several sam threats randomly. But never thought about using it to randomize a whole scenario. Your version with various points in a mission is even better! Thanks a lot for the great advise and explanation!

[QOUTE] Blank Template Mission with triggers set for 4 scenarios all with a 25% chance of occurring, but no two will occur at once. i.e make a mission where there are 4 different scenarios possible, with one being chosen randomly and the mission start. Template Mission Download ________________________________________________________________ Is this template still available anywhere. Couldnt find any Info about IT since the link seems to be down?

Btw, flying and trimming with 3 x HOT3 works.

Check out this threat... http://forums.eagle.ru/showthread.php?t=172046 Polychop already corrected this behavior but we're still waiting for ED to put out the next update.

Patiently waiting for ed to bring the update but since it's pretty late now i guess we wont see an update this week...

Ahhh,,,i know about the effect, but didnt know its called blowback. Thanks for info. But i dint see a lack of blowback missing here. It generally occurs when passing translational lift. So in the gazelle i need to move the stick fwd to counter it during this phase.

It's working! Thanks so much Ciribob! The trick with deleting the lines in the export.lua's did it! Now off for some testing! Excellent work!

Sorry, must have missed that one: Tried to connect to the local server (127.0.0.1) and also to servers stated in this thead (e.g. TAW SRS Server 37.59.10.136). The connection was sucessfull on both servers. SimpleRadio Version 1.1.5.0 No Antivirus only Win10 Defender and Firewal. Thanks for the great support! Please find the screenshot, clientlog and export.lua attached. Export.lua clientlog.txt

Thanks for the quick answear! Sadly, i don't run a stable DCS version on my system right now. Only OpenBeta and OpenAlpha. I looked up the "dcs_variant" file and the only content in it is "openbeta" and "openalpha" acordingly.

Doesn't work for me either... I tried installing MS NET 4.5 (4.6 actually), looked at the export.lua, looked in the script folders as stated above and tried to configure the mic and speakers correctly. No joy at all. I still have three red dots with "no radio" and "unknown" in all three radio channels... Hopefully it will work somehow, cause this thing will be a gamebraker!

Don't wanna hijack this topic, but what is a "blowback from collective inputs"?

Awesome! You guys really know what customer relationship means! Thanks for the quick fix!!!

Good thing: I'm not alone...i thought it could have been some personal computer issues. Bad thing: We certainly have a bug here! Anyways, thanks for the replys guys!

Some more information: Problem also occuring in the L version! With full loadout, trimming fwd is not possible. With no loadout it works as it should. And i tried the following: I took a ride with a "no loadout" version. Everything worked fine. The i landed at a FARP and requested full loadout, took off and there was the bug again.

Hi, hope you guys can help! Description: Unable to trim fwd when loaded with 4 x HOT3. I can't trim this beast with the loadout stated. The nose pitches up all the time as soon as i put the stick back to neutral position. I tried to trim with both methods: Magnetic brake and trim hat. Nothing works so far. Eventhough the red cross (Right CTRL + Enter) states that i trimed forward as far as i can (red diamond in the upper half of the screen). Timming left, right and aft perfectly works. As soon as i change the loadout to zero weapons and even 2 x HOT3 i can easily trim as usual. I think the problem occured the first time after updating from 1.5.3. to 1.5.4. and also happens in the current 2.0.3. version. DCS Version: DCS 1.5.4.55584 and DCS 2.0.3.55457 Steam: no steam Map: Caucasus and Nevada SP/MP: SP and MP Reproducible: yes, anytime Step to Reproduce: Place a S342M anywhere in the Map and put it on the ground. Give it a loadout with 4 x HOT, IR-Deflector and Sandfilter. Take off and fly. Try to trim fwd and maintain a level flight at about 180 - 190km/h (was possible in former times with stick neutral just using the trim hat). Trim fwd as far as possible using the trim hat and put the stick to neutral position. Wait what happens. Then, change the loadout to nothing or just 2 x HOT3 using the same mission and A/C. Try the same procedure. Wait what happens. Screenshot/Video available: Trk attached Full Loadout.trk, No Loadout.trk Controllers: Saitek X52, 0 Saturation, + 6 Curves on pitch and roll axis

Same problem here, but with an non ffb stick (Saitex X52)! So the workaround won't work for me since i have nothing about ffb in my registry. Horrible times flying the gazelle right now...

I know what you're trying to point out here, but we don't want to figure out the magnetic heading. What we try to do is to get a magnetic heading corrected to a true heading (not true to mag) so we are able to fix a tgt on a map (since coordinates and maps are oriented to true north). In this case you have to ADD the declination. TRUE = MAG + DECL (6°E) TRUE = 360° + (+6°) = 006° If it were 6° W you still have to add the declination but with a negativ key signature: TRUE = MAG + DECL (6°W) TRUE = 360° + (-6°) = 354° Also google "declination/variation add subtract rule" or read it in this part of the wikipedia article.

Okay, i'll try but please be patient with me since english is not my mother language ;) Imagine you are south of the geographic northpole (where all the lat/long lines are meeting in the north) and your plan is to fly there. If you simply fly heading 360° you'll miss the northpole and end up at the magnetic northpole since a compass heading with 360° will allways show you directions to magnetic north. This is what we call declination (see wikipedia). The sollution is to add 5° in our example to counter the missleading 5° declenation. Your compass reading then would be 005° (360° + 5° declination). Now the earth itself has different local magnetic fields in different strength. This effect influences your compass additionally. This is called deviation (see wikipedia). This is exactly what you're reading when you look at the dev page in the nadir. Now let's say the local deviation is 10°. If we only correct our heading by 5° declination we would still end up 10° to the left of the geographic northpole since we didn't correct our compass deviation error. So we would also "miss" the geografic northpole because your compass will again misslead you by 10°. So in order to reach the geografic northpole, you basically have to head to 015° (360° + 5° declination + 10° deviation). Okay, now how do we use this information in order to solve our problem: The heading information you see on tv screen in the gazelles vivianne sight are provided by the same gyros that are supplying the compass...together with all the mentioned errors! So basically you need to correct that in the same manner as in our little example. Why did it then work in my example with the 10.6° correction factor? Easy! It was just a lucky shot. The nadirs deviation at Batumi is 6°. The declination in that region (simply follow a lat/long to the north) is about 5°. If you sum that up you'll get 11° as a correction factor which is pretty close to 10.6° Hope, it get a bit clearer now. Nevertheless, it really doesn't matter that much, since the MGRS gridlines and that lat/long lines differ about 1-2° on the map. But the more accurate way will be using the declination of the lat/long lines.

Guys, i figured out how it works! Ramsay, your first clue was right, but you forgot one important point. :smartass: What we get, if we look at the lat long lines is the VARIATION (also called declination). It's the difference between magnetic and geographic north. If you measure the lat long lines it gives you a variation of 4-9 degrees in the caucasus map, depending on your location (about 4° in the western part, about 9° in the eastern part of the map. To do that, just follow a lat long (NOT MGRS) line nearby your a/c location to the north. You'll get a heading of e.g. 355° which basically means a variation of 5° (360° - 355°) to magnetic north. NOW the Nadir gives you the DEVIATION and not the declination! The deviation is a magnetic compass error caused by local magnetic field differences of the earth. On the caucasus map it's somewhere between 6.0° to 6.3°. Now the simple clue to really get the right coordinates of your tgt is just to add both numbers (as we allready did somehow - with a little bit of luck). E.g. 7° variation + 6.1° = 13.1° If we put that in your formula it nails the tgt right on spot! How to get these numbers? Simple! Just measure the lat/long lines during a mission at your a/c location using the F10 menu and the measurement tool (as described above). Now just look at the deviation in the nadir and sum up the numbers. Then proceed along with the formula... After figuring out that the UTM method didn't work out (well obviously only where the lat/long and utm lines met) i tried this method and it worked everywhere and everytime. Hope, it wasn't too difficult to understand. If so, just ask and i try to provide some screenshots and further explanation.

Perfect!

I think you really need the map correction also. Maybe just try to add 10.6 instead of just the nadir declenation. Im really curious if it will work. Btw, i found out that the distance also matters. I tried my test from about 5.5k, and found out that i was allways about 200m right off the tgt from the helicopters perspective. I didnt matter if i tried it from north, south, east or west. Only after i messed aound with the declination and map correction i could really hit the tgt. I'm gonna try it from different directions and on different spots on the caucasus map to see if there are any other variables that affect the accuracy as well.

Ramsey, firstof all thaks so much for the hint about 1.5! For your interest, i tried a correction as you stated of 12.6 (5.6 declination and a map correction of about 7). My results were ok, meaning that i was about in a range of0.2 km away from tgt. Then i made myself a little excell worksheet and tried to tweak the numbers to be m0re acurate. I put 10.6 as a correction (5.6 declination and only +4 for map correction) and boom...nailed it right on the spot. Test range was nearby kutaisi.

Dear Polychoppers, i haven't had the chance to fly since the last three weeks. I tried the updated FM today...WOOOOOOW!!! What a great job gents! I was one of the first ones complaining about the old FM, but you guys really did it! It just feels much more to what i'm used in RL, turns are much smoother now a i have reseted all my axis to 0 again! Wonderful beast to fly and in my opinion the best and most realistic chopper in DCS now! Thanks for not giving up on tweaking it eventhough some mad voices came up in the forum during the initial release! I'm a really glad owner and a more than happy customer! Thank you so much!

I wouldn't call it a bug. The FM works as it should. But both of you are right. It should also nose-up a bit. But the greater effect is the flip-over to right or left, depending on a clockwise, or counter-clockwise rotorsystem. Maybe due to the hard dive (nose down attitude) the nose-up effect isn't encountered that much.