BS2 1.2.x bugs and glitches thread (not CTD/BSOD)

Last edited may 03rd 2014 / last changes in BOLD - DCS 1.2.8.27203

Note : don't lose hope, i know ED is reading this sometimes. Maybe nostalgia or sadness, but they're reading :) !

Here you can list what you have found so far with this new version of DCS World and Black Shark 1.2.8 (or earlier...)

Thank you for your support.

Gray lines means not it's confirmed/infirmed in latest patch. Please help me if you see any change

Red lines means this bug should happen to everyone

Green lines means this bug is hopefully resolved for standard installations

Orange lines means it's a tricky situation. It can happen

If you have a certified history change, it could be better - but don't forget BlackShark 1 wasn't perfect too.

The ™ symbol means ED's tester team has made an official statement

• Mainly BS2 :
  

- Black Shark on any deck drifting proportionally to the speed of the boat. - Active since 1.2.1

- HUD not repairable (and Doppler Nav) - Active 1.2.0 (™) (Damn you, cheat mode lovers ;-)

- CALC / RAIM (Abris Airport Codes) Malfunction - Active v1.2.0 (JG_Smil & TurboHog (Hotfix))

- Kh-25ML behavior - Active v 1.2.7 (dimitriov™)

- Instant engine failure shutoff * - Active since v1.2.1 6288 -> Check the track Instant shutoff.trk.

- Black buildings may occur with Alt-Tabbing - Active v7122 Mainly in FullScreen Mode. (or when BS is reduced, 500MB VRAM lost in the process)(™)

- TV Errors display may occur with Alt-Tabbing - Active v1.2.1 6288 Resolving when turning TV ON, and/or moving / reboot K041. (™)

- Incorrect Lazer Distance - Active v1.2.1 6288 (not always) but usually resolve itself when pressing a Second time on Designate Target.(™)

- The "Crazy" Shkval - Active since BS1 (not always) (Speed�™)

- ADF indicator problem (Ark.lua) - Active since BS1 but not a really clear procedure (BaD CrC and JG_Smil)

- Can't spawn multi-sharks on carrier in MP - Active 1.2.3 v9871 (can't test this atm)

- Cut-Off Engine levers shortcuts messed - Active BS1 ? (tietze and MadCat)

- Alt-tab issue is back. - not hapenning to me since v1.2.1 6288 (NHOMY)

- Old explosion ? (or randomized effect...) - Feature to increase FPS

- Russian Betty talking in English on Red Side (+ installed RU files) - Resolved 6288 with 1.2.1 corresponding files.

- Radio comms (pilot voice) in English on the Red Side (+ installed RU files) - Resolved 6288 with 1.2.1 corresponding files.

- Mouse Cursor Not showing immediately - Resolved 7122

- Helipads not lightenning - Resolved (Could be a install issue - workaround : map object Power Supply truck) 7570(NHOMY) (Tempest)

- 5+ seconds freeze after clicking "fly button" - RE-DEActivated 7204

