Bug in Shkval range calculations

[Griffin]

Was there anything done/checked about this bug(?) in the patch?

I have not encountered this as described by the OP in the brief time I've flown BS2 in 1.1.1.1 patch. However yesterday I had a situation that I posted in the Rookie Thread. Picture below. Is this perhaps related even though the false range value is in fact increased instead of decreasing? HUD range is correct considering the missiles reached their targets.

 

Also I'd like to know where both systems get the range information from. Both from laser, or?

 

[Isegrim]

Hey Griffin was your laser a fresh one or did you rearm before you have taken that screenshot ?

:noexpression:

[Griffin]

Yes it was fresh and I only killed that bunch of tanks you see there. 6 shots.

Does BS2 still save the last track somewhere automatically?

[Suchacz]

I can report this bug(anomality) too. (v 1.1.1.1)

 

The distance is measured by laser everytime you press your "lock" button, it takes a tenth(s) of second(s). Measured distance is correct, but after that, sometimes apparently incorrect value appears on Shkval screen. If you press lock button again, measuring is again correct, but then... etc :(

Edited December 29, 2011 by Suchacz

[Suchacz]

Does BS2 still save the last track somewhere automatically?

I'm curious too, I didn't find it anywhere, except multiplayer :( I mean some temp track file. I know that you can save track RIGHT after a mission in debriefing screen. But later...?

[AlphaOneSix]

For multiplayer sessions, tracks are, by default, kept in this folder:

C:\Users\<user>\Saved Games\DCS BlackShark 2\Tracks\Multiplayer

 

Your most recent single player track file is located at:

C:\Users\<user>\AppData\Local\Temp\DCS BlackShark 2\LastMissionTrack.trk

[Suchacz]

Your most recent single player track file is located at:

C:\Users\<user>\AppData\Local\Temp\DCS BlackShark 2\LastMissionTrack.trk

THX! Very useful! :thumbup::thumbup::smartass::pilotfly::megalol:

[Isegrim]

Ahh OK i was thinking so but its most time looking like this before laser says byebye:mad: so i was simply asking to be sure.....

 

Ahm but did somebody try out in different wheather and air pressure settings for me it looks like its has to do something with that.

 

Worst case scenario was looking like:

-Summer (i only testet in Summer)

35 deg Celsius

785 torr QNH

 

better was:

- also summer :music_whistling:

29 deg Celsius

761 torr QNH

 

and best:

all standart

20 deg Celsius

760 torr QNH

 

im sure it has to do something with weather conditions and air pressure.:book:

[Suchacz]

im sure it has to do something with weather conditions and air pressure.:book:

 

What you are talking about is a matter of physics, but discussed issue is a matter of simulation. It's not related with measuring, it is related to some wrong calculations.

[Nobody96]

The Shkval AFAIK uses the baro altimeter, so it is indeed weather related. I already posted a track in this track where I change the QNH setting on the altimeter which also affects the Shkval.

 

so long

Mathias

[Suchacz]

It surely is wearher-related. But IMHO the distance shown on shkval screen is calculated relatively to measured distance.

 

If you measure by laser (for example) 7,0 km and right after it appears on shkval screen (for example) 11,4 km than it looks little bit wierd :dunno:

 

I haven't seen it in BS1...:(

[madyogi]

Griffin, was the picture taken while any of PVI-800 NAV/TGT 1-8 were enabled? Though not see the NAV/TGT icon on your ABRISS, the print screen could be made when the icon went down (turned out). Enabled PVI800 targets blink on the ABRISS.

 

If I remembered from docks :book:, when NAV/TGTs are ON, the HUD displays range to selected NAV point and the shkval displays a range to observed target, all at the very same moment, so they can differ very much... Correct me if I'm wrong... :pilotfly:

[Griffin]

Yes propably it was NAV 1 enabled since I had no reason to change it in the mission start. I believe the HUD should not display any range unless a target is lased and it has always indicated the same range as Shkval since BS1.

[madyogi]

Yes propably it was NAV 1 enabled since I had no reason to change it in the mission start. I believe the HUD should not display any range unless a target is lased and it has always indicated the same range as Shkval since BS1.

I guess you're talking about WPT btn (the top left corner of the PVI; you can have 6 waypoints), I was rather thinking about the NAV/TGT btn, the one 3 btns below the WPT button (you can define 8?/9? NAV/TGS during flight or have them predefined in the mission editor).

If U select NAV/TGT 1->8/9 the OT shows on the HUD and the heli can stear to that point, but If U enable shkval and turn on the laser, it starts showing distnace measured with a laser and the HUD still shows distance to selected OT.

 

Since you say, you didn't change anything on PVI its must be a bug or 'undocumented feature'. (Have to admit i never reproduced it)

 

Though I have something 'unusal' with shkval too (BS1, BS2 possibly too)

1. Make sure laser is disabled

2. Enable shkval [O]

3. Designate AH64 or anything else flying. This way you can track it with opticks but not aiming it with laser; in theory target shouldn't know you're there (he doesn't have the laser warning), and that should increase your chance to come closer unnoticed...

4. Enable laser [O+RSHIFT ? ] (not sure)

5. Now, try to designate it again to get its distance and lock it...

=> WHOOPS - very often I end up trying to catch that F#$%$$%$ on the sky (and die) because the shkval optics go crazy...:joystick:

Edited January 5, 2012 by madyogi