*SA342 BUG REPORTS*

[FragBum]

Manual typos:

 

I've been reading through the manual as I just bought the module and finding some errors here and there. Not exactly a bug but hey, it might help :)

 

Page 7: Top down view states the width at the landing skids it states 2.750 meters whereas right below it in the Front view it says 2.040 meters for the exact same measurement.

 

All in all, I'd really recommend the devs to have another go at the manual and include things such as basic helicopter operation, checklists, and also review everything that's written so far. I've found several typos (such as 'witch' instead of 'which') and numerous occasions of questionable grammar.

 

Referring to a training mission in the manual is unacceptable for subjects such as weapon deployment. The manual is supposed to be a reference which is accessible at any time (from a second screen or secondary PC/Laptop). In the current state of the manual, if I haven't flown the SA342 in a while and I find myself in a situation where in my group I'm flying the SA342 I have no way of easily getting myself up and running. The exact same goes for start up, which is even MORE important. This alone ensures the SA342 will NOT be a widely used helicopter as it CAN NOT be started up without either some luck OR excellent knowledge of the aircraft. And quite frankly, I do not possess either as I can not invest hours and hours of my free time in every single module.

 

Perhaps more importantly, this sets a precedent of which I'm unhappy with the quality of (some important parts of) the developers' module. This makes me doubt whether I'll buy another module of them again if the SA342('s manual) will remain in its current state. And that saddens me greatly, seeing a possibly excellent module being deteriorated by simple things such as useless manuals.

 

This changed from a Bug report to more of a Feedback post. I hope you can appreciate it and will address some of the things I stated as they're incredibly important for the module's success!

 

Closing, a module that can't be flown because of a lack of knowledge is a useless module, not because it is bad but because it is inaccessible to those who can not invest their lives into DCS. And there are many of us that can't.

 

Cheers Art

 

There you go I haven't read the manual yet. :thumbup:;)

 

 

<edit>

By that I meant it flies well. :)

Edited June 21, 2017 by FragBum
<edit>

[SnowTiger]

I'm curious why you believe that Training Missions are inferior to learning Weapons from a Manual ?

The Training Missions teach you how to use the Weapons Systems in the Gazelle quite well IMO.

 

I agree having a written reference can be handy at times but the systems in the Gazelle are so basic and minimal that there isn't much to remember (or forget).

I haven't flown ANYTHING in 4 months (needed a break) but I'm confident that I will remember all that I need to remember the minute I jump back into the Gazelle (and most other Modules that I have flown).

 

Anyway, give the Training Missions a go before you shoot them down (so-to-speak).

Then after practicing what you learn in those missions/tutorials and referring to that which IS in the Manual (typos and all) if you still have questions, there are many of us here that are willing and able to help you with ANY questions you may still have.

Plus you will likely receive the help you need rapidly in these Forums.

 

Best of Luck and Happy Flights friend.

[D4n]

No kill message in multiplayer when a missile (AIM-120?) hits me from above (rotors?).

[Devrim]

Hello from DCS World v1.5.6.

 

This is SA342_interior_weapon_Controls _SPEC.dds filename in Gazelle's texture zip file.

 

1) There's a space before _SPEC word. Is that intentionally or a mistake?

2) Gazelle code looks for "..Controls _SPEC.." or "..Controls_SPEC.."?

 

Thanks.

[D4n]

No kill message when killed by AIM-9M from front. What's going on Polychop? You even checking this bug?

[Drexx]

Most of my friends on my populatr multiplayer server still have the sound bug, when you die the all the sounds that were in the cockpit keep repeating themselves forever and ever, I have to COMPLETELY close out the game to get it to go away, it makes me not want to fly this really fun chopper.....

[myHelljumper]

Most of my friends on my populatr multiplayer server still have the sound bug, when you die the all the sounds that were in the cockpit keep repeating themselves forever and ever, I have to COMPLETELY close out the game to get it to go away, it makes me not want to fly this really fun chopper.....

 

I think PC said it was a multicrew bug and they can't do anything about it, ED have to fix it. I could be wrong tho.

[D4n]

Drex, it is enough to rejoin the server to fix the soundbug btw.

Even if ED has to fix it, why hasn't it been fixed since several months now? ED is meanwhile fixing other bugs which are (imo) less important...

[myHelljumper]

Drex, it is enough to rejoin the server to fix the soundbug btw.

Even if ED has to fix it, why hasn't it been fixed since several months now? ED is meanwhile fixing other bugs which are (imo) less important...

 

I don't know, not a lot of players are using multicrew so it might be low on their list.

[D4n]

Other bug, when landing Gazelle really softly it still bounces hard right-left-right-left-BAAAAM tailrotor breaks off.

[birkenmoped]

Other bug, when landing Gazelle really softly it still bounces hard right-left-right-left-BAAAAM tailrotor breaks off.

 

I think you should be more specific.... Which DCS version? Offline or on which server? Is this happens every time for you? Or only with/in multicrew? Or only on tuesdays?

 

