captain_dalan

The nose and the string are indeed visible when from completely neutral. It's once you start pulling and rolling g's that the view goes down a bit. Also, when reading the instruments i "kneel" down a bit, usually during taxi. Snapshots from the default neutral view: null This is indeed a major problem, and one i haven't been able to solve thus far. Shifting the PoV forward, makes looking back really awkward, like your seat and headrest are half a meter away or more. Narrowing the PoV on the other hand, can bring the object in their seeming places, but then it feels like you are flying with horse-blinders or a toilet paper over your face. So i usually try to narrow or widen the FoV based on current needs during flight (like in that video) with the radial, but it's not a perfect solution. Suggestions are welcome! EDIT: This is about as close i can get it to the ACM panel without sacrificing too much functionality or distorting the perspective to the level of a refused meal, sent back to the provider the same way it came. Should the sitting position be further up? (FOV is 105 in this case, 130 gave a strong fish-eye effect)

It is and it isn't, like @Hiobsaid, there isn't a single best view for a static PoV. I.E. my current setup (which i will attach bellow) gives a better view over the nose, centers the view at the boresight (allowing for easier turn coordination) and gives better low calls (by Jester) recognition and interpretation. It also gives better low (as in over the canopy) spotting as long as you haven't disabled your lateral in cockpit camera movement (no idea why some people do that). However, the price i pay is that, when centered the gun ammo counter is hidden by the hook handle and the hydraulic switch is not accessible when you remove the cover. Fortunately, my time in VR has gotten me used to moving around in my chair and even more fortunately, i don't suffer from mobility impairments of any kind, so these are easily solved by just a slight nudge to a side, or a lean back. Here's a video of yesterday's test: And a screenshot of the default settings, in case anyone wants to experiment with them further and maybe refine them: If you do, please to write in this thread, i am very interested in your findings and even more so in your modifications and default view preferences!

Yeah, tried it. Unfortunately it didn't work. The stutters did reappear after a while. I am yet to establish any correlation between the mission type i'm in and the time elapsed before they come.

I tried this, and it is what i'm using now, but it has it's limitations. Like no way to lean forward I.E. This is in fact what i've been looking for. Thanks mate, i owe you one! Bookmarking this and trying it ASAP. The FoV won't be an issue, i have that assigned to a rotary, so i can easily change it in real time, depending on what i'm currently doing in the cockpit. Thanks again for the pointers! EDIT: what's the legend behind hAngle, vAngle, x_trans, y_trans, z_trans and rollAngle. EDIT 2: NVM. Trial and error is a fast teacher! Got around to it in no time!

I will keep this in mind. Will explore the option when i have more free time on my hand. Meanwhile the method of eliminating the stutters by starting an NVDEA video recording session 9and stopping it after 10 or so seconds) worked again in this Friday MP 4 hour long session. So i'll stick to it for now. I just have to remember to delete the recorded videos after each session @Flappie you can add this method to a potential workarounds list for people that have similar issues, but can't seem to make the other fixes work for them

I think i definitely fall under the latter, especially as they are persistent and don't respond to changes in settings. They don't even appear after the same elapsed period. Unfortunately i don't have nearly enough free time for that kind methodical purging. I hardly have time for DCS as things stand. And as it's the only game or even software that is susceptible to the phenomenon, i think i will just have to live with it. After all, i have for all these years. And then who knows, maybe some day a migration to a new engine will solve my issues. Meanwhile i'll keep scanning the forums for potential solutions. Thanks for all the help guys!

I actually get stutters when i don't record. Which is what baffles me. Just tried that an hour ago. Seemed to have worked for a while (could be me restarting the PC and DCS) and then the stutters came back I tried to correlate what tasks spike in disk usage when the stutters appear, and i get this: Not much use, i know Tried this as well, just to be sure. Didn't have any effect, for better or for worse

Yeah, but i never used nor use v-sync. It's always been disabled on my installation. Did give the disable hot plug a go. Will see how it reacts the next time i test. Thanks for the inputs!

Something interesting happened while i was trying to record a longer video with the stutters today. As usual i recorded with the NVIDEA experience. After about 10 -12 seconds of recording, the stutters disappear. So it seems disk activity definitely plays a part here. But it doesn't seem to be a memory, GPU or CPU issue, as those don't change at all, neither do they peak out. My first suspect would be defragment tools, but i have those suspended. Whatever it is, it stops as soon as NVE starts writing the recording. Weird. I marked the point when the recording starts, there is clearly a small spike in CPU usage, and the GPU plateaus, but unexpectedly stutters are gone. The only thing the corelates is the disk activity going to minimal. And that's C drive, my system and virtual memory file drive.

Aye. Can't remember when exactly, so it must have been off for a long time now: You mean disabling the VSync? Yeah, i think i've never had it enabled at all.

That's only been around since april i think, when i got the new mouse, but the stutters were here since ever. Never the less, i will kill the task next time the stutter reappears and report the effects! Oh yeah, both the main folder and the saved games folder, just to be on the safe side.

