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

[LordLobs]

The fuel quantity switch works. The issue is actually with the fuel gauge...

 

I mean, if you start a mission with let's say 10% fuel, the fuel gauge will show 10% even without powering it. If you refuel your aircraft to 100%, the gauge will still show 10%... it'll only show 100% fuel after you flip up the switch. PS: The gauge keep showing 100% after you turn everything off.

FuelQuantity.trk

Edited January 25, 2013 by LordLobs
posting track and additional info

[doveman]

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.

 

+1 and I'd like to see it made a sticky as well, so that it doesn't get buried by newer posts.

 

Another thing that would be really useful is a sticky detailing which mods/tweaks still work and are needed/recommended for 1.2.2 (or the latest version). Some tweaks are quite simple and vital, like deleting smokecloud.pfx from Bazar\Effects\PFX\high (or medium or low if you're using those) which if not done cripples the framerate at very low-level flying. Then there's the need to tweak the profiles in Scripts\net\net_types.lua to get good performance with fast Internet and maybe No Airport Vehicles is essential whilst the models are crippling performance at airfields (I haven't tested this mod to see if it helps yet).

 

Others, such as increased visibility, Devrim's HD Pits or Real Sound, might be more of a personal preference but might be recommended if their impact on framerate is minimal.

 

The problem at the moment is a) the mods are all buried in their own separate threads so it's not easy to identify what's available and b) it's hard to know if a certain mod is still needed and is compatible with the current version of BS2, so having them all (or the main ones at least) listed in one sticky, with information about whether they're needed and still work (with links to their own threads of course), would be immensely helpful.

[Erforce]

Guys, I'm really glad to see more and more participation in this thread to help me out.

Yes BlackShark community is quiet as hell, and i don't understand Russian.

Just made last edits, it took me 1h30 (it was just Edits !!)

It's a quite difficult task because majority of bugs listed about BS2 are not common to everyone (install/harware problems) but everyone thinks ED is responsible. (Ex : i might get a clue about datalink wingmen new behavior)

 

BaD CrC :

About ADF channels, JG_Smil asked me to investigate the problem but i must confess i'm a complete Newbie on those indicators. And didn't had time to re-read the manual and made tests. I will do this shortly.

In the meanwhile, you're entered the red line because a wrong Lua file is common to everyone.

The Crazy Shkval : I've got this bug once, and assimilated it to a low-hardware lags, like my Trim auto-disable/enable when passing throught heavy dynamics clouds. This is a complex glitch, not always happening. I've added it too, but i'm not sure this will be resolved anytime soon.

Some glitches dissapeared after my hardware upgrade (Xeon to i7 3770k)

 

LordLobs :

Yes, sure ! I knew it, just forgot to "correct" the definition ;)

It's done.

Someone said it's a normal behavior(so BS1 was wrong), we'll probably get an ED statement on this. My car has this exact behavior too :smilewink:, but it's cheaper.

 

Doveman :

Always a pleasure :D

But don't count on me to start a "mods-optimization" thread :smartass:

I'm not a modder, and i think gathering updated infos on everyone will be tought ! Because Modder can stop their work anytime.

My best advice on this, just submit yourself to the specific threads. Usually, when a patch come out, the modder should try his mod first.

Anyway, what you're asking could be nice.

 

------

A new update about this last update : No, unfortunately only a moderator can change the Title. I do change the title, but it's just change the name once you're IN the thread.

I've added links to "official" threads too. It will get easier to follow discussions.

 

Thank you again

I'm working on "The Fighters Collection" guide. should be out soon :D

Edited January 25, 2013 by Erforce

[JG14_Smil]

LordLobs: I think others have reported this about the fuel gauge. One thing I do note is: every real picture I see of a KA-50, the fuel gauge is showing a fuel level with power turned off.

 

ADF channels "bug" seeems to be fixed with proper ark.lua file edits. Adding the custom ark.lua file to each mission created is needed to banish it for good.

 

Before I found this thread, I was thinking of creating a thread called something like "To Improve Blackshark" that would be much like the ideas disussed: A list of bugs, a list of mods to improve the sim, ect, all in one place. As noted, the fixes are found all over the place and even the search feature can have trouble finding the proper one sometimes.

