grim_reaper68

Test on Syria give the same result. But if i drop the 2 RP35 before the critical point, the F1 seems to recover its attitude. depending on the position of the trim indicator, the F1 will start to roll to the right, and i was able to trim it to neutral fight again. The test with only the 2 RP 35 under the wings is OK. No trim drift.

I saw 2 video of real startup, once from a SA341 and one of an SA342, in the first they cut off the starter, in the second not.

Hi the aspect ratio for the TV is 1.26, so for 663 width you need to have 526 height. So the reticle will be round as in the Heli.

Good question, i will make some other test on different maps

If I remember correctly, once the turbine at nominal power, you could shut off the starter. But maybe i'm wrong.

I think I have a part of the answer: I made a third test, in calm conditions (static weather, no wind, the 2 first where made in dynamic weather, so there was some wind) and after 2 hours of flying, no drift of the roll axis. The AP works perfectly. A little bit of right aileron was present, but I think i cames from the BARAX and PHIMAT pods who have different weights. For a complete information, I was loaded with 2 Magic II, Phimat on the left, Barax on the right, 1 full loaded RPL201, and 2 full loaded RP35, so a very heavy aircraft on both first flight. On the third (no wind), I dropped the 2 RP35 about 20-30 minutes after take off. I just made another test, with the full load config all the flight and no wind. The roll drift cames back. As soon as the RP35 where empty (both lights on at the same time), the F1 began his deadly left roll after 5-10 minutes. So, maybe there should come from the 2 RP35. It's like they would emptying at different speed. PS: I didn't try it with only the 2RP35. I will make it later to see if it's the same.

Since the latest update, you still need to let the starter on, which for me is not normal, but maybe i'm wrong. So the turbine breakdown also disappear.

Hi. No overspeed, between 350 and 400 kts, altitude established at 12000ft. I took some screenshot, you can see the time line on the clock. Take off time on 12.00. On the first screen the trim indicator doesn't appear, but you can see that the fuel quantity indicator become visible. On the ohter one, the angle of the trim grows up, as seen on the input window on the left. No action on the stick at any time. I was just flying in autopilot, changing bearing with the bearing selector. Another fact is that the aileron didn't move in a left turn with autopilot. In the screen below the F1 has engaged the turn, but if you look at the left aileron, it's down. Hope i'm clear in my explanation. I forgot to mention that i was in SP. I've tested it twice with the same result.

Hi Just made a flight on Sinaï Map, and after a while, the AP rolls to the left. But the strange thing is that the trim indicator was full right and the aileron too, but the mirage rolls to the left... It seems to be the aileron trim who deviates slowly. I've maid a second flight and the rolling bug appears after 1 hour of flying with the AP. I joined the track. When i look from outside, the aileron are moving like the trim indicates, right up and left down. When the AP disconnect, they still stay in that position, but the aircraft violently rolls to the left. It reacts like if the tanks are emptying assymetricaly, but no indication on the tanks indicator. DCS F1 long flight AP bug.trk

Hi I have a problem with the TV visor, using the mouse axis on the warthog throttle. Verticaly it's ok, but horizontaly it don't work as well, the right side is the worst. When i try to move, it move a little bit, but then stucks. if i release the pressure on the axis and try again, it's the same. In the axis assignement widows, they works perfectly, and on other mods too. I tried different curves and axis limitaion, but nothing help. Did someone have the same problem?

Something strange I noticed is that i need to put the x position to 1980 instead of normaly 1920 to have the TV on the right screen. With 1920 I had a part of the TV on the main screen. So for the RWR too, with 3020 instead of 3040 (my screen setup is 3600*1080, 1920*1080 for the main screen and 1680*1050 for the second one).

