Headwarp

Hey thank you for the consideration. :) It's really the only thing I struggle with when trying to use SRS. The hatswitch I leave free for SRS in FC3 is sometimes a countermeasures switch or some other function in a full fidelity pit. It is kind of daunting for me trying to figure out where to put those functions when most of my buttons are already used in most of the clickpits.

>.< Okay. let me rephrase my post :P i'd dedicate a 250GB SSD to DCS World 2.5 Open beta alone. I only have use for one client >.< however, add a few maps and modules and I could see saying the same thing in a year or two. Dat Hornet tho.

The problem doesn't lie in the updater. It has to do with the size of your drives. You can get a 250GB 2.5" sata III SSD for less than the cost of the hornet module. Personally if 250GB was all the space I had on a drive and I wanted to use it for DCS, I would ONLY use it for DCS. Instead, I have a 480GB PNY SSD i picked up for cheap years ago, and it's only half full with DCS, 1 other sim, and 1 other game. SSD's by design also perform better if you leave some free space on them. My build for example has 1 240GB sata III SSD for boot, and any programs/drivers related to my system and peripherals, 1 480GB sata III SSD for simming, 1 480GB SSD for anything I might use on steam, and a 4TB HDD i dedicate to video storage/rendering and maybe older programs that load fast enough without the use of an SSD. I'd really love to have NVME drives but I also live on a budget. So those are items on the wishlist for the time being. Every now and then I get to check an item off that list. I'm not trying to insult your intelligence or anything, but the solution to your dilemma is simple and not the fault of ED. I'll also point out that this advice relates to using a desktop PC, which by chance if you're using a laptop upgrading/swapping out drives may not be so easy or doable at all, although it does provide another example the choices made by the end user relating to the limitations of hardware.

So thankful ED got the TDC axis assignments implemented. In light of some of the other posts in this thread - the lack of IFF is definitely on the top of the list of things I hear about when flying the hornet with friends. While, I'm not demanding it be prioritized or anything like that, it certainly will be nice to have when it gets here. Comments like "special kids" referring to people who don't actively use whatever VoIP you enjoy makes me feel I'm listening to/reading from someone rather "special" myself. Not every one who plays the sim is going to play it your way or have your experience level. No matter what we think or say - buddyspikes from friendly Hornets will likely be something we have to deal with until we get IFF. Nothing has stopped me from successfuly landing on a carrier or a runway at this point. That being said I'm patiently enjoying the updates we're getting, and appreciate having the opportunity to fly this beautiful bug in DCS. Can't wait to see what this thing is like by the end of this year.

Ciribob, was wondering if adding a new dropdown window or something of the sort for allowing the switching of PTT hotkey assignments would be a task you might be willing to undertake. I.E. Some kind of profile I can setup and save for when I switch between aircraft. I have quite a few modules, and I tend to try to match HOTAS diagrams as closely as possible when mapping controls for full fidelity pits, which leaves me conflicted when I switch from an FC3 aircraft to something full fidelity. If nothing else maybe a checkbox that disables hotkey assignments in srs if the "Radio works as PTT" feature means what I think it does. Feel free to clue me in if I'm missing something.

Wags has already confirmed this is a WIP. Don't fret guys. We can work around it in the meantime. Go have fun. ;)

Thank you for the reassurance. I'm sure everyone's been working really hard, so it's extra appreciated.

I'm fairly certain they overlooked or plan to add in the future. "Oops we accidentally added the code for mouse TDC usage" or something hehe. *edit* Wags himself has spoken on this topic - we'll be able to use it in the future for certain. just a matter of when. https://forums.eagle.ru/showpost.php?p=3506178&postcount=5 Rejoice! :)

I'm confident it will be added at some point. Just kind of feels like a no brainer since you can use it with any other aircraft with similar functions. As well as the Warthog being such a popular choice for this community. Not trying to rain on anybody's parade today with the release of such an iconic aircraft. FWIW i only managed about 2 hours of sleep last night, and am squealing with glee sitting in this virtual cockpit. The excitement is real. Just wanted to also add - thank you guys for the 3 position switch functionality off the getgo. This plane is amazing.

