Jump to content

Wicked.-

Members
  • Posts

    703
  • Joined

  • Last visited

Everything posted by Wicked.-

  1. YO PANTHER! Hope all is well with you and yours girl!
  2. The SRS GUI does not display on this new release for me. Is there something I'm doing wrong in the install? It IS connecting to the server and functioning but I can't change channels in FC3 aircraft without the GUI. Thanks
  3. I picked up a gen 1 Odyssey to possibly replace my Rift which I've used for over a year now. The Rift speakers quit working and I wanted to see if the odyssey would be better. After installing steam VR and WMR for steam I fired up DCS and the eyes are out of sync. Everything is crystal clear while in the WMR and steam VR app but the minute I start DCS the main screen is out of sync and stays that way after launching an instant action. My IPD on the headset is 60 and as I said it's clear when not in DCS. Changing IPD in game doesn't effect the physical IPD of the unit but instead changes the size of the world around me. I changed it anyway to match the physical IPD with zero effect. I also changed the PD with no effect. Is it just a bad headset or has anyone had this problem and fixed it? Thanks
  4. Crab, was the last part of your post for me?
  5. So, I bought another Odyssey today (original) and set it up. Within the WMR home app everything is clear. But when I fire up DCS the main screen is so out of focus I have to close an eye to see clear enough to click exit before I puke! Lol. I left my Rift settings the same which is, PD 1.5 and IPD (in game) 55. Again, everything is nice and clear until I get into DCS, then it's out of focus so it's not the lenses physically being out of alignment but obviously software. Any ideas on how to get it synced right? Thanks,
  6. Wow! Pretty damn close to what I've mapped. At a glance, (filling in blanks) I have engine operate switches as crank left and right and engine flow to move throttles to idlle left and right. They also shut off the engines as well. APU start I use for APU start lol. Everything else is very close to what I have other than your master mode switch. I have mine set to the boat switch because if you select the mode twice it turns it off and back to nav.
  7. It can do that and much more including timed holds on switches that trigger a different action.
  8. You should swing by the 107th. It's got a Multiviper kind of feel..
  9. I assigned it to the slider on the Warthog and it doesn't really do the job. I'm setting mine to the red China hat since it's spring loaded. None of this would be much of a problem if the TDC slew axis worked and I didn't need to use a hat for it.. But hey.. It's beta..
  10. Throttle Designator Contoller up, down, left, right, depress. It's in the Throttle Grip Catagory.
  11. Since the most recent patch, the F-15 radar will drop lock on a target and for the life of me I can't figure out why. I fly in a wing on the 107th and our specialty is air superiority. All A2A all the time so I'm very familiar with the behavior of the radar. That is until this most recent patch. I can be head on, within 20 miles, at the same angels as the bandit, have him "bugged" only in TWS or hard locked in STT and out of the blue I'll lose lock. I'm flying in the Persian Gulf, over the water when this happens so the bandit is not being terrain masked. After watching Multiple Tacview replays the bandit is still headed nose hot when this happens and holding the same angels. It happens mainly against the F16 but also on the 29, 27, 33 and F4. I typically don't bug a target till around 30 miles and sometimes closer but as we're closing on each other the lock will break. Is anyone experiencing this? Could it be the PG map? Did something get porked in the patch, did all AI fighters get cloaking devices? I've noticed other new behavior from AI which is good though. They will launch home on jam if within 20 miles with great effect. They don't react when you fox on them while in TWS (which is the correct behavior) and overall they're smarter. Which means I need my radar to work! You can't tell me the mainstay American/Israeli front line air superiority fighter's radar is this fickle... Anyway, I wanted to see if anyone else has had the same issues.
  12. Thank you sir!
  13. Well said. Not only do you know where a friendly is in relation to bullseye, you'll know where targets are as well. Weather AG or AA. Whether you slew your radar cursor over the contact or lock it up you get a bullseye coordinate for it that can be communicated to other pilots. This is one way of building SA on the battlefield/theatre in real time. I realize there are only a few aircraft in DCS with the ability to show bullseye by a wayport or INS. However, aircraft like the F-15C have the ability in real life. So, without trying to add a feature in an older module I'm looking for a way to extract the data that shows your current bullseye or a contacts current bullseye like we're able to do with gauges for Helios. I'm asking this of the developers and modder's and a simple yes or no will suffice. This post is not meant to be a DCS/BMS comparison. I simply want to know if the data can be extracted because I know it's there. Persian Gulf kicks ass by the way! Happy flying!
  14. My first question is: Does DCS keep real time bullseye coordinates on each aircraft when in multi player? If so, is there a way by some keystroke to see your aircraft's bullseye in the corner of the screen? Like an SA bar? Thanks, Wicked
  15. Got it. Card was overheating.
  16. So I hopped on the 104th server to check out the Persian Gulf map after DL'ing and I noticed horizontal lines in the Rift. Anyone else experience this yet?
  17. Never mind! I had bound button 15 in the UI. Once I unbound it and uncaged a mav...... It all works again!! Woohoo!
  18. Roger that. It works fine for me in Windows hardware settings but not in the Harrier. I'll try a different module. Are you using today's update? Thanks
  19. I fired up DCS 2.5.1 today after the update to see if the mavs were working on the Harrier (no) and noticed my uncage button for mavericks wasn't working. It's assigned to button 15 on my Warthog which is the big red button used for AP on the A10C. When I went to controller settings to check it, I found it doesn't register at all and was in fact bound correctly. Is this just part of the mavericks being porked right now or something new?
  20. Cockpit resolution is only for your monitor when not using the Rift. The mirror you see on your monitor is from your left eye.
  21. I've spent three months jacking with my settings and came to the conclusion that MSAA sucks in conjunction with DS and leave it off. The higher the PD the better everything will look in the pit. Some pits (like the Mirage) have graphics issues regardless of PD. The higher the PD the better everything will look but.... it is harder to make out aircraft at a distance as the pixels are smaller. Going more than 1.8PD is pointless as there is no noticeable visual improvement. Honestly there's hardly any from 1.7-1.8. As of the 2.5.1 open beta, I can run 1.8PD with all settings maxed except I keep all shadows flat, heat blur off, cockpit displays 1024, MSAA off, cockpit global lighting off, chimney smoke off, depth of field off, and AF 16X. I could not do this with 2.5 stable or 2.5 open beta. Gauges and dials are all about PD and textures being high. Nothing else will fix it.
  22. Ok, ok, ok. Take my money!
  23. Turn off MSAA. It doesn't play well with DS.
  24. I've experienced the opposite. Going from 1.4 to 1.7 made such a difference I stopped buying hardware lol. With high textures it's absolutely stunning how much detail you see on things like the seat cushions, canopy ledges and other parts of the cockpit and ZERO jaggies or shimmering. Then again I've flown Falcon and BMS for decades so my standards for graphics are low other than in the cockpit itself which has been awesome since Aeyes released the first superpits with Falcon SP3. I do have issues picking up ground targets above 1,000 feet and in TGP or Mav displays but not enough to kill the immersion or me ;).. FragBum, have you tried my settings? For shits and giggles I would turn MSAA off, bump up your cockpit displays to 1024, no cockpit global lighting and set your PD to 1.7. See what that looks like. While it is slightly blurrier in 2.5.1 it's still looks fantastic. Lastly, I've noticed that the weather makes a massive difference in how things look in the cockpit as well. Overcast days look like shit!
×
×
  • Create New...