Jump to content

AKRocco

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I started out the same way, went from years of WW2 to DCS. Personally I found the bfm to be similar in a hornet to ww2 aircraft, but needing more precision. What carried over for me were the visual cues, understanding the fight geometry, gunnery, recognizing overshoots, scissors, 1c vs 2c fights, difference in energy states (though I had to relearn the cues for that). Pretty much all bfm basics haven't changed in 100 years, just the speed and altitude where they happen. what was new to me was the importance of maintaining that right corner speed, operating the avionics and countermeasures, breaking the habit of using some ww2 specific tricks that don't work with jets, and needing to react to cues faster than in ww2 sims. I struggle the most in BVR engagements, missile evasion, that kind of thing, because there is no analogue in ww2. boom and zoom only works if it's guns only/they are much slower/underpowered/don't know you're there, and you break off before you get in front of them. There's a saying for the hornet, "go up to blow up". the hornet doesn't do well in the vertical in most situations. against most fighters downhill is the way to go. In a fox 2 environment you definitely can't run. pretty much any aircraft in the game will be able to get nose on and fire before you get out of range. best bet there is get your nose on them before they get nose on you (I know, not super helpful), or at least keep turning so they can't get nose on and wait for them to make a mistake. As for 2v2, with a human wingman communication helps a lot to avoid blue on blue. with AI best advice I can give is always keep an eye on where they are. there may be better ways I don't know about. I don't really know the inner workings of the iff. The missions that helped me were the single missions for the hornet, the 1v1 bfm against the su-30 then the mig-21, moving up to 2v2. and for fox 2 the weapons qualification. I created a few of my own missions that helped a lot as well. Don't be afraid to jump in the mission editor and create your own setups for air to air and air to ground. you can control the opponents skill, relative position, loadouts, and even make them ignore you if you like. Just drop two fighters near each other, make one red and the other client, and go from there. Fighting AI will get you the basics but it is a huge jump going from AI opponents to human ones, it pretty much felt like starting from the beginning again.
  2. Check out Movers YouTube, he has two videos on it from 6 months ago, the fights and a debrief. First video here. I would love another Folds of Honor tournament, had a great time last year. But with all the drama wouldn't be surprised if it doesn't happen.
  3. Squadron Name: None Discord ID on MVP Discord: Sir_Rocco#7778 Contact person Discord ID: Sir_Rocco#7778 Aircraft Selection: F/A-18C Pilots: Canada - Sir_Rocco
  4. Hey man did you get your 1-4 check your display cable error fixed? This seems to be happening across the board with windows mixed reality. My odyssey is doing the same. Also when you unplug your headset and re-plug it in is there an audible sound like you've plugged in a usb device? Sounds strange but mine becomes recognized but without a sound. Whenever I have got it working there's been that you just plugged in a usb device windows sound. I also had some luck uninstalling my usb serial bus controllers in device manager and then restarting to have them reinstall. After the restart I plugged back in to a 3.1 and it worked....until the next restart! Have you also tried command prompt as admin and then sfc /scannow   ?

    1. AKRocco

      AKRocco

      No I never did get my first headset working. The replacement they sent has worked so it was definitely a faulty headset for me. Unfortunately the 1.4 error is not very specific and there's a hundred different things that could cause it.

       

      I did have an issue with the usbs on the mb itself, they were causing stutters in tracking and audio, and I would constantly hear the connect/disconnect sounds. Didn't matter which usb port I used, 2.0, 3.0, 3.1, type C, they all did it. Fix for me was using a powered USB hub. No idea why it would work better than direct but it does for me.

       

      I haven't tried that command prompt command. I do know that there are a few things that register in the device manager for a headset. For the G2 it comes up as a display, a WMR device and under the usb for tracking. If you haven't already I would take a look in there and see which part isn't coming up.

       

      Hope you get your headset running!

    2. cochise

      cochise

      Ah shame man! Yeah I'm thinking I'll try another headset. Once mine works it works flawlessly no stutters or audio crackles which is why it's so baffling. I'm scared to think it might be the motherboard though but it's a possibility! Thanks for the info.

  5. I've tried moving USB ports, USB C, regular USB using the supplied adapter, and using a powered hub. I've tried all my display ports, don't have an adapter to try the HDMI, and tested the ports with a monitor to confirm they work. I uninstalled my video card driver, headset driver, and WMR and reinstalled. Confirmed I had all the Windows updates. Updated my BIOS. Tried all different variations of rebooting and unplugging and plugging in the cables. Only thing I can think of is trying on another rig, I just have to find one.lol The thing is it was working for a bit and I didn't really change anything when it stopped. There are 3 places it should show up in Device Manager, under Mixed Reality Devices, Monitors, and Universal Serial Bus Devices. But after it died it won't show up in Monitors anymore. So that points to Windows not seeing the Displayport connection. Specs : CPU: Intel Core i5-8600K GPU: AMD RX 5700-XT SSD: Samsung 960 Evo NVMe PCIe M.2 250GB (Windows Drive) SSD: WD Blue 3D 500GB SSD : ADATA SU650 500GB RAM: Kingston HyperX Fury 32Gb DDR4 3200MHz (2 x 16Gb) MBD: MSI Z370 SLI PLUS (MS-7B46)
  6. No WMR doesn't keep restarting for me but it's the same error I'm getting, 1-4. From my online searches that error is kind of a catch-all with a bunch of different causes, a lot of the fixes involve reinstalling WMR and video drivers. I used an Oculus cv1 before so this is my first experience with WMR.
  7. Mine arrived on Thursday and I'm already getting an RMA on it. It worked for a bit but as I was setting up steamvr it just stopped working. WMR gives me the 'check your display cable' error and it looks like windows isn't seeing it as a display (doesn't show up as a monitor in device manager). Went through all the fixes I could find online but nothing. Talked to tech support and they told me to get it RMA'd from the reseller, so no idea when I'll get it replaced. Sounds like the cable or headset itself. It was great for the hour or so it worked, I hope I have better luck with the replacement.
  8. Yeah same with me, same issue just last month. It took 3 business days to hear back and another week for the new cable to get to me. Just under two weeks from ticket open to stick fixed.
  9. Congrats Sungho! Make us proud kicking that AI's butt! Thanks to everyone that put in their time and effort to make this event possible. I had a blast competing. I flew some virtual jets, met some great ppl and helped out an amazing cause, can't ask for a better way to spend a couple weekend mornings! See you all at the next one!
×
×
  • Create New...