Yeah I'm using the Coolie hat (proper designation for the hat you're refering to, not to sound snobby or anything). I'd rather be using the coolie hat for radar elevation since I don't have a rotary on the throttle like the f/a-18c does, as well as for the buttons on the front of the throttle. Hopefully it's just a matter of them programming in axis controls for the TDC. See no reason why they won't be able to, as there are TDC Mouse assignments. . Not too big a deal. I've managed to get around it by putting what should be throttle grip assignments on one of the extra hat switches on the stick, but, it feels wrong lol. I usually match the HOTAS diagrams in the manual as closely as I possibly can. There is really nothing else the Slew Axis is useful for on the WH Throttle IMO, because of its nature to return to center. I'm not even asking for the team to set up a saturation/curve/deadzone profile for it. I can do that much. Just the ability to assign it like every other aircraft with some kind of camera/target designator allows for. I also don't really agree with this thread moving to wishlist rather than bugs and problems, but please don't take that as me attempting to give anyone a hard time. Slew nubs make more sense to me than using my mouse for the task. :) I see this as more as an oversight, no offense. I know you guys have been busy today, I'm not trying to be harsh. Also not going to be upset if this is where this stays.

Don't get me wrong I'm not upset. Just please add this even if slightly unrealistic, I kind of need the slew nub not to be useless to make the most of my WH Throttle. Hope this is planned. I'm stoked to be sitting in a virtual Hornet. I'm quite excited. For me slew nub for TDC is must have. Apologies if this belongs in the bugs and problems thread.

I get it guys. Blue Angels have become an epidemic. But if you're patient, and sweet, soon your Blue Angels will be flying right over your head. Being pushy is not the way my friends. Never is.

you can convert release to Openbeta and vice versa if you'd like. Personally I see no reason to have both clients installed. I pretty much stick to Openbeta myself. Just food for thought.

It's like.. I've been suffering a case of Blue Angels ever since they made the announcement, and tomorrow my Blue Angels are going to fly all over the place.

What matters here is the resolution you play at to begin with and the GPU powering that resolution. And then recognizing that SSAA 2x is basically doubling the amount of pixels and then fitting that image into the original resolution, creating a sharper image. So for Lenny I'm assuming is on a 1080p monitor, 1920x1080 with SSAA 1.5 is like 2880x1620 - a 1070 is capable of running it without much struggle I'd imagine. So if you're running three 1080p monitors, that's 5760x1080, SSAA 1.5 is basically like trying to run 8640x1620, and 2x = 11520x2160. The GPU doesn't exist for that kind of resolution yet, and likely not for some time to come. Hence your system came to a screeching halt when you attempted it. It's like I said earlier in this thread - if you're running 1080p and using a 980Ti or something more powerful - this is probably a decent anti-aliasing option for you, and the reports of people using more GPU power than their monitor requires seems to show they are seeing a benefit from using it. Personally - I'm taking this as a sign that ED is taking steps to give people alternatives for anti-aliasing, and that as a high resolution user eventually I'll be able to get rid of some shimmering/jaggies myself if the next generation of GPU's doesn't solve all my jaggy woes. Patience is a virtue.

G13 is a nifty device, but requires a bit of setting up. Mine gets the most use in DCS flying the Ka-50. I've got the targeting panel configured to the bottom right of it and it sits to the left of my throttle in my obutto frame, and I've got my keyboard on a tray that swivels out to the right, so I also ended up setting the autopilot panel to ins/home/delete/end/pgup/pgdn and like one button from the numpad. I've also set the countermeasures to the right side of the numpad on my keyboard so basically, in a combat situation anything a real ka-50 pilot would have to take his hands off the cyclic or collective for I mimic. I also use the g-13 thumbstick for the left stick in the Viggen on the rare occasion that I fly it. You could map any switch or button press you wanted to it, and it has 3 profiles or 3 functions per button/joystick. You simply program the keybind from in the game to your chosen buttons in the G13. Every single key is programmable, so it's a viable option to eliminate mouse usage. You can even program key combinations aka macros. It also operates my landing gear, but doesn't get a lot of use from me beyond that mostly because I can assign most things to my hotas. I could see it getting a little confusing trying to use it for MFD usage, but I plan to get a set of TM MFD's at some point. Food for thought.

Was experiencing something like this in the SEAD practice mission. First sidearm gets a lock tone but ring is aiming at something closer to me than the sa-8, fire, no kill. Play the same mission again and sidearm locks sa-8 and nails it. Second sidearm won't acquire lock either time, even while the first missile is in flight and the sa-8 is launching at me. May try uninstalling and then reinstalling the module as someone said it helped them with some bugs in another post, although I don't believe he mentioned this one specifically.