No put this at the end of the TV/Indicator/init.lua file. For the name you can use LEFT_MFCD. And the same for the RWR dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("SA342_RWR") to add in the RWR/Indicator/init.lua file My monitor setup is as follows _ = function(p) return p; end; name = _('TEDAC+Camera+RMFCD'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 16/9; } } LEFT_MFCD = { x = 1920; y = 0; width = 560; height = 560; } TEDAC = { x = 2480; y = 490; width = 560; height = 560; } RIGHT_MFCD = { x = 3040; y = 0; width = 560; height = 560; } VCM = { x = 1920; y = 0; width = 560; height = 560; } SA342_TV = { x = 1980; y = 0; width = 1000; height = 789; } SA342_RWR = { x = 3020; y = 0; width = 560; height = 560; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center

In opinion, something is going wrong with the FM, When you hoover over the ground, you can put 100% of collective, the turbine load stays at 90%, but the Gazelle won't get higher. You must move forward with a speed over 20km/h to start having a positive vertical speed. All this time you have to push hardly to the right to stay on course. When reaching higher speed, above 20 km/h, the VS increase, but also the turbine load, taht goes over 100%. Maybe it's the ground effect that hold the Gazelle, or the FM must be corrected. Before the update, the transitionfrom hoover to flight was maybe good, but now it's hard the get out the ground effect. Second point, is the transition between flight and hoover, where the Gazelle litteraly sink to ground, even if you're gentle or hard with the collective. And it's more present at "higher" altitudes, where it quiet impossible to hold it on, and finished with a crash, or a good slam on the ground before standing in a ground effect hoover. Thats join to the first point, so I think, but maybe i'm wrong, that ground effect and vortex are exagerated, or the efficiency of the collective is undervalued. When I look to most of the videos of the real Gazelle, it's really more reactive that the actual DCS FM. Perhaps the truth is in the middle of the old and the new FM. I also noticed in that video, if you look at the feet of the pilot, he's not pushing so much on the right foot to stay in position. Hope Polychop will find the correct setup to have a marvellous Gazelle like we can see in the videos. I just want to finish by telling Polychop a big Thank You for the work they are doing on this great french heli. I can imagine that it is not easy to have the data and to set a perfect FM in DCS. Thanks to all the Polychop team.

Got it! I just forgot 1 line. The correct lines to add are those dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("SA342_TV") I named it SA342_TV, so in can have a bigger screen as the MFCD, specially with the AH64 where i have the TEDAC in the center of the screen. Works perfectly, with the RWR on the right.

Hi I'm trying tio export the TV of the SA342M (Viviane) on my second screen . Still not found it. I'm using this the try to have it, but not work yet. Did someone had more succes? try_find_assigned_viewport("LEFT_MFCD")

I agree the colours are a little bit too flashy

The lower (green light) is the engaged position. The upper is the active. It's like you turn your autohoover on, but it's not working because you're out of the conditions. Once in the flight conditions the CSV engage automatically. I think it is so. But maybe I'm wrong. You can fly with the CSV upper light on. And so far you're speed and vertical speed matches (less than X km/h and 1 m/s) the CSV will stop the Gazelle. It actually not works perfectly but made it. Hope I'm clear enough.

The CSV works on the cyclic, not perfectly but it works. It's quiet easier to use as before, cause it engages automatically when the conditions are met. Sometime it disengage itself just because you're adjusting the tail rotor to align the target. Maybe it comes from the variation of torque.

Personnally with that setup mine still roll violently to the right. I need to put the stick between 1/4 and the half to the left to make a smooth hovering takeoff.

Yes my cfg fixed the double display of the TEDAC.

I actually changed nothing in the TEDAC_init.lua. And it works fine. No :try_find_assigned_viewport("TEDAC") or other . Try maybe a DCS repair, so the apache lua files are cleared.

That's to know for the ALV. I will try it soon.

Hi here is mine _ = function(p) return p; end; name = _('TEDAC+Camera+RMFCD'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 16/9; } } LEFT_MFCD = { x = 1920; y = 0; width = 560; height = 560; } TEDAC = { x = 2480; y = 490; width = 560; height = 560; } RIGHT_MFCD = { x = 3040; y = 0; width = 560; height = 560; } VCM = { x = 2560; y = 0; width = 480; height = 480; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center It works fine. The only problem is that the TEDAC will stay on the second screen when you switch back to the pilot seat.

On my side I tried attack target of opportunity and engage air defence to my wingmen. They always respond negative...

Maybe they have to trim the grass a little bit lol. I accidentaly added static cows into a mission and the grass is almost so high as the cows. Either the cows are dwarves, or it's giant grass... lol.