They are more of hiccups then stutters. I call them micro cause they usually last less then a second, and this video is them at their absolute worst. As for what's running beside DCS, this is the average list of processes on an average day (DCS excluded) That is, not much. And most of the time i don' get them. But when i do, sometimes (though i haven't always checked) the System goes up.

@IronMike? Anyone?

Hey guys, i need some help (like the title suggests) with creating a new default view for the F-14. After much experimentation i found out what works best for me, most of the time. And it looks something like this (the FoV isn't important here, the the direction of the "forward being towards the bore" does: I tried saving the look through the face tracking software but it doesn't work that well for me, so i'd like the make this a more permanent. Can anyone translate this view into a preset and instruct me how to make the changes to DCS myself? Thanks in advance!

I got "lucky" tonight, if lucky is the word we can use here, and the stutters returned. I got a literal 5 to 12 call from a buddy in London for a short MP session, so jumped into DCS to warm up before flight. Punched the BFM instant action on the Caucasus map and bingo, stutters from the get go. Here's a short video of how they look like, with the performance window opened as well. Adding the priority line to an alternate shortcut leading directly to the DCS exe seems to have resolved the issue. Performance on the Through the Inferno wasn't great, but that was a server wide issue, not specific to me. Is this the kind of stutters you guys were having?

Will keep this in mind, thanks! Last night and the night before i couldn't reproduce the issue, so maybe the power service was a fix. The stutters can occur on cycling through full screen or not, but that's a different matter and an even easier fix. Bookmarking this discussion!

Another possibly related issue. Instant actions Syria - Lebanon Free Flight and Syria Devil's Edge BVR, both hot-starts, start with left and right oil temp warning lights on. Not sure if these are the only missions that do, but so far, it's the one's i've noticed in which this happens.

Tried all the missions i did last night, with the same settings, and flew for about 2 and half hours. There were drops in performance naturally, but the repeating hiccups didn't occur this time around. This is my GPU usage from min to max. All on Syria map. I did some other missions, including aerial refuels and dogfights, just to tax the machine. This is the best i could get. Thoughts?

Roger!

Will try that tonight, when i get at home. Question 1: shouldn't VRAM, RAM and page file clear as i turn off DCS though? The stutters persist after it restart it manually. They only stop if it restarts itself when i change the settings. EDIT: it also happens on any map, it just happens to be Nevada and Syria i use most often. Once it does appear, it continues on any map as well. Question 2: What parameter i am supposed to observe here exactly? <enclosed screenshot> Or one of these?

Someone should give this man a medal, and this thread a sticky! kudos!

And tail lights always flash in DCS. Are they supposed to be that way?

+1 for nav-grid-center airplane shortcut. This would golden for campaigns and actual missions, just like shortcuts for TID range are now. Also, is it possible to add a feature that would let us chose between Jester calling out bandit positions or airspeed during dogfights? Possibly in the dogfight menu? I know many people rely on the airspeed cues, but personally i find them of little use, and would prefer for him to scan for bandits, especially in multi bandit engagements.

I noticed did during this evening's playing around with the Devil's Edge (F-14A) BVR instant action on the Syria map. It's a specific mission, as it's set around sunset. Sometimes, the HUD at the start would be in the default green tint, and sometimes in the red one. This is where the funny business starts. When the HUD is red at the start of the mission the handle that changes the HUD color isn't pulled. And pulling it, doesn't change the state of the HUD, naturally, as the act of pulling it, should switch it to red. Pushing it back switches the HUD to green. If the HUD is green at the start, pulling the handle switches it to red and vice versa, as expected. By the way, the mission was never started with fly again option, but started through the instant action menu. On one of these runs, i git poked in the right engine by an R-73. As a result the engine died, i entered into a low altitude flat spin and immediately ejected. As is a known and long lasting bug, every other mission start in an F-14A, be it on this mission or any other, resulted in a state of the right engine being dead from the very start. Taking another plane (even if it's an F-14B, even on the same mission), resolves the bug. Hypothesis, can these two bugs be related? Is it possible that on each instantiation of the F-14, the variables aren't properly reset to their defaults? Thus resulting in lingering states between missions/spawns? This was all in SP mind you, so no server-client issues.

Some thread revival here, as i may have some helpful info. For the longest time i suffered from periodic hiccups in performance, that wouldn't always hit, but when they did they stayed there indefinitely, even after i restarted DCS. So about a week ago i found this forum and decided to try the disable power service and disable my anti virus during play. Lo and behold, this helped and the stutters did disappear. Until tonight that is. I flew around doing AAR, CASE I's and some instant action missions with no issues. And then i switched to a free flight mission during sunset. As i flew low over Beirut with all the city lights on the performance dropped (expectedly) from around 50 (my average) to around 30 or slightly bellow. This is when the funky stuff started again. After i flew over Beirut and into the sea, the average FPS got back to 50, but every few seconds it would drop to 30 or bellow. So turned off the mission. Started another mission in daylight and over desert. The stutters are back there as well. I change the map and the stutters remain. I turn off DCS, start it again and the stutters are still present. So in a moment of inspiration i change the resolution of DCS to the next lower 16:9 one (i was on 1980 x 1080 by default), DCS restarts itself for the settings to take effect, i start the same mission on Syria in brad daylight......et voila! The stutters are gone. I exit the mission, change the resolution to the default one, DCS restarts itself and the stutters are no longer there. I start flying real low, like treetop low over a densely forested area, the performance drops, and after i clear the area, the stutters are back. So what ever causes the stutters seems to go away when DCS restarts itself during settings change, but not during manual shut down of the program. @Flappie Did someone report or noticed anything similar thus far?