Jump to content

JiveMiguel

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by JiveMiguel

  1. I am coming back to DCS after a long break. Those training missions are great for getting back into startup/shutdown etc. Is it reasonable to figure that when Caucasus is on the new engine that all those tuts/missions/campaigns will be there too?

  2. Hi everybody- first off, I am loving this module. And in VR it's one of the coolest experiences I have had in gaming.

     

    THE ISSUES: I am having a weird issue with the way the map renders in VR. Essentially, if I look at it straight on, all that renders is the blue/grey background and the icons for planes and such. HOWEVER, if I turn my head to the side, the map renders (in grid chunks) in part- flickering in my periphery. Is this a known issue, or is something perhaps setup incorrectly?

     

    Also, The radio communications seem a little unpredictable. For example, I go into a cold start to fly around from point to point. I seem to have a limited number of times I can use the radio comms before it stops responding. If I ask ATC for startup, and ask the ground crew to run the starter, I can't get a third time to access the menu to request takeoff. I read that people have had better luck using the "push to talk" command of [r alt + \] but it really hasn't changed anything. Both scenarios, I only get a few successful button presses before it just stops doing anything- keyboard and HOTAS behave the same, btw. And in the campaign missions, I can't use the comms AT ALL. After the dogfights, I can't raise ATC when I RTB. Anybody seeing this?

     

    I am running a dk2 with the updated SDK. I don't have any mods installed except for the chat and text enlarger, without which, radio and tooltips become really tough to read. Also, I am running a downloaded version from ED, not steam. I have it indexed in my steam library, but I don't use it (there's a conflict of taking screenshots and the comms menu option of F12)

     

    Any advice on these two issues would be greatly appreciated. Thanks!

     

    EDIT: I rebuilt my install and comms menu is fine now. Map is still borked...

  3. Not yet. They will be available with upcoming official release of Bf109.

     

    Whoa! That is fantastic news! Is there a release date?

     

    I am pretty new to the DCS world, and I am spending the majority of my time in the ww2 aircraft. I have been seeing that there was a Normandy Map that never came to fruition. Do ED have any plans to release a proper WW2 map?

  4. I have been playing around with the MiG21bis and TF 51D trying to figure out what I will map to my HOTAS and what I can just leave to a mouse. Bear with me, because I don't think will be too easy to describe, but here goes:

     

    The new UI has a carat in center view which is kinda fun, but when you're in flight and you want to operate something, you pretty much have to bury your face in the dial. On top of that, if you click on the control you want to manipulate in the cockpit, it actually takes your focus out of DCS and back into windows. Bear in mind, you are happily in your VR lala land not realizing you kinda alt-tabbed out of the program...

     

    If you pull of your headset and look at the other monitors, the mouse is being somewhat locked into the "preview window" of the oculus runtime. So there is some kind of function in place here that is preventing you from clicking all over your desktop while running the game. The problem is, it is not really doing what it is intended to do, so you as soon as you go to touch something in the cockpit, your mouse is released from that oculus mouse lock, and all hell breaks loose.

     

    SO. The question is, can we manipulate an ini file somewhere to change that center mounted carat for the old mouse function? DCS is on the verge of a perfect setup- VR with an interactive cockpit where you can prioritize critical controls to your HOTAS, and things like engine startup routines to mouse clicking in the cabin. To take it one further, I'd imagine having something like leap motion hooking into the mouse is pretty much the holy grail, as you can flip switches just by reaching out with your hands!

     

    I can't explain how much of a dream come true it is to see all of this unfolding :) But back to the question- Anybody got a fix for this mouse issue?

  5. Well, this got moved to Virtual Reality, so I'll assume for now that some of the powers that be understand I am talking about an Oculus Rift.

     

    SDK 1.3 Is not a developmental release, nor is it alpha. It's market.

     

    Looking around on reddit, people are using this hardware with mixed results- mostly good. Seems they are still working on getting it to 100% though. The game runs beautifully, but it's gonna be hard to build up some profiles if I need to close and open the game every time I need to make changes to the profiles.

     

    Hopefully it'll soon be resolved one way or another.

  6. I am running a DK2 with SDK 1.3. It works beautifully in game, but if I quit the game and go back to the menu, all the head tracking is gone. Also the little reticle you use to point and click is frozen. I try to move it with my mouse and it moves a little but snaps back to center. Any suggestions?

     

    Setup:

    AMD FX 9590/Asus Sabertooth 990fx/32GB Ram/Samsung 850 pro SSD

    Strix 980/DK2

    X-55

    Windows 7 x64

     

    That aside, I can't believe what you guys have done in this game. I AM SPEECHLESS! Incredible work!

×
×
  • Create New...