This is no normal behavior and this not happens to me for a while... (only when I'm "learning" this modul)

[D4n]

stable DCS, online, when landing on a very high and flat mountain (as high as when I cannot hover without losing altitude, but when I fly in any direction slowly, I can still climb). Happens quite often, bouncy bounce, black screen (high G?) and tailrotor broke off.

[Raven434th]

Master arm switch ON/OFF button doesn't stay in on position when mapped to joystick. I use a modifier plus joystick button combo to enable this function but it immediately returns to the off position when released. I have the exact same button setup on the black shark which works as it should. The same thing happens with the Master on/off(autopilot) switch, (the one that lights up on the panel). However the master autopilot switch on the stick(why are there two autopilot masters btw?) works and stays on in its selected position. NOTE...both these buttons work as they should when using a mouse click to operate them. which is really strange.

Edited July 20, 2017 by Raven434th

[Gizzy]

There are various mappings in the Gaz.

 

If you map that control to a DX on/off toggle switch it will work fine. i.e. If the DX is ON the switch is ON, OFF it's off - if that makes sense. If you have TMWH put it on a toggle switch.

 

A momentary DX switch such as found on many joysticks, TM MFD's and some button boxes will only activate the swtich when ON ie pressed.

 

The keyboard command works as a toggle on/off so workarounds can include TARGET or any other software that maps keyboard commands such as found on some keyboards, mice, or Joy2Key AutoHotkey etc...

[Raven434th]

There are various mappings in the Gaz.

 

If you map that control to a DX on/off toggle switch it will work fine. i.e. If the DX is ON the switch is ON, OFF it's off - if that makes sense. If you have TMWH put it on a toggle switch.

 

A momentary DX switch such as found on many joysticks, TM MFD's and some button boxes will only activate the swtich when ON ie pressed.

 

The keyboard command works as a toggle on/off so workarounds can include TARGET or any other software that maps keyboard commands such as found on some keyboards, mice, or Joy2Key AutoHotkey etc...

 

 

 

I worked around it by doing what you suggested...but if that's the case they need to add a master arm button that is a single button push just like all the other buttons. IMO its a bug not a feature in this case.

[Raven434th]

2 crashes back to back

 

Firing on a BTR 80 using missiles crashed the game twice in a row same parameters (roughly) ...I will change it to another enemy armor vehicle to see what happens and report back.(1.57 version)

 

 

edit: changed 1 btr to a t-55...killed it no problem. will change it back to a btr group and repeat test.

 

 

edit: changed it back to a 4 platoon group of BTR...engaged 3 of 4 no problems. What can I say. However ,I didn't engage the leader of the group as I did in the first two missions that crashed(possible reason for crash?)

Edited July 20, 2017 by Raven434th

[FragBum]

Mkay setting my AC number to "666" sets okay to side panels on doors. :thumbup: but tail has "66 66" :D

Edited August 4, 2017 by FragBum
<typo>

[FragBum]

Other bug, when landing Gazelle really softly it still bounces hard right-left-right-left-BAAAAM tailrotor breaks off.

 

Yeah I know it does that every time I hit the ground to hard as well,.. :megalol:

[D4n]

It's impossible to lock on to Ka-50 with Mistral heat seeker. Please fix ASAP ! ! ! VERY ANNOYING!!! We all payed money for this to WORK ! ! ! DO IT, fix it ASAP

[purpi]

To ascend in autohover mode

 

The problem is the altitude on the ground where the helicopter is flying and the total weight of the load "fuel and weapons"

Edited August 15, 2017 by purpi
Corrected argument

[D4n]

Actually, afaik, it's supposed to behave this way, as you'd want the autopilot to keep the altitude. Imagine your going auto-hover and you're looking outside into the distance or focusing on instruments or sth. other than the ground right below the Gazelle. In this case, when slowly decreasing altitude, at some point you'd crash into the ground. I rather believe that what I'm experiencing from time to time, that the collective DOES change altitude WHILE auto-hover is activated (happens in 1 out of 10 cases or even more rarely) is the actual bug... I'm not a real pilot, but are you?

[SnowTiger]

When you activate the autohover mode the helicopter is unable to climb, collective at 100% and does not ascend. This happens in the DCS 2.1 version, but in 1.5.7 it works fine. :helpsmilie:

 

Tested with maximum weight and minimum weight, the helicopter is not able to ascend in the version DCS 2.1. In 1.5.7 it works perfectly with maximum and minimum weight. :helpsmilie:

 

Is this happening even when using (or not using) the Manual/Automatic collective mode (as described on Pg 131 of the PDF DCS SA342M Flight Manual) ?

The "C" Key turns this On/Off (the Controls Manager shows "COL" when in Hover). This should remain at a constant altitude above ground but then when you turn it Off, you should be able to Ascend/Descend.

 

Is this NOT working for you in DCS 2.1 ?

I haven't tried it in DCS 2.1 for a while but it worked the last time I did.

[Gizzy]

When you activate the autohover.....:helpsmilie:...:helpsmilie:

 

 

Just checked in v2.1.1.8491.

AP hover, Altitude & Speed hold all work fine.

If you're still having problems, PM me...

[purpi]

Is this happening even when using (or not using) the Manual/Automatic collective mode (as described on Pg 131 of the PDF DCS SA342M Flight Manual) ?

The "C" Key turns this On/Off (the Controls Manager shows "COL" when in Hover). This should remain at a constant altitude above ground but then when you turn it Off, you should be able to Ascend/Descend.

 

Is this NOT working for you in DCS 2.1 ?

I haven't tried it in DCS 2.1 for a while but it worked the last time I did.

 

:joystick: No problem jeje

Edited August 15, 2017 by purpi

[purpi]

Just checked in v2.1.1.8491.

AP hover, Altitude & Speed hold all work fine.

If you're still having problems, PM me...

 

OK :thumbup:

Edited August 15, 2017 by purpi