spetsnaz26

hey thanks...thought it must've been nothing new...

2560x1080

I tried to set my resolution to 3840 by 2160 as instructed in the video but the monitor turned black when I clicked 'test'. Is this resolution specific to my VR? I'm using a Odyssey with two 1440x1600 screens. Monitor is a LG g sync monitor. Not sure what's wrong here. Thanks

saw this for the first time today while in VR. Part of the canopy is 'fogged' up to the point of being opaque. It seems to be a graphic artefact as a function of where the sun is and it occurs on the side away from the sun. see my screenshot and graphic setting below. I already lowered my graphics to shameful levels by the way to make it borderline playable.

Looking back you may be right that is tied to fps. I recall very slow trim in VR at about 45fps and below. I literally had to hold trim up on my way taxing to the runway and during takeoff roll. When I disabled VR and the fps shot through 110+, the trim was crisp, even coarse I felt. Maybe the trim mechanism was implemented as a function of frame rate. In that case, it REALLY has to be updated.

1. I believe it's the steamVR loading screen with the dancing three vertical bars in the lower center of a dark grey square. Problem is it almost always pops up at the most inconvenient time in-game. Once it hijacks the game you can't make any input but can still hear the sound effects. It certainly is very very annoying. Is it possible to get rid of this somehow? 2. Another major source of frustration is the game going out of focus without me knowing in VR. This can happen when the mouse somehow goes out of the window (even when the option to keep mouse in window is ticked) and inadvertently clicked other icons on the task bar. This also happened once when an itune update window popped up. The end result is not being able to see the cursor in the cockpit but in one case I was maneuvering and lost control because even stick inputs didn't register in game. Any solution?

