Aces High Bulletin Board
Special Events Forums => Friday Squad Operations => Topic started by: Rocco on March 12, 2026, 01:55:10 PM
-
Let me know if there are any questions.
:salute
-
Appreciate the work put into it :cheers: :salute
-
Just FYI, Kill Shooter was enabled/on tonight first frame.
Someone flew between me and my target and it musta been a head shot because 1 strike and I was out.
MOST OF ALL, thanks for the time change, it's now within my reach of playing. <S>
-
if i recall Kill shooter is alway's on because I have hit Friendlies before and credited for a friendly kill so ya have to watch out at times these things happen
-
Kill shooter should only be on for initial take off and then off for the rest of the night.
-
I could swear (based on memory)I read it was set to Off. I’m not complaining, just making note.
Ya can’t blue print my situation. I’m firing and a plane flew 90 degrees between us, no reaction time. Couldn’t have been more than .5 seconds and a head shot. <blank stare> Ya have to laugh because ya can’t plan or react for that.
-
My system kept crashing. I updated a few drivers yesterday. Trying to figure out the problem.
-
My system kept crashing. I updated a few drivers yesterday. Trying to figure out the problem.
Try a rollback.
If that doesn’t work take it to tech support forum. We’ll figure something out.
-
Just FYI, Kill Shooter was enabled/on tonight first frame.
Someone flew between me and my target and it musta been a head shot because 1 strike and I was out.
MOST OF ALL, thanks for the time change, it's now within my reach of playing. <S>
Killshooter is ON at takeoff for a few minutes... at about T+10 it is shut off.
-
My system kept crashing.
I hoped you would make it back in, at least after T+30 when the fields are open for the rest of the night.
Of course, it could have been worse, when I was working on opening the field back up for you... (no idea how it happened), I was trying to run the Flight ON script, noticed my radio buffer was open... rushing to clear it... enter, enter, enter....................
Just as reports were coming in that Spits and Lancasters were spotted :furious
:salute
-
Killshooter is ON at takeoff for a few minutes... at about T+10 it is shut off.
You’d have to check logs, but pretty sure this happened well past T+10. It was also pointed out on country ch.
-
21:32 JazzCH was awarded the kill as you “crashed” maybe it was on… idk without looking at film.
If it was on and you died by hitting friendly just know that if it was off you would have killed that friendly.
-
21:32 JazzCH was awarded the kill as you “crashed” maybe it was on… idk without looking at film.
If it was on and you died by hitting friendly just know that if it was off you would have killed that friendly.
21.32.45 - The chart I see the reward is empty. I didn't film.
1ijac also had the same issue. I think he hit himself 4 times and died. he was the one who mentioned it on country channel.
1 or 2 others, but I forget who they were.
I think Rocco verified it was on.
It's not a massive deal, I was just going by what I read vs what happened.
It was still fun.
-
21.32.45 - The chart I see the reward is empty. I didn't film.
1ijac also had the same issue. I think he hit himself 4 times and died. he was the one who mentioned it on country channel.
1 or 2 others, but I forget who they were.
I think Rocco verified it was on.
It's not a massive deal, I was just going by what I read vs what happened.
It was still fun.
The point I would like to make... if it was on, no one reported it to me. I'm not on the Allied side, so I certainly didn't know about it.
Please note that the only cross channel communications the CMs have is monitoring text channel 202.
-
I hoped you would make it back in, at least after T+30 when the fields are open for the rest of the night.
Of course, it could have been worse, when I was working on opening the field back up for you... (no idea how it happened), I was trying to run the Flight ON script, noticed my radio buffer was open... rushing to clear it... enter, enter, enter....................
Just as reports were coming in that Spits and Lancasters were spotted :furious
:salute
Thanks for your help Sir. Unfortunately, when you said go my VR headset froze for the 2nd time. Apparently, there is a problem with the latest NVIDIA driver and the Meta Quest Link. Still have not found a solution. Rolled back the NVIDA driver but still seeing the problem.
-
Just a thought... are you flying with the headset wired?
I only ask because I had similar issues which turned out to be the USB cable from headset to computer. First time it happened, I thought "No way this is the culprit". Boom, fixed. Second time it started happening, I had a new cable on the way from Amazon immediately and it has been behaving ever since. It would seem the cables definitely have a shelf life :uhoh
-
Just a thought... are you flying with the headset wired?
I only ask because I had similar issues which turned out to be the USB cable from headset to computer. First time it happened, I thought "No way this is the culprit". Boom, fixed. Second time it started happening, I had a new cable on the way from Amazon immediately and it has been behaving ever since. It would seem the cables definitely have a shelf life :uhoh
Ill give that a try. Should have one tomorrow.
-
In my biz, 90% of the time the issue is a cable/connector.
Many times cables will go bad within 3 inches of the connector.
This is usually because thats usually where the stress occurs because it’s usually bent there from cable weight OR the cable moves a lot when connected.
Fractures in the wire can build up to a break.
Vocal mic cable go first.
Usb connection can wear out. Again weight of the cable or movement start wearing in the female connection metals.
We don’t buy any molded cable. Because it gets used and wrapped up nightly we know we’ll have to chop the last 6” off and reinstall the connector.
An install where the stress of the cables is held up and fixed to a case wall…..last a long time.
-
New cable no joy. It froze up on me before I could get my gear up. It's not the game. It has something to do with Meta, NVIDIA, or Windows and it only hates me apparently. Last Friday I updated the NVIDIA drivers and updated the Windows patching. I generally operate as an IT Pro from the bleeding edge so I got cut :(. I like the new cable. There are few upgrades from the one I bought a long time ago. I guess I need to start ripping into rolling back updates. Was hoping for Meta to update drivers but that has not happened.