Edited January 25, 2013 by JG14_Smil

[doveman]

Erforce, No I wasn't expecting you to do a "recommended mods" thread as well, you're doing quite enough with this thread thanks. As you say, modders can stop work at anytime but the thread would just be a single place where people can see what mods/tweaks they should be using with the current version and if someone's tested and found it incompatible, it can be taken off the list to help others.

 

JG14_Smil, It would be great if you are able to create a "recommended mods/tweaks" thread, that will hopefully get stickied along with this one. I'd suggest not duplicating Erforce's work and leave bugs to this thread though.

[BaD CrC]

ADF channels "bug" seeems to be fixed with proper ark.lua file edits. Adding the custom ark.lua file to each mission created is needed to banish it for good.

 

Correct Smil. Until you sent me the link to this ARL.LUA thread, I spent the last 18 months trying to figure out what was doing wrong with my ADF. Now everything works great and we had a blast with my squad mates this week practising IMC NDB approaches based on Jeppessen charts. ADF works as explained in the manual only since this bloody ARK.lua file is modified. But default file makes it impossible to work with ADF and to me this is a bug.

[JG14_Smil]

Thing to remember is: anyone that flies your mission gets their ark.lua file over-written, so in effect, we can fix this bug ourselves until the next update comes out and re-screws it up. :)

 

Adding an ark.lua file to a mission needs to become a standard procedure.

[BaD CrC]

Erforce.

Is watching helplessly your chopper, engines off and brakes on, slipping off the moving ship deck until it crashes into the sea worth mentioning in your list? Didn't test it though with 1.2.2, so maybe it is already solved.

[JG14_Smil]

Yes, I created a mission with a runway start on the CV and the helo slowly moved forward and fell off the CV. Helo appeared to be moving slightly faster than the CV. Park brake was on.

[Erforce]

Yes yes yes i'm on it guys !

The fact is, my thread being mainly about BlackShark, and this "feature", which didn't existed in BS1/2 being common to every modules (well... i think). There are numerous glitches about DCS Ships ATM, i don't really know what ED is doing with their code.

 

I'll probably make this entry in a hour or 2, when i'll update one or 2 other things.

Thanks again !

Edit: BTW, an A10 cannot takeoff from there. and i don't have FC3. if any of you have it, please tell me if this bug still present.

 

Edit 2 : Ok, added the drifting feature. I've worked on the datalink problem last hours, i think i'm close to a solution. will keep you updated. I've posted a track of my instant engine failure too, get a look, try to do it yourself :D

The easy comm works as intended, i can control everyone again (=> wingman4).

Edited January 28, 2013 by Erforce

[BaD CrC]

Thanks Smil for testing it.

And merci Erforce for your time on this thread. Hope it will become a sticky soon.

[JG14_Smil]

Here is another one for us to mull over.

 

Real life runway headings are off a bit as I have seen noted elsewhere, and in my example here, Mozdok RWY 8 is at 082 degrees when setting DTA-Manual to the runway heading. The Aerodrome charts pdf file has this runway listed as 076 degrees. This verifies what I have read that the map magnetic variation is seemingly 4-6 degrees off in DCS.

 

So I thought I would test the magnetic variation knob to see if I could affect this change in my flight controls, but I still saw a 082 degree runway heading when I landed. I have to question if this feature even works as I made a big change with no results seen. It almost appears as though this has not been modeled into the map.

 

I was just wondering if there was anything we could do to get the runway headings to line up with the provided documentation.

[JG14_Smil]

Radar altimeter warning lamp - this is the small yellow triangle in the 'minimum safe altitude setting' knob - does not appear to work in my KA-50.

 

It should light up anytime I am below the minimum safe altitude (MSA) and stay lit until I am back above it.

 

I note my Helios LED for this lights up properly when I go below my MSA, but does not shut off when I go back above, but I will look into this more and might be able to fix it.

 

I do not see this lamp work in DCSW BS. I remember it working in an earlier BS version.

[BaD CrC]

Good finding Smil for the radalt light! So the magvar knob also is inop?? Need to try that as it is wired in my pit. What is the magnetic deviation in this region by the way?

[JG14_Smil]

Approximately 5 degrees in the Caucasus. That seems to tie into the error pretty well. (manual has this written as: "5-degrees", could that mean it is negative?)

 

