Paveway333

Hi! This is a wish list topic about the same subject as the thread "Helmet in way" by @LavaFlight listed under the F-16C Bugs and Problems section. To make it short, it has to do with the 1st person pilot model (R-Shift+P) in F-16C & F/A-18C. The helmet gets in the way looking over the pilots shoulders at certain angels (it will start to pop in and out), from my understanding this is intentional. When you pass a certain threshold in the Z-axis looking backwards, the pilots head will render so it can be used to take nice screenshots or movies of the highly detailed pilot, witch i understand it looks nice! However this feature can be quite irritating when suddenly a head pops up in your view during a dogfight, this is because the headtracking has slowly creeped forward in the Z-axis during the time your trying to look for the bandit. To fight this problem you can configure the Z-axis to almost no input, but then other stuff becomes a problem, leaning forward to read MFD, Instruments etc. I have way low Z-axis sensitivity settings, but this still happens from time to time. I would welcome a re-review of this feature/problem so that all (movie makers or not) can be satisfied. Here are some ideas: Move the threshold even further forward: Can maybe create new problems i don't know. Make new inputs for further control: R+Shift+P = Show Pilot Body, R+Shift+R-Ctrl+P = Show Pilot body + Head Make the the threshold an On/off state: R+Shift+R+Ctrl+P = Remove Pilot head threshold Make it an option under special options: Probably requires most work I hope i provided you guys with some ideas that maybe can make it in the game some day, thanks!

Why not make it an option? Like: R-Shift+P = Show Pilot Body, R-Shift+R-Ctrl+P = Show pilot body with head (for Screenshot purpose), or even better special options. I understand why it is intentional, it looks awesome in both screenshots and videos, but i can't understand how that has taken priority over a more realistic simulation and immersive gameplay. I like to use the pilots body especially in 16&18 with the nice kneeboard and all, then suddenly in a merge i become a selfie stick, and even then it's far to sensitive seeing the head pop in and out 4 times in a second, because most of us will hang just around the threshold. Please, consider reviewing this again and make all of us non screenshot/video makers happy. Thanks! Edit: Instead of limiting us with special TrackIR curves, in my case I have almost non Z forward movement and yet I get in this situation I know i can turn it off almost completely and probably get rid of this problem. But then i create issues in the other end, problems leaning forward seeing instruments or seeing hud elements in detail etc, that's all. Thanks!

Any news on this? Getting pretty frustrated....

The latest update brought a great feel to the aircraft. However I feel that there is still something off with roll rate, acceleration, g-onset and alpha. I have no evidence to back this up other than 10+ years of watching this aircraft in the air, and in my opinion it seems a bit more agile in real life. Two examples being in this video at this timestamp down below: First, look at that alpha and how he slides trough the air almost backwards, and second look how fast he is accelerating out of that manouvere. Tried to recreate this in DCS so many times, it is not far off so I give the devs credit for that. Recreating stuff like this in game just make it seems that there is a couple of things a little bit off, same with demonstrations off roll rate etc. However like i said they have done an incredible job with the likeness of how she manouvers, just hope they continue refining some details. Thanks!

Approved

Same issue here, randomly freezes for about 15-20 seconds and then works fine again. No USB disconnect sounds etc, happens to both throttle and stick (more often stick).. Actually happens to all four of mine orion 2's (2x throttle and 2x stick base). Sometimes it's really bad and happens a few times in row during a session, and other times I can't trigger the problem for days. Background tasks I often have open are Discord, TrackIR, Steelseries app and sometimes Process Lasso. No clue what is causing this.... =( edit: Would be interesting to see if it is DCS related or if it still happens when the game is closed. edit2: Maybe related, Will try this fix when I get home. i9 12900k, rtx 3090, 32gb ddr5

As probably most people in this forum im in love with how the real Tomcat sounds, the ones currently in game is not bad at all so don't take it as that.. But as a fan of this module, I hope there is time/room for improvements in pretty much all minor details covering the aircraft like vapes etc, witch in turn makes this module more awesome than it already is, mine for now happens to be the "Howling" sounds the aircraft sometime makes. Hope that someday small details like this could be added, keep up the good work! Thanks! @00:55 and @02:55 From timestamp and onwards.

+1 fps at lower 40´s with the new night lightning.. The same problem with night lightning on Sinai map, so maybe this two maps are using the same tech. 12900K, 32gb DDR5, RTX 3090ti flatscreen. - Beautiful, but not usable.

Thanks for the support guys! I now know that steerpoint entry between 26-30 is valid for Jdam attack using DDD’MM.mmm. And that stp also can be shared to member flights. Thanks vking,furiz and backspace340.

