Was working my way through the exercises on hackthebox.com and every FFUF scan was saying the file size as 0.
Turns out it was Bitdefender’ “Online Threat Protection” ->”Network threat protection”.
This blocks the filesize of FFUF results so the will come out as 0 if you are connected using VirtualBox.
So a few months ago i seen Amazon had a sale on the VR headset ive followed for years the Oculus Rift. It was cheaper than i had ever seen before so i ordered one.
Excitement for Flying in PC VR with Flight Simulator 2020:
I cant begin to describe how excited i was to connect it to my PC in order to play Microsoft Flight Simulator 2020, my entire reason for buying it. I had a PC capable of VR and Graphics card well up for the task.
Problems:
When you connect the Oculus to your PC it does a check to see if everything is ok. You need to plug 1 cable into a USB 3.0 port (no problem I thought, I have loads! Then you plug the other cable into your Graphics card. The software checks to see if all is good.
The Test:
I spent days searching for the problem and hoping there was a simple fix. I read post after post but nothing. i tried everything i read;
USB 3 Ports:
The motherboard i have has 4 USB 3 ports some of them 3.2 gen and above, shouldn’t be any problems!
The Fucking Red-Green Headset Sensor Check nightmare:
Those two green checkmarks you get are great until they go red and you pull the cable out and reinsert and you get it green or red. This plug in and out bullshit fucking killed my interest in the headset.
Sensor cant track headset:
Stuff of nightmares
Researching the problem:
I knew or thought i did that somebody must know the reason for this because Oculus didnt. All the help they give is to disconnect the headset for 10 seconds and reconnect it. The number of times i did that.
The solution:
There’s no way id have ever figured this out without reading a reddit post saying to buy a USB 3 self powered hub from amazon. it sounds so simple, I cant even remember how or why i found the post i did but if i remember right the person said they had the same problem i was mentioning.
The solution came from a comment on the reddit; https://www.reddit.com/r/oculus/comments/f75f3y/oculus_rift_s_turns_off_mid_play_along_with_all/
Last chance saloon:
So i thought nothing else has worked and chanced ordering this from amazon and it worked!
The USB 3 Hub i ordered:
https://www.amazon.co.uk/gp/product/B08ZKSK6MB?ref=em_1p_0_ti&ref_=pe_4028881_605832111
Ever since i upgraded my PC last year, my Windows 10 pc will not go to sleep and neither will the monitor and that’s with a fresh Windows 10 installation. The first thing i did was to press the “Restore default settings for this plan”..didnt work.
I’m really finding it hard to figure out how this is a problem when with my old hardware it was never a problem. The only thing i cant think off is that its the motherboard and some setting in BIOS thats not quite right.
This problem has been happening since i installed the new hardware and for some reason i thought it was normal..but remembered how my old PC would behave it would just go to sleep when the windows 10 power settings told it too.
Hardware Specs:
MSI B 450-A PRO (latest BIOS)
AMD Ryzen 2600
Win 10 64 210h (latest)
32GB DDR 4 3000
Possible fixes:
Solution:
After reading about the same problem being caused by a controller being plugged in, I disconnected the Joystick from my PC and within one min the screen had gone off.
Logitech Extreme 3D pro is causing the the issue:
Logitech Extreme 3D pro
https://www.tenforums.com/performance-maintenance/27004-windows-10-will-not-auto-sleep.html
Sources:
Solution Found Here
https://www.techpowerup.com/forums/threads/monitors-wont-go-to-sleep-why.244167/page-3
When installing windows on a multidrive/boot system you can sometimes get this rather cryptic error message. It relates to how Windows setup sees your Drive partitions. There are two was to solve it;
1) Disconnect all drives from your PC except the one you are installing Windows on.
2) Enter your BIOS and set the hard drive you are installing Windows on to be the top-priority drive.
Either of those should fix the error message.