Deviation and variation are different things :)

 

Variation is caused by the earth's magnetic fields. Deviation is caused by the helo itself. (page 6-52 in the BS manual). The Ka-50 has a positive 7/8th of a degree deviation for the 082 degree runway heading.

 

We will also have to check to see if the Latitude adjustment does anything. It is a darn shame nav fix points don't work either.

 

One has to wonder why so much time is spent on writing a manual if the feature(s) does(do) not work.

Edited February 4, 2013 by JG14_Smil

[JG14_Smil]

Some of this does make sense. If the error we are seeing is 4-6 degrees off, this could account for both the variation and deviation error factors.

 

This would also prove that no correction is being done with the magvar knob(?).

Edited February 4, 2013 by JG14_Smil

[JG14_Smil]

While I am on a roll, could someone look into the Gyro switch on the wall panel? I am not able to get the helo to follow a manually set heading with manual gyro operation. It'd be great to get that figured out...

 

Note to ED: If you need a beta tester, for Pete's sake let me know.

Edited February 4, 2013 by JG14_Smil

[JG14_Smil]

It appears to me that the world map we fly in in DCSW BS has the true/magnetic meridians messed up.

 

DCS treats the magnetic meridian as the 'true north' meridian, giving us all the 4-6 degree errors just as it should.

 

Perhaps this is a fixable in an update? If the magnetic variation knob did actually work, we would be able to work around this, so I am thinking that there are a couple bugs right there.

===========================

 

Another bug I found for testing: LWR test button does not turn on any of the LWR lamps as it should for testing the system.

[doveman]

Hi Erforce

 

Could you add this bug please, where the mouse cockpit no longer works after pressing Esc and looking at the Briefing? http://forums.eagle.ru/showthread.php?t=101243

 

It's completely reproducible for me and a complete pain in the ass, because it means I can no longer operate the shark and have to abort the mission, therefore losing all my progress (as there's no save function).

[Erforce]

A quick update, as i said to JG_Smil, i'm not a true heading/magnetic expert, so i will need more time investigating this.

 

LWS self test button is working like the manual descibes it (30s hemisphere + some lights LWR and master caution.)

 

I've just tested ark lua for the first time, and, without messing Ark.lua, the predefined airports ADF worked like a charm. Landed in pure haze with hsi needle. Anapa preset 4 : outer=>inner=> landed.

 

In the manual, it says you must edit lua yourself sometimes.

 

My magnetic compass has about 3-4° difference from my true heading.

but the magnetic deviation knob does not work.

I didn't tested the map/3D world differences

 

I really can't reproduce the mouse bug described by doveman at all.

 

Am i doing something wrong?

[doveman]

Hmm, I thought it might be a recent mod I'd added that was causing it but I've just tested with no mods and it's not working still.

 

I even tested with the mission it was working on earlier (with all my mods) and it's not working on that now either, so it doesn't appear to be mod or mission related (tested with three missions).

 

When it was working earlier, I was using SoftTH/Helios but I've tried disabling that as well now and it still happens.

 

I tried killing RadeonPro and MSI Afterburner just in case but no difference.

 

It doesn't matter whether I exit the briefing screen with Back or Fly, no ability to move the cockpit view with the mouse afterwards, although the numpad still works.

 

EDIT: Tried doing a Repair with all mods disabled but that didn't make any difference either.

Edited February 13, 2013 by doveman

[JG14_Smil]

I have no issues as you describe.

 

Can you try the disable aero option in DCS?

[doveman]

I have no issues as you describe.

 

Can you try the disable aero option in DCS?

 

Thanks but that didn't make any difference.

[JG14_Smil]

Issue with GRBX OIL LED lamp described in link below. I have confirmed the steps and results.

 

http://forums.eagle.ru/showthread.php?t=101732

Edited February 21, 2013 by JG14_Smil

[Nereid]

Hi Erforce

 

Could you add this bug please, where the mouse cockpit no longer works after pressing Esc and looking at the Briefing? http://forums.eagle.ru/showthread.php?t=101243

 

It's completely reproducible for me

 

I have checked this and noticed this behavior also. Its impossible to change the view with the mouse after opening the briefing ingame. Keys still work but no mouse.