Thanks for the info, but can it use precise lat/long or is MGRS precise enough to guide a Jdam? Never used MGRS, only precise lat/long in the Hornet.

Thanks, i Will try that.. It just don’t make any sense to me, if you see a target you would most likely mark it via helmet, hud or overfly - send the data and your flight should receive it as an X on the hsd.. Why should manually entering be any different and what is the reasoning behind even having the ability to enter coords under the mark page if it does not work? Just trying to wrap my head around this, Thanks!

Is there a way to manually enter a markpoint only using F10 map to deploy a Jdam? Can’t figure this out, In my case im trying to find a target and find its position on the map, then mark that location using coordinates taken from F10 and send the markpoint to a human wingman.

+1 been bothered by it since release especially in the Hornet, but I also see it in other modules. It makes the aircrafts look like stiff toys compared to the real thing. Hope someday the teams will look at their 3d models and actually care about details like this. The entire wing lifts and flexes gradually as the forces increase during flight, not only when extreme G's is being applied.

I never said you couldn't fly trough your own turbulence, but I have never seen a Gripen, Hornet or Viper losing control during a Solo display just because of flying trough it's own wake. Numerous of times in DCS have i been flipped almost upside down due to this, if that's accurate I'm pretty sure airshows wouldn't be allowed. Witch brings it to my conclusion that something is flawed in the simulation of wake turbulence, and that's all i meant with that post.

LOL! I live ca 30km from Såtenäs. Don't really get the point of your post though...

I believe the wake turbulance is either incomplete or quite bugged to be honest, cases of aircraft on the ground flipping over etc, as for the Hornet and Viper I do know that they are extremely sensitive to there own "old" leftover turbulence, as is very easy to notice when your'e doing pretend airshows and are flying trough the same spot over and over again. Actually about a month back I lost a wing in the F-18 fighting a friend who was in the Viper, about 20-30 meters behind pulling 6-7g, just as I passed his tail it pitched so violently that I blacked out instantly combined with the lost wing.

+1 (in mission editor)

I'm looking to maybe purchase a 55" 4K OLED TV, does anyone got any experience using something around 55" with trackIR? Seems like the placement of the camera is going to be a problem, not because of the distance but rather the height, thanks!

Im also running my panel limited to 60fps using RTSS. But it's easy to spot when i turn v-sync off and let the frames rise as high as possible, when the frames are stable i turn on all instrument + flood lights and on my end my frames drops from around 160-130 (depending on graphics settings).

Hi, noticed this aswell, around 30fps quite a big drop. So i definitely understand if people with lower end hardware having issues. (Level flight, single aircraft in editor) 8700k @4,8ghz, 32gb ram, RTX 2080ti 2560x1440, 4xmsaa, Shadows High, Cockpit global illumination off, SSAA off

Two things id like to see explained or improved upon: Missile callouts, i don't know if this is true but it often feels that he shouts at everything he see's, even at those who aren't intended for our aircraft, like a SAM far away engaging other aircrafts. Some indication when he's locking targets in TWS, other than monitoring the mirrored radar screen.

Hey guys! I am in need of some serious troubleshooting. Couple of years ago i used to record in dcs, using both shadowplay,obs and bandicam. At the time i owned a 3440x1440 60hz monitor with a Gtx 1080 and the recordings came out perfect. Current hardware consists of a new monitor 2560x1440 144Hz G-Sync and a RTX 2080 TI. Since i bought the new hardware a while back I cannot seem to get smooth recording anymore, doesn't matter if i use OBS or Shadowplay. I get this "frame drop"/"stutter" especially in panning shots. This stutter is not visible when i record in-game, my clips seems ok when I look in the properties (constant 60fps). Have someone of you with similar hardware run into this issue? BTW i use RTTS for capping fps at 60, mostly to get rid of stutter caused by TrackIR that wants either 60 or 120 fps. ____________ Things I've tried: Turn off RTTS. Turn off/enable both G-Sync and V-Sync. Tried booth Fullscreen and Windowed.

Don't know if this bug has been found internally yet, but as of today me and 3 others experienced this during our own mp session. 4 Jets, started Parking Hot with all weapons already loaded. 100% Fuel, 2x Wing Tanks, 2x mk84 and 4x Aim9L, Persian Gulf, no wind. Id say we all noticed this issue pretty early in flight, so low fuel state seems not to be the issue. Have noticed this issue earlier playing around in the editor, was really easy to spot when you fastforward time. Double checked using rctrl+enter making sure no inputs were made from stick or rudder.

Seems to be working fine here.

This is going to be amazing! Can't wait to hear the the new engine sounds. =) BTW have the EA release been changed from Early Autumn? From video: The early access release date is planned for autumn 2019. Our Viper is currently in development and will be released into early access later this year.