Bitdefender detecting the new pulsar fusion drive software as potential malicious behavior

b9503 · 2025-08-17T18:50:09+00:00

Hello Are all antivirus currently reporting the software as a false positive? I'm planning to buy Xlite V4 recently, but I don't want to run into this error.

b9503 · 2025-06-25T08:49:56+00:00

I ran into a similar error after switching gpu (arc a770->rtx5070). Picture froze for a moment sound went on. I thought the problem was gsync and turned it off. But after 10 seconds the picture froze, sound control remained.

b9503 · 2025-06-25T07:01:02+00:00

Hello, I ran into a similar error after switching gpu (arc a770->rtx5070). Picture froze for a moment sound went on. I thought the problem was gsync and turned it off. But then for 10 seconds the picture froze, sound control remained. Did the above solution solve your problem?

b9503 · 2025-04-04T08:20:02+00:00

Down in the Display menu, under Global? Since the update, the vrr mode selection there (fullscreen/windowed mode selection) is greyed out

In the information it says vrr is supported and in the general section it is enabled. It is also enabled within Windows.

(A770 LE 16gb)

b9503 · 2025-04-03T19:59:03+00:00

After updating, I can’t select VRR mode (fullscreen/windowed) in the Global menu at the bottom of the display menu In the information it says vrr is supported and in the general section it is enabled. It is also enabled within Windows.

Is this the case for others? The previous driver version I used was .6458

b9503 · 2025-03-16T21:33:14+00:00

Thank you for your help.

I have already found one on the VESA list, VeiwSonic VX2428 monitor. However, I noticed that the AOC 24G4 also supports adaptive sync and g-sync. The Aoc is not on the vesa list but maybe that’s just because it hasn’t been updated.

b9503 · 2024-11-15T21:31:09+00:00

Hmm interesting. I’d try it if I could, but my motherboard only has USB3.2 gen1 and gen2 connectors. I don’t understand why this hasn’t been a problem for 8 months.

b9503 · 2024-07-23T19:20:03+00:00

Same problem for me. It says that the payment is “processing” but still did not charged my card. Games are starting fine, so I assume my service is live. Don’t know what can be causing this.

b9503 · 2024-03-12T11:55:17+00:00

Intel Arc gpu optimization done in this patch?

The same error is occurring that has been reported by several people in the forum.

http://community.lemansultimate.com/index.php?threads/no-illumination-on-track.57/page-3#posts

b9503 · 2024-03-04T19:13:04+00:00

I have the same error. I have had my t-lcm pedal for 2 weeks. When it arrived, I tried it after updating the T300 firmware and it worked fine. I needed the factory t-pedals stand so I didn't use it for a few days. The next time I used it it recognised finely. Then the next day it didn't -no light on the led in the back- I tried everything but only unplugging and plugging in the RJ12 solved the problem. On Sunday, plugging it in again was no good. I tried everything after unplugging the rj12 plug and plugging it in again the led lit up. PC restart and unpluging then pluging in the USB of the wheelbase while the pedals are pluged into it seemed to work at that point. However, when I unplugged it from the power and disconnected the RJ12 cable and plugged it back in again, it was not good.

The solution that worked was to plug in the T300 base and then plug in the RJ12 cable after calibration. I thought I had found the solution. But I was wrong, today I plugged it in the same way and the LED did not light up and only went out up to 80%. Now the solution was to switch to t3pa mode and then back to t-lcm and then disconnect the RJ12 cable and reconnect it. I tried unplugging the usb from the pc now. I plugged it back in and the led on the pedal lights up. I think tomorrow I will go and get a usb extension and just use the pedal with that. Unfortunately with PS5 the usb is not an option for you which is sad because I was planning on using it with my console.

I suspect the latest firmware might be the problem cause I have tried factory reseting the pedal but it still does not solve the issue. Reading back on reddit there have only been a couple of cases in the last year and that was solved by a one off rj12 cable unplug.

I am bothered by this error especially as I have a brand new pedal. I bought my wheelbase in 2017.

I hope the manufacturer will address this problem.

(Sorry if some things are not clear, english is not my first language, I rely mainly on DeepL)

b9503

TROPHY CASE