SSAA is Supersampling. Think of it this way - if you're running 1080p, and have a video card that is more than what's required to power a 1080p monitor, SSAA is a good option. If you're already running at a higher resolution that is close to or already maxing out your GPU.. SSAA is going to give worse performance.

It's all good. My moniter has a 100hz refresh rate, but it's also g-sync so lower isn't necessarily bad. I can notice less fluidity at 60 fps than say 75 or higher. I'm not saying 60 FPS isn't enjoyable, but with a PC being part of my life for over 20 or more years now my eyes do pick up differences in framerates. I wasn't implying anyone needs to chase a certain framerate. And admittedly - I overlooked brainfart being a VR user. I can't speak for it but I imagine the same applies to the resolution of a VR headset that it would to myself or a 4k user, that with current GPU technology a faster CPU isn't going to help. My wingmates that use VR however don't complain too much when we're flying DCS together, so with that 1080Ti you should be able to find settings that are at least playable currently. And it sounds to me like we're talking what's required to feed your monitor if neither your gpu or CPU are struggling to run DCS :) If I could get 100FPS at all times I'd definitely aim for it having a 100hz monitor. Sure less than 90 fps isn't going to make me nauseus My poor 980Ti is bottlenecking however, and I refuse to upgrade after only one generation lol. I mean, it took intel 6 generations to convince me I wanted a new CPU. My apologies if I've gotten myself a little confused. I'll end this with saying - my frames aren't dropping below 60FPS atm with my current settings, and up high I'm well over. I'm content with that until I feel rich enough to get a new GPU.

SSAA will likely be a decent option for anybody still using a 1080P monitor using anything more powerful than a GTX 980. For those of us already running 21:9 or 4k setups you probably don't want to turn this on. For the guy who said SSAA made his system run better - I'd guess your CPU clockspeeds were a bottleneck for your GPU, and your GPU is taking more of the workload running at a higher resolution, which ultimately should result in a smoother picture.

<1gb sounds like you need a new drive my friend. Doesn't have to be the fastest brand or model. I'd dedicate no smaller than a 240-250GB drive to DCS World currently. Shopping around i saw a 250GB WD Blue 2.5" SSD on sale for $70.. hehe I think I paid twice that for the Kingston 240GB serving as my boot drive years back. I dislike giving advice like "throw money at it" but I try to keep my "combat simming" SSD at no more than half capacity.

SSAA wrecked havoc on my framerate. 1.5x gave me worse FPS than msaa, and 2x was a slideshow. Which - makes sense..considering it's actual Supersampling and I'm playing at a higher than average resolution already. This is probably would have happened if supersampling in NV control panel actually did anything. This option might not be bad for someone running a beefy video card on a 1080p monitor. I think I'll stick with my happy medium of FXAA and high FPS. Actually looking pretty good. Sorry mods for moving slightly off topic here.. I will digress with my statement that 2.5.2 in general - minus new aa options seems to have allowed for a performance increase.

Haha and here I was thinking I'd just gotten the best image quality/performance I could out of this video card/monitor setup in 2.5. Moose, thank you for pointing that out, and for making me feel slightly stupid today. Indeed I do find it to be a good thing when my derp moments being pointed out lead to improvements of any given situation.

You're likely right on that. I've done something that seems to have reduced perceived shimmering on objects/buildings in the distance, which is likely more to do with the texture filtering options in NV control panel and my mind must have attributed that to enabling SS. There's still a slight shimmer but noticeably less than before I started playing around in NV Control Panel on a whim. Having turned off Supersampling and running a couple quick flights - things still looked about the same, albeit I suddenly feel the need to enable it to check and see if those jaggies looking at the wings of the AV8B are still there when I look behind. However at least one part of my post remains true - flying around low alt my FPS rarely drop below 60 at the moment in SP, and only get higher as I climb in altitude. Feel its worth mentioning Trillinear optimization and AF sample options to off reduces shimmers to much more acceptable level, where previously - I felt torn between msaa/lower fps and shimmers/more fps. Have no idea why i had them set to on in the first place.

Trust your keybinds/hotas bindings. Hold the brakes and move the throttle forward slightly if you absolutely must. If you hear the RPM's go up or see the throttle move beyond idle you know the parking lever isn't engaged.