Jump to content

Recommended Posts

Posted (edited)

Before the update we had no problems with the laser. but now, when flying with Jf, the laser turns off after 5-10 minutes and does not turn on. Even when we get landing and replace the pod, the problem persists. and when we throw a point track, the missiles do not go to the laser, as if there is no laser. is this a problem or is it because of a novelty?

Edited by uboats
  • Like 3
  • Thanks 1
Posted

Also occurring for me only after a few BRM shots.  Won't work in manual/auto either.

I did wonder if it was related to high G maneuvers but then the TGP itself would also stop working right?

  • Like 1
Posted

The same problem with me, but tgp works as well as shows range. The problem remains in both of modes, auto and man. Even I tried to turn on and off by myself on when I need it, each time the same result, after 5-7 minutes laser breaks. I thought about it, but why when I change it on airfield it doesn't work? I put new pod and laser doesn't turn on. Only reboot of aircraft helps. I thought about overheating and breaking of pod, but why when I change it on airfield it doesn't work? I put new pod and laser doesn't turn on. Only reboot of aircraft helps, and how can it brakes after 3-4 launches of brm?

Posted

Good evening, me too after the OpenBeta patch the laser does not work from the third / fourth GBU-12 or after some BRM-1.

It makes me think that a timer / bug is triggered ?.

In the stable version no problem.

  • Like 3

CPU: i7 14700KF 5.5 Ghz - MB: Asus Prime Z-790A Wi-Fi - Cooler cpu: BeQuiet Loop 2 FX2 - RAM: XPG Lancer RGB 64 Gb 6000 - GPU: ASUS Rog Strix Gaming RTX 4080 16G - SSD M2 PCi4: 1x Samsung 990 Pro 4TB -  1x MSI Spatium M480 2 TB - 1x Crucial P3 Plus 4 TB - Power: CORSAIR HX1000i - Case: COOLER MASTER H500 ARGBP - Hotas Warthog (FLC+THR)-  - TM MFD Coguar - Honeycomb Alfa Flight Controller - Honeycomb Bravo Throttle - Virpil TCS Plus base+ SharKa-50 Collective Grip - Virpil Mongoost T-50 CM3 Throttle - Virpil Sharka-50 CP3 -  Virpil Alpha Constellation Alpha + Moongose T-50 CM3 base - Virpil ACE Collection Pedals -Track IR5 - Oculus Rift S -  HP Reverb G2 V2 - Monitor MSI Optix MAG322CQR WQHD 165 Hz - Windows 10 Pro - DCS: All Modules & Terrains

Posted
I made further tests with and without mod, I confirm that after 7 minutes from the first start the laser does not work (in auto and in manual mode) in OpenBeta 2.7.10.18996

CPU: i7 14700KF 5.5 Ghz - MB: Asus Prime Z-790A Wi-Fi - Cooler cpu: BeQuiet Loop 2 FX2 - RAM: XPG Lancer RGB 64 Gb 6000 - GPU: ASUS Rog Strix Gaming RTX 4080 16G - SSD M2 PCi4: 1x Samsung 990 Pro 4TB -  1x MSI Spatium M480 2 TB - 1x Crucial P3 Plus 4 TB - Power: CORSAIR HX1000i - Case: COOLER MASTER H500 ARGBP - Hotas Warthog (FLC+THR)-  - TM MFD Coguar - Honeycomb Alfa Flight Controller - Honeycomb Bravo Throttle - Virpil TCS Plus base+ SharKa-50 Collective Grip - Virpil Mongoost T-50 CM3 Throttle - Virpil Sharka-50 CP3 -  Virpil Alpha Constellation Alpha + Moongose T-50 CM3 base - Virpil ACE Collection Pedals -Track IR5 - Oculus Rift S -  HP Reverb G2 V2 - Monitor MSI Optix MAG322CQR WQHD 165 Hz - Windows 10 Pro - DCS: All Modules & Terrains

Posted
5 минут назад, tanax сказал:
I made further tests with and without mod, I confirm that after 7 minutes from the first start the laser does not work (in auto and in manual mode) in OpenBeta 2.7.10.18996

+

Is it your words?

Posted
14 minutes ago, tanax said:
I made further tests with and without mod, I confirm that after 7 minutes from the first start the laser does not work (in auto and in manual mode) in OpenBeta 2.7.10.18996

Sounds like it keeps lasing and burns itself out, even though the plane says it's not firing.

Posted
18 минут назад, J20Stronk сказал:

Sounds like it keeps lasing and burns itself out, even though the plane says it's not firing.

Enought to use laser 3-4 times with 10 sec turned on to catch this bug, it is impossible to burn so fast. There is no problem with litening.

Posted

Hi, Yep same here. I can lase manually for 5-6 minutes in flight but then i can't lase anymore. Pod work fine, but LSD isn't displayed. 
And i bought the JF for the BRM... and i enjoy buddy lasing... Well time for some CAP i guess.

Posted

Hello,

Same problem here, after some shots with BRM-1, rockets just stopped to hit the designated targets. I used target marked with point track, laser set to auto, so it would not overheat, max. G recorded was 2.8 (I tried not to over-G stores). Launch parameters met. After few passes hits stopped.

Posted (edited)
55 minutes ago, Fairey Gannet said:

Hello,

Same problem here, after some shots with BRM-1, rockets just stopped to hit the designated targets. I used target marked with point track, laser set to auto, so it would not overheat, max. G recorded was 2.8 (I tried not to over-G stores). Launch parameters met. After few passes hits stopped.

I don’t think WMD-7 is G limited in any way. One patch when jammer broke I had fun using it to lock onto people at 20nm, turn my radar off, notch them and see exactly when they fire a missile. It was a lot of fun and didn’t limit maneuverability 

Though I forget about rockets….

Edited by AeriaGloria
  • Like 1

Black Shark Den Squadron Member: We are open to new recruits, click here to check us out or apply to join! https://blacksharkden.com

E3FFFC01-584A-411C-8AFB-B02A23157EB6.jpeg

Posted
17 minutes ago, AeriaGloria said:

I don’t think WMD-7 is G limited in any way. One patch when jammer broke I had fun using it to lock onto people at 20nm, turn my radar off, notch them and see exactly when they fire a missile. It was a lot of fun and didn’t limit maneuverability 

Though I forget about rockets….

 

I was thinking about rockets in this case, I forgot to clarify that. But either way, 2.8 G should not break anything.

Posted
14 minutes ago, Aqil Huseynov said:

I guess the deka staff don't check for errors. As far as I can see, this part of the forum is nothing but silence. If you want people to be interested in the module, you should look here in the meantime. I  reported this bug to ED team but no one is interested. (good luck deka)

You know you can tag the Devs if it looks like they haven't seen the thread? 

 

Here, watch this;

 

@uboats any timeline on this bug? the tpod is pretty important.

Thanks

Posted
1 ora fa, Foogle ha scritto:

You know you can tag the Devs if it looks like they haven't seen the thread? 

thanks for your interest.

CPU: i7 14700KF 5.5 Ghz - MB: Asus Prime Z-790A Wi-Fi - Cooler cpu: BeQuiet Loop 2 FX2 - RAM: XPG Lancer RGB 64 Gb 6000 - GPU: ASUS Rog Strix Gaming RTX 4080 16G - SSD M2 PCi4: 1x Samsung 990 Pro 4TB -  1x MSI Spatium M480 2 TB - 1x Crucial P3 Plus 4 TB - Power: CORSAIR HX1000i - Case: COOLER MASTER H500 ARGBP - Hotas Warthog (FLC+THR)-  - TM MFD Coguar - Honeycomb Alfa Flight Controller - Honeycomb Bravo Throttle - Virpil TCS Plus base+ SharKa-50 Collective Grip - Virpil Mongoost T-50 CM3 Throttle - Virpil Sharka-50 CP3 -  Virpil Alpha Constellation Alpha + Moongose T-50 CM3 base - Virpil ACE Collection Pedals -Track IR5 - Oculus Rift S -  HP Reverb G2 V2 - Monitor MSI Optix MAG322CQR WQHD 165 Hz - Windows 10 Pro - DCS: All Modules & Terrains

Posted
5 hours ago, Aqil Huseynov said:

I guess the deka staff don't check for errors. As far as I can see, this part of the forum is nothing but silence. If you want people to be interested in the module, you should look here in the meantime. I  reported this bug to ED team but no one is interested. (good luck deka)

They can’t check everything before a patch. And they can’t always comment on every thread. They are a small team who dont work full time like some Heatblur staff, but I can assure you that they do care and will do everything they can to take care of it. They have done nothing less then that since they first released J-11A like three years ago 

  • Like 1

Black Shark Den Squadron Member: We are open to new recruits, click here to check us out or apply to join! https://blacksharkden.com

E3FFFC01-584A-411C-8AFB-B02A23157EB6.jpeg

Posted

same here, big issue 

RYZEN 7 1800X 3.5ghz / 32 DDR4 RAM Crucial / Nvidia 2070 RTX EVGA / Samsung SSD 500 GB / Acer XB270H G-Sync / Trackir 5 / Thrustmaster Hotas Warthog / Oculus CV1

Posted

Ok, then I am not getting nuts as I thought that I am only one with this problems. I got same issue with BRM and GBU. Works few minutes and then dies. I also for some reason do not see INRNG message on HUD and that was weird too, despite being at 2500 at a time which was alot less than 4000 in Chuck's guide picture. I can't pinpoint problem but I can try to add  my test track and if I am able ill try to add last log. Or not. Cant attack track 5,5 mb large.  Really?!

trk link:

https://easyupload.io/8x5sat

 

dcs.log

  • Like 1
Posted

hmmm, interesting.

actually, we haven't touched the wmd7/laser code for really long time

also i noticed similar report for other modules that their tpod/laser not work properly.

i will investigate, and see whether it's some bug from dcs core.

  • Like 1
  • Thanks 1

[sIGPIC][/sIGPIC]

My DCS Mods, Skins, Utilities and Scripts

 

| Windows 10 | i7-4790K | GTX 980Ti Hybrid | 32GB RAM | 3TB SSD |

| TM Warthog Stick | CH Pro Throttle + Pro Pedal | TIR5 Pro | TM MFD Cougar | Gun Camera: PrtScn |

  • uboats changed the title to [CHK] JF-17 Laser Problem
  • Recently Browsing   0 members

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