Jump to content

Radar Stuck in Standby Mode

Avio

By Avio
in Bugs and Problems

 Share

Recommended Posts

Avio

Avio

Posted
Posted

Radar was still working fine yesterday, but now it stays stuck in standby mode, even with radar switch in ON. Just will not do any sweep.

Anyone has this problem? Or is this related to the dispute going on?

 

  • Like 2
Flapjacks

Flapjacks

Posted
Posted
6 minutes ago, Avio said:

Radar was still working fine yesterday, but now it stays stuck in standby mode, even with radar switch in ON. Just will not do any sweep.

Anyone has this problem? Or is this related to the dispute going on?

 

Just seeing this reported on discord. It's something to do with files going out of date. Some people have said rolling back the computer's date fixed it. As long as it was set to the 13th (or before I'm guessing).

  • Like 1
  • Thanks 1
Avio

Avio

Posted
  • Author
Posted
1 minute ago, Flapjacks said:

Just seeing this reported on discord. It's something to do with files going out of date. Some people have said rolling back the computer's date fixed it. As long as it was set to the 13th (or before I'm guessing).

Thanks. That is not good. Will try roll back date and see if it works.

Anyone else seen this issue? It was still fine as of yesterday 13 June.

YoYo

YoYo

Posted
Posted
4 hours ago, Avio said:

Radar was still working fine yesterday, but now it stays stuck in standby mode, even with radar switch in ON. Just will not do any sweep.

Anyone has this problem? Or is this related to the dispute going on?

 

What??? Looks like a Trojan horse, or rabbit 😁. I'll check it too ...

qqMbaA.gif

I haven't returned anything from Razbam, but it's starting to look bad 😞

  • Like 1

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

TonyRS

TonyRS

Posted
Posted

I hope there is a very quick ‘fix’ for this 🤷🏻‍♂️Changing the ‘system date’ just to get something working in a single module seems like a very bad idea 😱
To be functional DCS needs to work without the need for such ‘hacks’???

  • Like 3

Self Build: 5000D Airflow Case, Asus ROG Maximus Z690 Hero DDR 5 MOBO, 1200W Corsair Modular PSU, I9-12900K CPU, MSI 3080 ti 12GB GPU, Corsair Vengence 64GB DDR5 5600 RAM, H150i Elite CPU Cooler, 2 x 1TB & 1 x 2TB Samsung 980 Pro M.2 PCIe 4.0  SSD's, Windows 10 Pro OS, Samsung Odyssey G7 28" G-Sync (3840 x 2160 Resolution) Monitor, Thrustmaster, ROG Strix Go 2.4 Headset , HOTAS Warthog Stick, Throttle & TPR Rudder mounted on WheelStandPro V2 rig. TrackIR 5 - DCS: Channel, Normandy 2, Persian Gulf, Syria, Nevada, S. Atlantic, Sinai, Kola, Afghanistan, Iraq, Germany - FC3, Super Carrier, Spitfire, Mosquito, P-51, P-47, Bf-109, FW-190 A-8, AH-64D, Huey, Kiowa, Chinook, F18-C Hornet, AV-8B, F-16C, F-5E, A-10C II, F-86E Sabre, F-15E Strike Eagle, F-14 Tomcat, Viggen, MB-339. Android Tablet with DCS UFC & DCS NAV

Tom Kazansky

Tom Kazansky

Posted
Posted
1 hour ago, BIGNEWY said:

Hi all we are aware of the problem and we will look for a resolution. 

thank you

Thanks! Is this something ED can probably repair, for it seems it has to do with file dates, or do you need Razbam for a fix?

  • Like 1
schmiefel

schmiefel

Posted
Posted

Just guessing, but that really looks very intentional made by Razbam putting a time-out into their files to stop using the module if there will be no further updates provided. And maybe that's why several AV tools showed a red flag for some files of the F-15E installation recently?

  • Like 3
  • Thanks 1

Primary for DCS and other flightsims: i9 12900K@default OC on MSI Z790 Tomahawk (MS-7D91) | 64 GB DDR5-5600 | Asus TUF RTX3090 Gaming OC | 1x 38"@3840x1600 | 1x 27"@2560x1440 | Windows10Pro64

Spoiler

Secondary: i7 11700k@5.1GHz on MSI Z590 Gaming Force MB| 64 GB DDR4-3200 | PowerColor RX6900XTU Red Devil | 1x 32"@2560*1440 + 1x24"@1980*1200 | Windows10Pro64

Backup: i7 6700K@4.8GHz | 64 GB DDR4-2400 | PowerColor RX5700XT Red Devil | SSD-500/1000GB | 1x49" 32:9 Asus X49VQ 3840x1080 | Windows10Pro64

Flightsim Input Devices: VPC: ACE2 Rudder / WarBRD Base / T-50CM2 Base with 50mm ext. / Alpha-R, Mongoos T-50CM, WarBRD and VFX Grip / T-50CM3 Throttle | VPC Sharka-50 + #2 Controle Panel | TM Cougar MFD-Frames| Rift S - Secondary: TM HOTAS WARTHOG/Cougar Throttle+Stick, F-18-Grip | TM TPR Rudder | DelanClip/PS3-CAM IR-Tracker

  • ED Team
BIGNEWY

BIGNEWY

Posted
  • ED Team
Posted
11 minutes ago, schmiefel said:

Just guessing, but that really looks very intentional made by Razbam putting a time-out into their files to stop using the module if there will be no further updates provided. And maybe that's why several AV tools showed a red flag for some files of the F-15E installation recently?

It is not related to AV, some AV just do not like the protection being used. 

 

  • Like 2
  • Thanks 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Musis

Musis

Posted
Posted

After the reading of some comments about the F15E Radar, I have test it this morning and effectively the Radar is blind (the caret for the horizontal screening don't move).

I have only tested the A/A mode.

I have red somewhere that the problem disappears by modifying the system date after the launch of DCS.

I attach a track of my test in case of I was in error during this test.

 

Best regards

test RDR.trk

Slippa

Slippa

Posted
Posted
2 minutes ago, BIGNEWY said:

It is not related to AV, some AV just do not like the protection being used. 

 

What about the former? Can you say whether or not it looks like an intentional ‘security’ time-out type thing? If so, the rights to which would be part of the copyright?

  • Like 1
  • ED Team
BIGNEWY

BIGNEWY

Posted
  • ED Team
Posted
9 minutes ago, Slippa said:

What about the former? Can you say whether or not it looks like an intentional ‘security’ time-out type thing? If so, the rights to which would be part of the copyright?


I can not comment sorry.

  • Like 2
  • Thanks 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

YoYo

YoYo

Posted
Posted

Yes, radar sweap doesnt work for me too.

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Bigity

Bigity

Posted
Posted
4 hours ago, schmiefel said:

Just guessing, but that really looks very intentional made by Razbam putting a time-out into their files to stop using the module if there will be no further updates provided. And maybe that's why several AV tools showed a red flag for some files of the F-15E installation recently?

Guessing is right.  

  • Like 1
schmiefel

schmiefel

Posted
Posted
2 minutes ago, Bigity said:

Guessing is right. 

Yes, because I don't know for sure, but something like this specific timestamp doesn't just happen by chance during programming or at least its very, very unlikely that its just a mistake. Draw your own conclusions.

  • Like 2

Primary for DCS and other flightsims: i9 12900K@default OC on MSI Z790 Tomahawk (MS-7D91) | 64 GB DDR5-5600 | Asus TUF RTX3090 Gaming OC | 1x 38"@3840x1600 | 1x 27"@2560x1440 | Windows10Pro64

Spoiler

Secondary: i7 11700k@5.1GHz on MSI Z590 Gaming Force MB| 64 GB DDR4-3200 | PowerColor RX6900XTU Red Devil | 1x 32"@2560*1440 + 1x24"@1980*1200 | Windows10Pro64

Backup: i7 6700K@4.8GHz | 64 GB DDR4-2400 | PowerColor RX5700XT Red Devil | SSD-500/1000GB | 1x49" 32:9 Asus X49VQ 3840x1080 | Windows10Pro64

Flightsim Input Devices: VPC: ACE2 Rudder / WarBRD Base / T-50CM2 Base with 50mm ext. / Alpha-R, Mongoos T-50CM, WarBRD and VFX Grip / T-50CM3 Throttle | VPC Sharka-50 + #2 Controle Panel | TM Cougar MFD-Frames| Rift S - Secondary: TM HOTAS WARTHOG/Cougar Throttle+Stick, F-18-Grip | TM TPR Rudder | DelanClip/PS3-CAM IR-Tracker

Bigity

Bigity

Posted
Posted
Just now, schmiefel said:

Yes, because I don't know for sure, but something like this specific timestamp doesn't just happen by chance during programming or at least its very, very unlikely that its just a mistake. Draw your own conclusions.

Yea, bugs never get into code that apparently have a random trigger.  😄   I'm just saying slow your roll on blaming RB.  Or don't, whatever you feel like. 

  • Like 1
schmiefel

schmiefel

Posted
Posted
3 minutes ago, Bigity said:

apparently have a random trigger

You really think that a certain date that gets passed is a 'random bug trigger'?

  • Like 3

Primary for DCS and other flightsims: i9 12900K@default OC on MSI Z790 Tomahawk (MS-7D91) | 64 GB DDR5-5600 | Asus TUF RTX3090 Gaming OC | 1x 38"@3840x1600 | 1x 27"@2560x1440 | Windows10Pro64

Spoiler

Secondary: i7 11700k@5.1GHz on MSI Z590 Gaming Force MB| 64 GB DDR4-3200 | PowerColor RX6900XTU Red Devil | 1x 32"@2560*1440 + 1x24"@1980*1200 | Windows10Pro64

Backup: i7 6700K@4.8GHz | 64 GB DDR4-2400 | PowerColor RX5700XT Red Devil | SSD-500/1000GB | 1x49" 32:9 Asus X49VQ 3840x1080 | Windows10Pro64

Flightsim Input Devices: VPC: ACE2 Rudder / WarBRD Base / T-50CM2 Base with 50mm ext. / Alpha-R, Mongoos T-50CM, WarBRD and VFX Grip / T-50CM3 Throttle | VPC Sharka-50 + #2 Controle Panel | TM Cougar MFD-Frames| Rift S - Secondary: TM HOTAS WARTHOG/Cougar Throttle+Stick, F-18-Grip | TM TPR Rudder | DelanClip/PS3-CAM IR-Tracker

Bigity

Bigity

Posted
Posted
4 minutes ago, schmiefel said:

You really think that a certain date that gets passed is a 'random bug trigger'?

You think a company trying to get the 7 figures they are owed would do something like this?

 Share
Go to topic listing

  • Recently Browsing   0 members

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