- Limited Radio controls in Easy communications - Resolved 7570 => If not, Use normal comms instead (Right Alt + Radio button`(SPU-9 PTT in options)). (™)

- AI direct order (Attack) not always followed - Resolved v7570 (it may depends local anti-air threats) (™)

- AI DataLink targets new behavior - Resolved and Repaired, See my guide herev1.2.4 11855

- Can't start from ramp on a boat - Resolved v1.2.4 11855

- Magnetic/True Heading differences not working - Resolved 1.2.7 v23803 (IvanK & tietze)

- Wrong sided heat blur (Right engine On / Left exhaust blur) - Resolved 1.2.7 v23803 (sgtmike74)

- Gun shell ejection position - Hotfix available. - Resolved 1.2.8 v27203 (Davis0079™)

- Incorrect Km / Mile conversion. - Resolved 1.2.8 v27203 (JaBoG32_Herby & Tietze™)

[/size] Needs official confirmation :

- Engines Restart Failure within 1mn05 (not repairable). - Active since BS1 (MaverickF22)

- Non-FFB Trim oversteering - Active v1.2.2 (Doveman)

- Gearbox Oil Pressure Light illumination procedure - Active BS1? (Nereid)

- Zebra light missing when rotor RPM set to Low (RAlt Numkey Minus(-) ) as described last line page 10-11. - In Confirmation v7570 - 10201(JG14_Smil™)

- Fuel gauge needle frozen when fuel switch is off/on (unpowered) - Appeared in 1.2.2 v7204 - Confirmed normal behavior

- SA-TLF "de-switched". This had no function anyway. - Appeared in 1.2.4

• Not only BS2 :
  

- still slideshow with arty/smerch bomblet any almost anything with dust (ship cannon, MLRS launchs (close), rockets...) - Active v1.2.0 (better in 1.2.3 but just because of less smoke effects)

- Carrier Ops : Crashs on deck : Resolved in 6288 at least. (Happy face ! :D )24 Fighters can land without trouble !

- Long load time with high/med/low settings and SSD (50secs preload (+ 30secs load), was present in 1.2.0 but resolved magically to about 30s) - Resolved v7570 (10s preload/10s load, not for everyone though)

- Smerch miscalculation in long range - Seems Resolved 1.2.3 v9871

- DCS Ships : Some USSR ships won't engage Blue team with missiles. Some others shoot missiles in water (Nimitz's sam, Tomahawk (Ticonderoga fire at point)).- Resolved 1.2.3 V9871 (at least tomahawk+Harpoon anti-ship)

- Random crashes (not developped here yet) v6288

- Flickering After Burners on some crafts, like mig 31, F18, ATi / nVidia - Resolved v1.2.4 11652

- Mission Editor save/prepare/fly messed. - Resolvedv1.2.4 11652

- USA ships (Oliver) CIWS broken (bad tracking then go stuck). - Resolved 1.2.7v23803

------

*NOMHY : Not Happenning On My System

-----

*Instant engine failure steps to follow : Make your chopper going nuts

I succeeded only once in 30+ tries in v6288... Track V7570 below:

Instant shutoff.trk

set a vodka-friendly weather (-50°C Winter)

in flight Ka50, low-med altitude

-- Take control --

set Ice/dust protection ON

set max RPM (page-up or yellow levers back-left)

Shut off L/R Electronic Engine Governor (EEG)

look at your engines RPM monitor. should be around 9500/10000 RPM @ 1000°C

now raise your collective to max

Temperature should rise fast above 1150°C

Engine fails miserably if its try to pass 10 000 RPM

one or two engine instantly go to 0 RPM.

don't make this with your über char log book.

It's seems ED won't let us Overclock our chopper are they recommend for our processors. why they made a 11K red zone RPM ? my car car go in the red zone without instant fail

Shut off L/R Electronic Engine Governor (EEG)

That's generally a baaad idea LOL :P It's there for a reason you know: so you don't blow up your engine(s).

It's seems ED won't let us Overclock our chopper are they recommend for our processors. why they made a 11K red zone RPM ? my car car go in the red zone without instant fail

Disable the rev limiter on your car and repeat the test :)

If you rev your cold engine at -50C I can guarantee that you will end up with a broken engine. :)

The EGT only show you the temperature of the exhaust, not the rest of the engine.

Mates it was just a procedure to show this bug.

I know every "don't do this irl blah blah"

fact is sometime i shut off (or just forgot) EEG to gain some power.

You could gain some extra climb m/s because the Engine Limiter is not active.

Moreover, -50°C, 0°C, +50°C, same story. By the way your engine Loves cold air. My car will probably survive over-rpm and extra power in a -50°C environment, as long as nothing is frozen.

same for 7Ghz CPU.

My Rev, Limiter, or Ruptor like i call it here allows me to enter 50/75% the red zone.

So, please be kind not to populate this thead with "Don't do it anyway"

ED is not maintaining a "known bugs" log for us, and it could be useful if someone start this kind of thread. you could save 1h when looking for a bug and 2h reporting a bug, because you easily found someone else already done that.

Like everyone have the cursor bug, and i didn't tested the skhval yet.

cheers ;)

As for the RPM Red Zone. Its so you can actually see if the engine is in a overspeed condition or not.

And when it is alert the maintenance crew to take appropriate action.

If you would not have the red zone, you would never know if the engine was in a over speed condition for any period of time.

Which can have a disastrous effect on the engine's lifetime.

(turbine wheels can actually explode due to to high RPM's)

Here you can list what you have found so far with this new version of DCS World and Black Shark 1.2.1

please put DCSW bugs in the thread designed for this purpose. Its easier for ED and for the testers to monitor.

http://forums.eagle.ru/forumdisplay.php?f=185

thanks.

I can't get the ka-50 datalink to work anymore, the send/mem button just flashes when i press it. I can't say for sure if it's a bug, maybe I'm doing it wrong. Can anyone else try to send datalink to AI wingman and see if it works.

I can't get my wingman to attack any units in the first mission of Georgian Oil War.

I can't get my wingman to attack any units in the first mission of Georgian Oil War.

It happens alot. No attack commands work....not just in the first mission.

look at your engines RPM monitor. should be around 9500/10000 RPM @ 1000°C

now raise your collective to max

Temperature should rise fast above 1150°C

Engine fails miserably if its try to pass 10 000 RPM

one or two engine instantly go to 0 RPM.

How is this a bug?

@Sobek :

In fact, i'm still working on mission design, test random things like Super-Shark flying at 700kmh, Take-Off/ Flying with 1 engine or climbing at 8500m ... Prepare Button saves somes times, but doesn't have access to tracks saves

-This Engine fail is a bug somehow because it never happened before.

-Not written on patch ;)

The thing in BS when you usually loose an engine (because you hit EEG after asked max power for example), is a slow & steady shutdown. (announcing gently a very bad news)

In this case, it's just ON-OFF, the sound just suddently stops, the needle goes to 0 FTL

BUT

Since 6288, i've only reproduced that only ONE time. (and i even restarted it while flying). Assuming no-one playing with buttons on his shark, no-one will see that anyway. (shame on you, give some love to backup systems :))

@NuNce / lokiTexas

guys i will test it tomorrow

You are saying it's happening in campaign mainly?

Because when i tested Datalink, directs commands worked great.

Anyway, i remember at some point earlier discussions (experienced that too) with "unable-like" wingmen, was in 1.2.0 and earlier imho.

"Flight, engage ..." "-Unable ! - Unable !"

"Flight, RTB you lazy asses" "-Ok Boss"

Edit : Tested, indeed, it didn't worked in my mission ! Wingman 2 refused every direct attack order, Wingman 3 said yes but went crazy, wingman 4 was a good wingman. Bug added. Weird enough, last week it worked as i created thoses targets for each wingman and they complied ...

Hello!

I wanted to bump this great post in hopes of making it active. It's purpose is to help make BS World all it can be by having a place to discuss a possible bug or bug fix that we can then pass on to ED in the proper fasion as listed by Druid in post #7.

I have recently reported a bug about the Free-turbine RPM governor that many seem to have missed or not cared about, but is quite important when flying the Blackshark. I made it official after conferring with Enforce to learn it is repeatable.

Please be specific as possible. It is not a wish list, use it for things you can verify and repeat so we can get them sent to ED in the proper fashion. We have to show that there is a need for this or it may not happen.

Best wishes,

Please add this to the list: "Auto-pilot oversteering when trimming".

I've posted two tracks showing the problem here http://forums.eagle.ru/showpost.php?p=1652472&postcount=35

and someone else has posted a video showing it here http://forums.eagle.ru/showpost.php?p=1655247&postcount=37

it seems some people don't experience this, so it may only occur with certain settings, although I tested with Central Trimmer mode on and off. Even hovering just after take-off it does it, so it doesn't seem like it can be explained by accumulated trimming errors. The only workaround suggested so far is to use "Hold-trim whilst steering" but I'd like to be able to fly the KA-50 the proper way (this is meant to be a sim after all).

If the tracks and video linked to above aren't enough, I'll make a video from the tracks or a fresh flight.

To hold the trimmer while steering is the proper way. The real KA-50 pilots holds the trimmer when ever they move the controls.

I agree it is harder to keep the helo level than earlier versions, but it sounds like you are fighting the gyros. They need time to work. If you rush it you fight gyroscopic precession.

I've thought a bit more of this over coffee...

I've noticed that when I look at the RCTL ENTER control indicator, the pippers that show input of the controls move as though they are hydraulically damped - no matter how fast you move the control, the pipper takes it's time reflecting the change. Move rudders full range to see this. To me, this is a neat feature of the sim that simulates either hydraulic or gyro damping of the controls. It seems to be more pronounced than I ever remember seeing.

The Blackshark has also become harder to control is some ways than eariler versions. That is a fact. We can ask if this issue is related to the latest modeling of the INS system of the Ka-50. Is there some math error or whatever that makes the helo want to tilt one way or the other as opposed to flying level? Do we have to hold the trimmer too long?

just trying to help narrow it down :)

I understand that real Russian pilots use the click and release method and that's the method the manual describes. There's certainly videos where the pilot is repeatedly clicking the trim, not holding it, one where he's landing on an aircraft deck. This would be impossible in DCSW as it would oversteer and smack him into the deck. Perhaps he had FD enabled, which seems to prevent the oversteer but I've been told enabling FD is a fudge that shouldn't be necessary. Holding the trimmer also seems to be a workaround that we're forced to use in DCSW as the other method doesn't work properly.

Have you looked at the video and/or tracks I linked to to see if it looks like we're fighting the gyros? I don't think the Controls Indicator even reflects the oversteering.

Hello Doveman. I know this problem because everyone has this, since forever.

I saw your tracks and video. It doesn't bothered me because i'm used to see it.

The fact, is, i'm an experimental pilot (i've broke sooo many sharks ;) ) Even if i use sometimes this click and forget method , i know there's a chance of a wrong AP input.

If i do this when i'm going nuts (at 340+km/h) i would have immediate rotor intersection and a horrible death. same for acrobaties (loopings/rollings etc...).

The point is, it's there since BS1. And Click the trim in the final position is considered as insta disconnect/reconnect Autopilot. If you think further, when the AP is disconnected, it release the hydraulics pressure it made to stabilize your shark. And when reconnected , especially if you're manoeuvering (like in the video) it would inject pressure, added to YOUR steering, thus oversteering (you have a sensible delay, unlike a Fighter).

That's probably why this effect is (almost) negligible in a stable flightpath, and terrible when used while manoeuvering.

I think we would need a real shark pilot to confirm this. But i'm sure he would answer : i don't do this anyway, like offlining EEG (but a governor fail is possible in my case ;) )

A real bug about the trim is in certains cases, it just go on and off repeatedely (and very fast) even if you keep your trim pushed. This behavior is caused by a massive lag on medium- CPUs. (you can't trim while passing throught clouds in a heavy dynamic weather) But it's ED's code problem. No sure they can do much about this.

Anyway, i'll add an entry on probable bugs, in case we have a confirmation by ED someday.

Thank you !

Enforce:

About your PM. You were able to see the yellow rotor warning light flash when you switched RPM to Low? I know the light works when RPM's go under a certain percentage. The yellow light should be on the whole time the switch is set to low if the manual is correct.

To reproduce: Go Instant Action/ Takeoff Belsan. While on runway, visually confirm free-turbine switch on collective change from Nominal (92% RPM) to Low (87% RPM). No Warning light or buzzer.

If it is, could be there was something wrong with my update of BS(?)

When a real KA-50 pilot can tell how the trimmer works, I'll listen. Not 'till then though. That is an endless argument from BS original.

LATEST UPDATE: I think this is trouble on my side. I get no warning lamp or sound even when my RPM go under 82%. My beeper and warning only sound when I use the "Test Lamp" button. There could very well be something wrong with my installation.

I think comment from real Ka-32 pilot should be enough, because principles of Ka-32 AP seems similar to Ka-50. I have spent some time reading flight manual of Ka-32, and it mentions same 20% of AP authority, AP disconnection on depressed trimmer, AP remembering angles of yaw, pitch, roll on release of trimmer, recommendation to press and hold trimmer if you want more effective controls. It even goes as far as naming pilot the extension of AP, and it tells the pilot not to fight AP, but intervene when authority of AP isn't enough. Unfortunately, it does not explicitly tell to use either click-click or click-hold-release method for trimming.

Exactly, I think both are used, just as some of us do in the sim.

Hello Doveman. I know this problem because everyone has this, since forever.

 

I saw your tracks and video. It doesn't bothered me because i'm used to see it.

The fact, is, i'm an experimental pilot (i've broke sooo many sharks ;) ) Even if i use sometimes this click and forget method , i know there's a chance of a wrong AP input.

If i do this when i'm going nuts (at 340+km/h) i would have immediate rotor intersection and a horrible death. same for acrobaties (loopings/rollings etc...).

The point is, it's there since BS1. And Click the trim in the final position is considered as insta disconnect/reconnect Autopilot. If you think further, when the AP is disconnected, it release the hydraulics pressure it made to stabilize your shark. And when reconnected , especially if you're manoeuvering (like in the video) it would inject pressure, added to YOUR steering, thus oversteering (you have a sensible delay, unlike a Fighter).

That's probably why this effect is (almost) negligible in a stable flightpath, and terrible when used while manoeuvering.

I think we would need a real shark pilot to confirm this. But i'm sure he would answer : i don't do this anyway, like offlining EEG (but a governor fail is possible in my case ;) )

 

A real bug about the trim is in certains cases, it just go on and off repeatedely (and very fast) even if you keep your trim pushed. This behavior is caused by a massive lag on medium- CPUs. (you can't trim while passing throught clouds in a heavy dynamic weather) But it's ED's code problem. No sure they can do much about this.

 

Anyway, i'll add an entry on probable bugs, in case we have a confirmation by ED someday.

Thank you !

Hi Erforce,

Thanks. I can understand having problems clicking Trim in some conditions, such as maneuvering to an opposing direction to our current heading, when we can expect the AP to suddenly disengage and throw the shark further than we're aiming for and then it makes sense to use click-hold, however in my track I found it was doing that just after taking off when I was trying to achieve a hover, where I hadn't manouvered much and there shouldn't have been much AP input or accumulated trim I don't think. I haven't found it makes any difference if I maneuver and stabilise on the new heading before clicking Trim either, so I wouldn't say the effect is negligible in a stable flightpath

Of course if real pilots confirm that click-release trim is unusable and they all have to use click-hold (or maybe click-release can only be used in very limited circumstances), I have no problem using that method and I hope ED will reflect this in an updated manual but certainly the current manual and other online guides tell me to use click-release (not to mention the snarky comments about my lack of ability every time I ask why click-release Trim seems to want to kill me!)

Doveman, I've added an entry for your Trim problem. I'm followind your thread too, but don't hesistate to PM me if your have more certifications.

JG, following the procedure page 10-11 didn't activated my zebra light at 84%. But the fact is the needle seems to be near 85%. However, The zebra correctly flash under this percentage (give some collective) without buzzing.

This does the same way in BS1. Maybe ED will change the manual or something else in the future ;)

Doveman, I've added an entry for your Trim problem. I'm followind your thread too, but don't hesistate to PM me if your have more certifications.

Great, thanks Erforce.

Excellent Job Erforce. I missed this thread and it was badly needed considering the lack of consideration BS's bugs are getting with each DCS update. Now it is traceable. Maybe you should consider renaming it as 1.2.1 is not the last version anymore.

Do you think that the incorrect default ARK.lua file and the crazy shkval problem should be part of your list?

Good job.