I've been using the 3k Odyssey for a while. I've got 8700k @4.9Ghz, 16Gb RAM, 1T SSD just for flight sim, 1080 stock. I can get 45fps (it's capped to 45fps if capable of 45 to 90 I think) only with PD 1.2, MSAA 2x, Anistropic Filtering 2x, tree visibility maxed, and global illumination OFF. other settings all low except the first two (texture?). FPS is barely 20 when in Nellis with other AI aircraft around, but 45 or so once in air and away. I suggest that you get the best card there is if you're particular about performance. by the way, forget about 90fps if you're on stock 1080.

Good to know man, and yes I think some in-game screenshot improvement can really benefit a lot of players. I occasionally disable VR just to admire it on a monitor. Thanks.

Hey thanks Jabbers,I guess that will have to do for now.

well I am not that bothered by resolution per se, but rather by the fisheye effect due to the need to cram a high FOV into a rectangular frame. In the 'all things VR' youtube video the author seems to have quite normal streaming out of VR, not sure why it'd be difficult to take a screenshot? Such a pretty game, real pity if I can't take good pictures.

i assume you're saying viggen playback would soon diverge from..actual history? I thought that was a time compression problem. good tip though thanks.

as far as the L1 L2 thing, having played most of the Red Flag missions, I think most of the time L1 is placed at Lincoln County airport. Note that briefings mention first landing at Lincoln, refuel, and then ferry to Nellis. I never bothered flying back to Nellis, but at least can report that you are supposed to return first to that northern airport close to the marshalling orbit rather than going back directly to Nellis. I do recall one mission where pressing L MAL button took me back to Nellis directly for some reason. Second the sound problem. Close the canopy and only some in-cockpit control sound effects and radio chatter can be heard. Seems not to be Red Flag or NTTR-specific. Recall having same problem in the mini campaign in Caucasus as well.

With the in-game screenshot function the result looks like a very wide angle shot with distortion around the edges. I understand that just like the mirror this is taken from the left eye view. The short question is: how to take a 'normal' screenshot like the ones you get when not in VR?

Strange... Having watched the videos you guys uploaded I failed to see the final steering order. When did you pull trigger? I tried a few pop up attacks after the latest update and found the DYK mode quite usable. 6km pop up to 700m qfe, roll, pull, roll, align, unsafe, wait for distance line and wing symbology, pull trigger and hold, and then the steering order appears as the manual explained. Just when I tried to follow the order the bombs released...looked back and the stick hit quite nicely over the target, although there's significant error between my reticle and final steering order. The whole thing did tend to move down, but I can at least see the wings so that I knew when to pull. I've got a separate question though... No matter how much control input I made to track the steering order, the ring simply kept a constant distance from the reticle (in my case it consistently stayed up and sightly to the right) . Almost seems like it's running away. How is it possible to reduce the error this way?

Thanks man I think my late arrival must have been the problem. Next time I'll watch the clock closely and push on time.

My wingman and I were shot down by 23s just before we could bomb the targets. I looked at the replay in Tacview and found that there were eight Migs roaming the sky west of FEBA and really did a number on us. The F15s hanged way back in the useless CAP orbits all that time. Are we supposed to take on those Migs all by ourselves? I know the briefing said flanking but two Migs came straight at us. I used time compression on my way in up to Irish, not sure if the sequence could have been disrupted. I was also a bit late due to an extra orbit in the marshalling area. but the key point is the F15s appeared to have done nothing.

thanks. that solved my concerns.

You're right with respect to the target waypoint update. I'd have to say if you have to manually switch back to B1 if it has passed before you can do a visual fix, it's a cumbersome design. Within the last km or so to the assumed position of the next waypoint, it's really not that easy to tell if it lies beyond or before the actual fix. One mistake and it's messed up big time, then you have to clear it.

I couldn't find this detail in the manual or YouTube tutorials. For visual fix I haven't tried it but I assume the fix is associated with the closest waypoint, whether or not it has been passed. Say you're supposed to do a visual fix when overflying the cement factory. Before you arrive B1 is already sequenced due to nav error. With B2 displayed, will pressing TV mess up the position by moving B2 to your current position?... For radar fix (not that is usable right now because the radar image is messed up), I assume it always updates the currently active waypoint? It only makes sense this way because you naturally look ahead when doing a radar fix. Even if the cross may be close to the current waypoint on radar, it should still generate an offset as a function of the distance from next waypoint and the cross. Am I right? The target waypoints are exceptions of course.

It's still a Problem. In VR the symbology is really dim against a variety of backgrounds. I strain to see reticles and numbers there. Taking a screenshot in VR doesn't illustrate the program because the screenshot output looks better than in game VR.

I had similar issues during cold starts. The red flag campaign briefing called for 3 degrees up with external tank. but after holding my HOTAS trim switch for a few seconds there's no visible movement, so I gave up. However, notwithstanding a late rotation and alpha warning I was able to fly okay. The trim is just painfully slow. I didn't bother time check if the indicator actually moved in flight. Another earlier thread said viggen trim is slow in VR. I disabled VR yesterday and found the trim to be quick and even coarse (one press of the switch cause too much trim change). I didn't run a controlled experiment to single out the variables but at least can report the trim works albeit inconsistently.

Spent several hours to work this frustrating problem out. Out of fatigue, I disabled VR and retained the graphic settings. Got into a simple viggen bombing training mission to figure out the level bombing question and found that frame rate was only 20 while I usually got 100+ at high preset before. I used CAM to check my utilization and both were very low, around 15% to 25%. Searched this forum to no avail. Changing graphic settings had no effect on fps. I found that changing views sometimes can instantly recover performance but it's not consistent. The only thing that appears to work is to switch DCS in and out of focus in Windows. You can also try alt+enter in game. My result was an immediate increase to full performance. I still haven't tested it enough to confirm a cause and effect relationship, but I have never once encountered this problem before. I always updated DCS and video drivers as soon as they came out. Could this be related to the latest updates or... Switching off VR? Running latest 2.5 open beta on 8700k @4.9ghz, stock 1080.

CCIP mode appears to be more reliable and intuitive than level bombing. The manual's HUD symbology illustrations for level bombing are confusing: when am I supposed to pull the trigger? Only when the distance line appears? Even when I fly fast and at 200m radar altitude, the symbology still moves down out of the HUD before reaching the release point. I found that I could do a CCRP-esque release by holding trigger as soon as I designate the target and let the bombs release automatically. When I did so, the symbology has a reticle, a ring, a radar ranging fin, and three distance lines. I don't know what I'm supposed to do with the ring, because if I follow it with the reticle I enter a shallow climb and the bombs eventually fall way way long. If I maintain 200m, the ring sort of drifts up and eventually out of the view, and automatic bomb release occurs shortly afterwards. I'm usually half a stick long consistently. I've wasted two evenings trying to work this out. Maybe a simple official training mission is needed for each of these modes.

So, given that the Odyssey has higher resolution, does it mean that we need a lower PD to achieve equivalent quality? Taken to the extreme, once we have retina PD VR, there's not much gain to go above PD =1 In DCS, am I correct?

so in the tank busting mission I noticed that sometimes Rb75s were acting weird. One was seen flying vertically up at low altitude and making 'unphysical' turns aimlessly. I suspect that they start to act strangely if the currently locked target gets destroyed by another missile that arrives first. shouldn't the next missile to arrive hit the same target?