Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Notso

  1. Most WSO's are not rated pilots either. Not even civilian PPLs. Some are, most are not. They get almost no actual formal stick and rudder training beyond the basics. I'm a former WSO. I had a commercial ME rating by the time I retired. It still did not make me a USAF manned pilot. I never considered myself a "fighter pilot" in the strict sense of the word as in doing the JOB. But of course fighter WSOs are "fighter pilots" in the community sense. But that's a different topic for another day. There are WSO's that literally go their entire career in the SE and never touch the stick except for brief times. Some don't want to fly. Some but not many. And it's not expected of them. Riding along in the back seat doing your WSO job and occasionally flying the jet for <profanity>s and giggles doesn't make one a pilot even in the loosest of understanding of the word. It is clear that the only one here who is not understanding is YOU. FFS!
  2. Yeah, it should be great for SP. But the REAL fun is to go crewed in MP. If you get two guys working well together, it will be unbeatable IMHO.
  3. One thing to add is that Suites are not tied to engines or other hardware like the radar type. The F-15E fleet is roughly half and half 220s and 220s. They are also currently a mix of APG-70 and -82. Yet all the jets get the current suite OFP. So at the time, All jets had S4+ OFP, but they obviously didn't reengine them. Suites in the -15E are nothing like Blocks in the Viper - where you have both SW and hardware unique to a particular block.
  4. Actually, you don't need the push IN on the Castle. There are two ways of taking command of a display. The first is as described above: Castle IN and release and then castle short press towards the screen you want to take command. The 2nd method is just a LONG press >1 sec towards the desired screen. Both methods work to do the same thing. So if your stick doesn't have the IN option, the long press should work just as well. That's in the FCP only btw. The WSO take command is simply coolie towards which ever screen you want to take command of for that side. So for instance if I want to take command of the R MPD, then I would go coolied LEFT on the right HCU. If I wanted to take command of the R MPCD, then I would go coolie R on the Right HCU.
  5. Yes, you can. Most everything system control wise is controllable from both cockpits once turned on and set up correctly, with a few exceptions. For example, the Auto-Acquisition radar modes are pilot only. As is changing the Master mode. The WSO has some controls in the back like power and mode setup for the TGP, RWR, CMD, ICS, EWWS, etc. But once they are all turned on and set, then either cockpit can use those systems interchangeably. There are a couple of HOTAS functions the Pilot doesn't have that the WSO does and vice versa. But those are the exceptions. I would say 90%+ of the HOTAS can do the same things in either cockpit. The HOTAS switch sequence itself is usually different due to the different control configs - i.e. Front stick & throttle vs The two Hand-controllers in the back. But the end result of the HOTAS sequence is the same. Now "could" a solo pilot fly in combat without a WSO? No, not really unless he didn't need the systems that can only be turned on in the back. Maybe if the Crew chief turned them on once #2 motor was started and before the canopy is closed and before #1 motor was started. Even the story of the reporter flying in "combat" was a very carefully managed event in a very low threat scenario and they really didn't do much except support the wingman. And I'm sure they had to teach her to turn on certain switches in the back once the jet was running and after takeoff. So I wouldn't use that example as proof that pilots can fly the jet solo in combat. My understanding is the EX was redesigned such that they could manage it by themselves in a mostly A/A fight, but retained the rear seat for more complex missions where a WSO would be value added.
  6. Oh jesus, what have I walked into??? Sorry (not sorry) but no. A WSO is not an F-15E pilot. They are NOT trained to fly the airplane even though some can and do on an informal basis. But it does not make them Strike Eagle pilots. Could they land it from the backseat - yes probably some could (and have). But it's completely against regulations and is prohibited unless in an emergency. In fact there are a lot of WSOs who are not interested in flying the jet and are content with doing their job well - and their J-O-B is NOT flying the jet. So for "normal people" a WSO is not a USAF pilot much less specifically a SE pilot.
  7. Agree. That is all about what the bomb does post-release. It's all about the release parameters you are in at the moment you Yeet it at the target. From there the bomb does it's thing. That's what needs to be modeled correctly to have value in the game.
  8. Sorry, but you're way off with your "8 modes". It's a bit more nuanced than that. This ^^
  9. Nice rant, agree with most. In a nutshell it boils down to this for me...... If ED moves in the opposite direction and makes it MORE demanding on VR to the point where the hardware cannot keep up - I will abandon DCS in a blink and never look back. I'm never going back to flat earth flying. The fact that soooo many other titles out there are embracing VR while Ed seems to consider it a sideshow or an afterthought. I'm sure they don't actually consider VR an afterthought. But I suspect that they are so far down the road with their legacy engine, that they are finding it hard to keep up and make improvements in VR with an engine that is not really set up for it. Always the conumdrum. Immersion & Performance. of course.
  10. Not in the same boat at all. For me it's VR or nothing. I gave up flight simming back in the early 2000's (MSFS whatever and Falcon 3.0/4.0, etc) specifically because flat screen flight simming to me was nothing more than playing a game. There was no immersion whatsoever. Of course I'm jaded because I flew real jets for a living for 20+ years. So I'm not your typical case study. In any event, I gave it up until VR became mature despite VR just being a gleam in some computer engineers eyes that far back. Anyway, I digress....... I am running a G2 with a 2080Ti and am loving it. Is it as crisp as a 4K or 8K flat screen? Ofc not. I have most of my settings pretty high and it still runs a good solid 45fps. Could it be better? Sure. But I'd always take a slightly less crisp picture and have the full 3D immersive value i get with VR than EVER go back to flat world.
  11. I do exactly this, but with little pieces of velcro on the center buttons so you can feel the texture. With some practice, I don't have to look under the headset at all. My fingers just naturally find the buttons. I've also built the panel for the MPDs to be very close to where I would see it in the VR cockpit. So it feels fairly natural to reach down to the MFDs that I see and the real ones are right there. It becomes a very natural motion.
  12. Yeah, I think I'd be better off spending that $1500 on a 3090 and look at what comes out in a year or so VR headset wise. Maybe I'll win the lottery and get an XTAL, LOL.
  13. Thanks, that was super helpful! I think I'll stick with the G2 for now. I'd love to have that Huge FOV, but don't want to give up the crispness of G2. I'm pretty sure the reviewer said he was running it at 2K. I wonder if the Pimax would look different running at 8K on a 3090?
  14. Hi all, trying to work through all the posts in this thread. Good info. i'm on the verge of pulling the trigger on an 8KX but wondering if my system will be able to run it decently. I'm running a i9-9900K cpu and a 2080-TI GPU. I'm currently running a Reverb G2 with no issues but am very tempted to test out the 8KX for the wider FOV and higher Rez. Is it worth trying out or should I wait to upgrade the card into a 3080 or 3090 before trying the Pimax? TIA.
  15. Do you need a handcontroller for the 8KX if you're only doing DCS with it? I know you need a base station, but I'm not sure about the controller.
  16. After talking to some gaming SW engineers and visual artists who both use the Pimax 8KX in DCS to good effect - I'm considering getting one. I currently have the Reverb G2 and love it, but find the limited FOV binocular effect is slightly immersion killing. So I'm interesting in trying the wide FOV on the 8KX. Most of the previous stuff I've read on the early Pimax headsets were terrible. But with the 8KX, it seems to me that Pimax have gotten their "stuff" together finally. I'm currently running an i9-9900K with a 2080TI w/32gb. Is this enough to run the 8KX well until the 3080 or 3090 cards become more available? Would like to hear your opinions, especially if you have had both the G2 and the 8KX. Thanks in advance!
  17. I apologize upfront for probably what is a stupid question. But I don’t have the mission editor manual handy and I can’t figure this out. I’m trying to do some night missions in single player, but when I change the time in the weather and time function, when I go try to fly, it says that My mission is delayed start. How do I set a time in the mission editor and then be able to jump right into the flight at that time?
  18. One of the things that bugs me to no end is jumping into an instant action or a training mission that has an airborne spawn as it's starting point, but all the relevant systems are not set up for that particular fight. For instance, in some of the training missions where you do A/A with a bandit(s), the Master arm is not always on, the Countermeasures programs are not set up, A/A mode is not selected, etc etc. So as you're merging with the bandit, you are heads down as soon as you spawn trying to get the switches set correctly before you have to turn with them. And often times you're soaking up a missile shot because your Chaff & flare are off. Lots of similar stuff for A/G too where you are flung into the aircraft on the target run in, but the laser is not armed, the pod is in standby, the Bomb fuzes and programs are not set and there is no way to get them all set correctly when you're often less than 45 sec out. So Please ED - can you set up the aircraft at spawn with the switches already preset for the expected action? I don't have any issue doing it all myself - but not in the 15 sec before I merge with the Fulcrum on my nose lobbing heaters at me while I'm fumbling with the chaff/flare programs.
  19. Hi BN, I just found this thread while doing a search for how to fix some issues with my Reverb G2 settings. I've applied all your settings but not getting anywhere near 90 fps. Depending on how busy the scene is, 50-60 in SP and usually around 45. It's definitely improved over what I had previously, but nothing in the range of what you're seeing. The one thing I didn't see in your screenshots was the Steam VR main screen settings. What do you have the slider set to for the main steam window and what are your other settings set to such as Super Sampling ON/OFF etc. Thank you.
  20. What's not true? Are you able to run betas of either with the current issues?
  21. Very helpful, thank you. I had not thought about reflective surfaces being a factor. Also my Sim pit is right up against a wall on my right side and the left is open to the room. I wonder now if I'm getting any issues with wall color? But I have flown lots in there before with no previous issues, so not sure what's going on.
  22. Ah OK, thanks. So we are talking only the beta for WMR for Steam, correct? Should I turn beta back ON for Steam VR?
  23. Obviously the room lighting is critical for the headsets that are self-contained headtracking..... But I've never really seen it defined as to what is the correct and best way to set up the lighting for ideal performance. I've recently begun to experience issues with my Reverb G2 tracking. At least I'm assuming that is the issue. Here is a description of my symptoms as best as I can think to describe it.... When looking around IN the cockpit, especially looking down trying to find a switch - the whole cockpit floats around and starts "jittering". It does happen when I'm looking straight ahead, but much less so. AS soon as I move my head left or right or especially down - it starts to float around and then snap back, all the while jittering as if you were holding a camera while driving down a gravel road. Other times, there is a definitive stutter at a specific hz rate as if you're you're going tick, tick, tick..... Most of this is while sitting on the ground running. If I look outside of the cockpit, the scene and the world going by is fine. As soon as the cockpit comes back into the FOV - its starts floating and jittering again. If there is a way I could capture that video, I'll post it here so it makes more sense. Not sure how to take video clips in the VR headset. I've run FPS VR while this is going on and the frame rates down seem to change based on whether I'm looking down into the cockpit with the max amount of floating or not - so that's what's leading me to think its a head tracking issue. It's weird though, because I've not had this happen before. It also seems to improve slightly if I turn off my monitor, but it no where eliminates the problem. Any ideas, suggestions, fixes??? Huge TIA!
  • Create New...