Jump to content

Recommended Posts

Posted

Greetings guys,

 

Dunno if it's a bug or pilot error, well here's my problem.

 

Description: Once in a while, i get no lasing, range, meaning no shooting queue, and i get the RED light « Mauvais/Bad », and when this happens, well auto-slave is not working, even though i am in range and inside G003 and D003 and respect the parameters to get a shoot queue or lasing, Master arm is on, fireing button cover up, switch is on and at Jour/DAY. Ali is set to PIL, IR Power Knob set to M, Weapon selected. If i slew way up or down (depends of times it deos it) i get the shoot cue, so i need to drop or gain alt so be able to get cue or lase on target. Sometimes i need to expose my self way too much to the target so i get it, ie, hovering at 500 FT, which doesn't make any sens for stealth attack :)

 

DCS Version: 1.5.3.53279

 

Steam: No

 

Map: Caucus

 

SP/MP: MP mission made, but load it as single

 

Screenshot/Video available: This is a video on Youtube, this guys is having the problem i'm having, but he is in 2.0/Nevada. As you can see, is solution is, slewing down until he gets a shoot queue and lasing, then simply slew back up to the target to lase the missile.

 

[ame]

[/ame]

 

Any idea?

 

Thanks

Posted

So, no one is experiencing this problem? We are the only 2 person from everyone having the module? :( This thing is really getting to me, because i'm having a hard time to do my mission, i've created some SAM Hunting mission, but i keep failing because i fight most of my time trying to get a shoot cue or even a lasing option to slave to my target, so i ened up wasting my time and getting shot down trying to fight this odd behavior :(

Posted

Problems with Laser Range Finding are a known issue and on Polychops master bug list.

 

see post #13 in this thread.

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted
Problems with Laser Range Finding are a known issue and on Polychops master bug list.

 

see post #13 in this thread.

 

 

Thanks, haven't found this, but my concern is, not eveyone is having this issue, a feelow i fly with never get this problem, by the time i end up getting a shot cue, he alreayd had time to clean 3 targets lol

Posted

One thing though, i might have found, but not sure, my patience is getting to a point these days due to personnal stuff, so my test in DCS uses a lots my left over patience. :) But from what i maight have found, when i'm in flat terrain, i have no problem, but when targets are in mountains, i get this, a few missions made it, and in the video i linked, the guy also is with a taget on mountains, as if, the laser passes through or ignore mountain and lase too far? Might try diff stuff with and without mountain

Posted

I've run into this before, but I wanted to chime in that regarding FIRING a HOT 3, the system won't allow a launch if the angle between you and your target is too steep up or down.

 

I've had issues where it would refuse to lase, or at least was returning no range, before, and it always seems hills are involved somehow. DCS 1.5.3.

Posted
I've run into this before, but I wanted to chime in that regarding FIRING a HOT 3, the system won't allow a launch if the angle between you and your target is too steep up or down.

 

I've had issues where it would refuse to lase, or at least was returning no range, before, and it always seems hills are involved somehow. DCS 1.5.3.

 

 

Good to know, thanks. I'll check this out, normal targets, i don't mind playing around with altitude with auto-collective off, but when there is SAM's or AAA around, i get nervous lol specialy with IR SAM around, having no clue on being locked, leaving cover of mountains scares me :)

Posted

Good to know, thanks. I'll check this out, normal targets, i don't mind playing around with altitude with auto-collective off, but when there is SAM's or AAA around, i get nervous lol specialy with IR SAM around, having no clue on being locked, leaving cover of mountains scares me

 

I simply ran into an issue of needing to not have 1000+ meters of altitude on my target at 2.5-3km range, that sort of thing. I don't really know the details but often it seems solvable by just repositioning to to a lower place from which to mask.

 

In those cases the rangefinder was returning range values, though. I've had times when it wouldn't do so at all, with no easy explanation why. The camera and everything involved in it seemed to be working, nothing had changed with regard to my firing position, except that suddenly I was lasing and receiving no return even though I had moments before, and of course not getting the expected launch authorization from the system.

Posted

That video is mine. I've since found the laser likes to pass through hill/mountain tops, if what's beyond the hill top is farther than the 15km max laser distance, you will not get any range and it will not slave.

 

I can make another video tonight clearly demonstrating this.

Intel 9600K@4.7GHz, Asus Z390, 64GB DDR4, EVGA RTX 3070, Custom Water Cooling, 970 EVO 1TB NVMe

34" UltraWide 3440x1440 Curved Monitor, 21" Touch Screen MFD monitor, TIR5

My Pit Build, Moza AB9 FFB w/WH Grip, TMWH Throttle, MFG Crosswinds W/Combat Pedals/Damper, Custom A-10C panels, Custom Helo Collective, SimShaker with Transducer

Posted
That video is mine. I've since found the laser likes to pass through hill/mountain tops, if what's beyond the hill top is farther than the 15km max laser distance, you will not get any range and it will not slave.

 

I can make another video tonight clearly demonstrating this.

 

 

Well you just confirmed then my thought i mentionned a few post up since i didn't get any problems on flat terrain, thanks for posting it. :)

Posted

Here's a quick followup video clearly showing the pass-through problem.

 

Intel 9600K@4.7GHz, Asus Z390, 64GB DDR4, EVGA RTX 3070, Custom Water Cooling, 970 EVO 1TB NVMe

34" UltraWide 3440x1440 Curved Monitor, 21" Touch Screen MFD monitor, TIR5

My Pit Build, Moza AB9 FFB w/WH Grip, TMWH Throttle, MFG Crosswinds W/Combat Pedals/Damper, Custom A-10C panels, Custom Helo Collective, SimShaker with Transducer

Posted (edited)
Here's a quick followup video clearly showing the pass-through problem.

 

 

 

Thanks for posting, it was an easy test to make and never thought of it, will try in 1.5 if it's the same problem i get, but chances are, since the start i had an odd feeling it was the problem. :)

 

EDIT: Here's my video, from what i discovered, the problem occurs when passing more or less the half way up the mountains/hill.

 

[ame]https://www.youtube.com/watch?v=I4lkQnj7Kio[/ame]

Edited by Doum76
Posted
Nice videos guys. It's on our list of things to look into. We'll keep you posted.

 

 

Cool, keep up the good work, you guy made me like flying chopers more than ever :P

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...