BBQ Posted September 25, 2013 Posted September 25, 2013 I know this has already been submitted -- just wanted to show another example of the behavior:
ShuRugal Posted September 26, 2013 Posted September 26, 2013 part of what is going on there is that the laser only runs for a few seconds at a time except when actively tracking a target. The rest of the time it relies on knowledge of distance/angle to last known spot, and calculates based on camera and helicopter movement. Problem is, it assumes level terrain, so when terrain is not level.... the calculation is wrong. The effect is especially noticable at low angles, where a small shift in camera angle can make a large shift in range.
zaelu Posted September 26, 2013 Posted September 26, 2013 The laser is in Auto mode and probably this is what it does. As long as it actually ranges and tracks when I lock, is fine for me. Looks a bit more realistic this way but I don't know if is really real or some little bug lately introduced. Maybe a statement from devs in change log would clarify it? [sIGPIC][/sIGPIC] I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A, Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least
Suchacz Posted September 26, 2013 Posted September 26, 2013 This behavior is there since the BS2 came out. We can only guess how faulty or realistic is it... Per aspera ad astra! Crucial reading about DCS: Black Shark - Black Shark and Coaxial Rotor Aerodynamics, Black Shark and the Trimmer, Black Shark – Autopilot: Part 1, Black Shark – Autopilot: Part 2
BigOHenry Posted September 26, 2013 Posted September 26, 2013 I think its not realistic... I have lock target (for exaple 3.2 at cannon range) and in a few seconds i got for example 6.2 range. This happens a lot to me... Its a anoying bug...
BBQ Posted September 27, 2013 Author Posted September 27, 2013 I've been flying and using the laser range-finder since Blackshark graced the desktop (see my callsign in the back of the manual!) This jumping around of the range value is one of two things: [*]A New Bug [*]A New Feature Perhaps the real-deal does behave this way -- in which case this is a "new feature", or this new behavior was unintended, in which case it's a bug. I know for sure that the range-finder did not behave this way in the past, though I'm not sure which update introduced it --
Fishbreath Posted September 27, 2013 Posted September 27, 2013 I'm perhaps slightly leaning toward 'bug'. I have a shooting range mission I play around with, with targets to the west of Mozdok. The ground there is very flat, and the elevation is only 200m or so. Sometimes, after taking a laser range, panning the Shkval nearer to my helicopter will cause the range to increase at the same rate as panning it away. I can't really think of a sane range estimation algorithm which would do that. Black Shark, Harrier, and Hornet pilot Many Words - Serial Fiction | Ka-50 Employment Guide | Ka-50 Avionics Cheat Sheet | Multiplayer Shooting Range Mission
BBQ Posted September 27, 2013 Author Posted September 27, 2013 Last time it happened to me (this morning), I was over 1000 meters AGL, with sensor pointing roughly 45 degrees down, straight ahead at a tank, on flat ground, 5km off my nose.
msalama Posted September 27, 2013 Posted September 27, 2013 Uh... I think I've seen it behave like this in BS v1.0 already? Not sure though, plus have no previous versions installed ATM so cannot check... The DCS Mi-8MTV2. The best aviational BBW experience you could ever dream of.
karambiatos Posted September 27, 2013 Posted September 27, 2013 (edited) Uh... I think I've seen it behave like this in BS v1.0 already? Not sure though, plus have no previous versions installed ATM so cannot check... it does, but not to such extremes, where moving it a bit changes the range 2 or more KM Perhaps the real-deal does behave this way -- in which case this is a "new feature", or this new behavior was unintended, in which case it's a bug. I know for sure that the range-finder did not behave this way in the past, though I'm not sure which update introduced it -- since the patch notes didnt mention it, its a bug, until someone says something about it. Edited September 27, 2013 by karambiatos A 1000 flights, a 1000 crashes, perfect record. =&arrFilter_pf[gameversion]=&arrFilter_pf[filelang]=&arrFilter_pf[aircraft]=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&sort_by_order=TIMESTAMP_X_DESC"] Check out my random mods and things
BBQ Posted October 2, 2013 Author Posted October 2, 2013 Another Example This time, I could not get the range-finder to lock (hitting the Enter key throughout video)
idenwen Posted October 2, 2013 Posted October 2, 2013 At least thanks for that video. I had this problem the first time about a week ago or didn't realised it before.... thought of ... "What the hell is broken now??:joystick:"... Recalibrated Joystick and uninstalled every mod I had just to find out what was going on... So it's a featurebug! Thanks again for making me stop searching :D
BigOHenry Posted October 2, 2013 Posted October 2, 2013 I had problem with lock on more than 4 km. Problem was in modified file: graphics.lua . I had no problem with lock on 9.5 km today. Do not forget about weather. When is the bad light, Shkval has problems with lock...
Recommended Posts