Stal2k

Harli, what does fine mine? Is it pretty much locked at the 1/2 frame rate for motion smoothing?

I, like many, have been super underwhelmed with a recent hardware upgrade in regards to DCS. I went from a 1080 to a 2080 ti keeping the same i7 7700k CPU w/ 16gb ram. I'm sure everyone has seen or heard it before but I really hadn't done much research into it prior to purchasing as it was really kind of a birthday gift too myself. After loading up DCS with high expectations of no longer seeing double aircraft when dogfighting or being in the 20fps range if anything is actually going on, or god help multiplayer I was certainly jolted back to reality. Now I didn't JUST get the 2080 ti for DCS, but I certainly had it in mind. I've seen a few posts on reddit, some chat threads on ED Discord and even the odd forum post here and there with people coming to the same conclusion. Obviously, a lot of headway can be made on the DCS side but in the meantime, I'm wondering if ANYONE has "acceptable" performance on their VR rig, and what that is defined by. I see all the people talking about playing with ASW/Reprojection off but what kind of monster do you have to be to do that? I can't stand to see the cockpit blur like I've had 6 beers when I move my head. This goes for either Steam or Oculus VR, it's now about the same. Even with ASW/Motion smoothing off it seems like DCS has it's own forced vsync enabled, I'm still locked to 40 or 45 (depending on HMD). So I guess the bottom line responses I'd love to see are If you think your performance is acceptable, in single and/or multi? What CPU/GPU and mb of ram are you running Some detail on settings to achieve this This isn't meant to be a thread looking for advice on do this, don't do that OC, don't OC, mhz is king, a used 1080 ti would have been cheaper etc.. it's just truly trying to get a pulse on what people think is "good enough for now" and what it takes to get there hardware/settings wise.

Can you elaborate in case it could help anyone else out :) ? You mean crappy oc job on GPU or CPU? What did you use to diagnose this (if anything) and what did you end up doing?

Let me just warn you, someone else said it earlier but as someone who just got a nice new 2080 ti FTW 3 hybrid water cooled monster, DCS still runs like shit in VR after hours of tweaking. Also, like someone else mentioned for whatever reason Rift S runs it better (have both as well). My CPU/GPU frametime is rediculous and only utilizing 60% of the GPU and roughly same of CPU (although single core). It doesn't matter if I set it to potato mode or crank the SS and MSAA up it's still like locked to 40fps or 15-20 if anything is going on. I will say that for some strange reason, the SS of 1.8 seems to actually run better than any other SS setting even 1.0. I've been flipping back and forth between HMDs trying to decide if this index is going back or not, and it ain't looking good lol. The worse part about the Index is SteamVR to be honest, it's been a dumpster fire since the Vive and it's gotten *better* admittedly but it's still like the difference between an Iphone and an Android (when Android first came out). The way Oculus handles the ASW (reprojection) is just so much more graceful than Valve's at this point. Oh well sorry to vent on this thread but after 2 days of tweaking I came here to actually see if someone was claiming to be running DCS at an acceptable performance rate on "top end" hardware so I could see what I was missing.

Nice, looking forward to those updates.

My kneejerk response to that would be 1) a big fat note in the description of the "Default POV Hat Function in VR" value since that initially causes the conflict w/ profile JPG you mentioned and also on the profile JPGs themselves. It's easy enough to figure out the padlock views don't work but I won't lie sometimes I get lost in the sauce on a profile JPG like the F18 MFD notes. Too much for me with the whole green, green italics, green in a box sometimes is bold sometimes green text in a box is green, sometimes it black... wait is that bolded.. shit it's lowercase bolded and underlined etc :) I'm exaggerating a bit but because of that and because of my lack of ability to quickly reference them (VR) I tend to remember them just based on trial/error and less if the legend is so complicated. I do tend to read and put the most stock in the box at the top left of a profile, so those with station switching maybe use a different color entirely to cause someone to check the notes/top box and notate it there. As for thought starters, I can think of two different routes.. both of which are probably more than you'd want to undertake short of a major version bump. Path 1 *Make a few more Profile JPGs to accommodate major hardware differences like VR or if you end up supporting F18 grip etc. Keep those in a repository until the "Build script" function is invoked, at that time it would select the appropriate JPGs from the repository and place them in the folders they all currently occupy. This would idiot proof it to a degree and require the least amount of upfront work Path 2 *Move to an HTML format instead of JPG so they can be dynamically populated based on configuration. I'm not sure how folks use these, but I assume they either have them open on the desktop or print them. In either case a move to HTML shouldn't really hurt anything. Obviously, this would require a fairly significant time sink up front but depending on your plans for CTS might actually make things easier down the road and certainly reduce any human errors/omissions related to manually updating profile JPGs. **To be clear virtually all values would be 'dynamic' in the sense that when you made a change/updated a profile you wouldn't have to redo the HTML, it'd be generated when the user clicks build script reflective of that script.

Oooook... so I feel a bit silly now. I blame this on me misreading the Profile JPG, maybe I'm not the only one but I'll explain :) It never occurred to me to try to do it unshifted, and I guess if I read the legend it DOES say italics *can* apply to shifted commands and I assumed being as the position text was red that it meant to use S3 (which did work in 2.32). I just checked the following using event tester and it all checks out. Pilot/Rio switching and APU lantirn remapping both seem to work, I tested lantirn with the H3D giving me a shift+downarrow with APU on and with it off nothing got logged in the keystroke. For the Huey, the same thing happened since I never even tried it unshifted - works fine. Sorry for the false alarm.

Thanks, I can confirm this is true on the Huey as well, I assume whatever you changed between 2.32 - 2.33 inadvertently killed the functionality that worked (with a double tap) in 2.32. The trim switch still respects the unshifted trim flag but will only behave as the VR mouse so either S3+H1L/R Long or double tapping it will behave like mouse clicks. Hopefully, it's a simple fix the only thing that looks kind of like a culprit from the changelog would be applying the dual functions to WH LOSB? I do have my Hat function in VR flag set to 1, I saw one or two other folks noting the loss of station switching a few pages back, might be additional insight there if nothing just jumps out at you from tracing back the changes. edit: Forgot to put a bracket on the " " tag

Redkite has a decent albeit lengthy walkthrough of the system, the link should have a timestamp: Here is a much shorter and dedicated video: Understood, as an aside for the latest version did something break or revert for VR station switching? Mine stopped working. Ahh, I kinda messed up equating it to the bore ACM mode on the F15. The MSL Mode does have different functionality depending on the weapon, with an overlap in some instances with the ACM mode (http://www.heatblur.se/F-14Manual/weapons.html#launch-modes). In the interest of keeping it simple, PLM is a target acquisition where the MSL mode changes the behavior. For example, the Aim54 launched in BRSIT (boresite) mode will come off the rail active locking onto the first thing it seems on/near the ADL. The BRSIT mode is a bypass for the sidewinder SEAM mode (useful if you need to fire quicky) and supports Sparrow via a flood mode allowing for salvaging trashed shots. Not sure if that warrants placement on the HOTAS itself, but my bad for the shitty original analogy.

I fly in VR so I kinda understand where you are coming from. What I ended up doing was printing out the profile JPGs and the high contrast MFDs and made a little bind I can keep on my lap, sort of like an IRL kneeboard. It's easy enough to kinda glance out of the bottom of my HMD if I need to, or depending on your hardware there might be an easier solution. If you print them in landscape mode you can have a nice little flip book that works just fine. The more you fly with CTS, in general, the less you will need to reference the book. I fly a LOT of different modules and for the most part, the profiles follow a similar theme - especially for similar aircraft. You get used to where certain things are going to be always and Homefries does a great job of keeping commonality where it makes sense.

I do have MFDs but I fly in VR so sometimes it's not the most efficient input method. I don't know how others do it, but for me I've can easily find the MFD but I have to physically check which button I need by referencing one of the corners, I imagine it's a lot like being blind :). Even on the easier buttons to find it's still like a ~2 second+ process. This can be compounded in other cases when the button I need is in between two buttons I definitely DO NOT want to hit by mistake. To be fair, where you have it now is probably one of the easier buttons to find being it's one to the right of "the fat button closest to the left corner" I was just thinking of what would be a good candidate to move to the HOTAS that would do justice to your style. It had more to do with how you map the FC3 boat switches than an inability to get to the button.

I'd say it's a personal preference at that point. I use both but certainly favor the actual mouse to the face aim. Mainly because I have a lot of crap mapped to the mouse and I've gotten used to it. Not to take away from the facemouse, it certainly comes in handy at times :) I'm waiting on them to clean up the actual VR hand controllers as I preferred using them over mouse/facemouse but they currently have it in a strange place with how they handle manipulating the switches so I'll be sticking to the mouse/facemouse until it's fixed.

After spending some time with the F-14 profile, figured homefries could use some more unsolicited feedback :) The biggest things I find myself missing on the HOTAS are; • Course & Heading knob selection • ACM Cover toggle • MSL mode toggle • Autopilot issues that are elaborated more throughout I wanted to offer some thoughts on where and how that functionality could exist while being cognoscente to the current theme and methodology. In the interest of brevity, I opted not to include a little summary on the rationale for the autopilot changes because I’m sure you can follow along the logic. Unfortunately, there is a bit of a domino effect throughout which I’m sure is only a small taste of the problem(s) you solve on a larger scale to make these profiles. Throttle - A/P Disengage button + 3-way vector switch Proposed change: APENG long = AutoThrottle | APPAT = ACL, APALT = Altitude Hold. What I think may be a cleaner solution is outlined under the boat switch section, this is mainly to solve the ACL usage issue outlined below in a vacuum. Why: The GSD state on the APENG switch prevents ACL functionality as you need both the A/P engage *and* AutoThrottle. Since GSD removes the only A/P Engage mapping you can’t really use ACL without clicking in the cockpit which sort of negates the need to have it mapped at all, the VEC/PCD (up state) of that switch isn’t going to be used, from what I can tell, ever within DCS. Moving Altitude hold over to the APPAT 3-way allows you to use automated carrier landing (ACL) functionality much more gracefully. I do realize this may create another problem as I’m suggesting using one physical 3-way switch to operate 2x 2-way switches but the main issue is the usage of the ACL function on the HOTAS. An additional considering for the current mapping is even if you go a bit out of order for the ACL and engage the A/P (which is going to be attitude hold) before dropping your gear you lose the ability to trim and if you need to abort the ACL with GSD your only option is the pinkie lever which kills your SAS. Boat Switch Proposed change: Move current A/P Heading functions to the APPAT/ALT/AH switch as either default or shifted toggles. This would free up the boat switch which opens room for some of your usual boat switch wizardry ???? This would centralize Autopilot functions physically on the throttle Alternative (combined) proposal • Move boat switch mappings to APPAT/AH/ALT 3-way • AutoThrottle mapping already exists on left throttle in a very user friendly (F18) place • ACL is the only homeless mapping which can be a long press APENG Subsequent Boat switch use: Easiest thing that I think is ‘on-brand’ for you would be an 'Enhanced Master Arm’ functionality similar to your FC3 profiles where the boat would serve as a BVR/ACM toggle. For example, forward would be straight up Master Arm and AFT would be Master Arm + ACM cover up. APU / Front Seat LANTIRN With several folks making use of the Pilot LANTIRN mod (https://www.digitalcombatsimulator.com/en/files/3303929/) a way to engage the LANTIRN state from the ‘pilots’ profile would be awesome. At a glance, the level of effort to add that to the GSU APU switch seems like a good fit? This could be a toggle option in the CTS configuration like how you currently have the fuel dump inversion. I'll admit I'd never been able to get the LANTIRN remapping toggle to work for me (VR user) so I’m really looking for a low effort way for you to make that work ???? China hat, Coolie, TMS and Navigation While must admit having the wing sweep on the china hat is much more user friendly than the coolie, I understand why you put it there as it’s closer to the actual F14 throttle. Suggestions: • Map course knob L/R to china hat, optionally leave the shifted AUTO/BOMB functionality as is • Either add a CTS config option or implicitly allow folks to disable the AUTO/BOMB on coolie coolie if they are like me and prone to accidentally selecting AUTO/BOMB when trying to manually sweep wings. • Alternatively, if you wanted to favor pure utility over semi realistic placement, leaving wing sweep as is on the china hat (aft/fwd/auto/bomb), the coolie could be used for both heading and course knob functions. • Map heading knob L/R to a shifted TMS L/R which is currently unused DMS While I could be wrong about the actual utility of the MSL mode switch, I equate it to roughly the grandfather of F18/F15 bore ACM modes. I find myself really wishing I had it mapped to my stick. I feel like using one of the redundant PAL slots on the DMS (L or R) would be a good fit. Summary of the Wishlist • Make ACL fully HOTAS friendly, removing unused functionality and utilizing the AP 3-way for either heading modes or as a ‘dual toggle’ solution • Reclaim the boat switch for a more creative application like your other profiles or a simple ‘enhanced’ ACM mode implementation • Make LANTIRN mapping available to both PILOT/RIO profiles • Decide if wing sweeping will live on the coolie or china hat, add course/heading knobs to whichever loses • Add MSL Mode toggle to DMS to replace one of the redundant PAL buttons

It doesn't actually move your mouse, you sort of 'face aim' with it. the hat left/right is left/right click and the up down mimics the scroll wheel. The point of it is to make it easier to manipulate the switches and knobs without an actual mouse or VR hands. You can tell it works by S3+H1L and see if you get a light blue crosshair. If so, point it over something and hit that same combo again to see if it clicks.

I'm using VR and am pretty sure that the 2.33 nixed position switching for me at least. I updated to the v233 luas for the F14 and it seems to be back to as it was two versions ago. Without in-depth testing, it doesn't seem like the APU functionality (remapping) works either. It seems the H1 goes to the ole VR mouse mode now with S3 pressed. FWIW I also kinda liked the double tap, and noticed that if I double tap H1U it gives a nice zoom in VR. Not sure if this is intentional but it's pretty handy. If a workaround would be going back to the old LUAS I'll do it, I just don't like to mess with them too much since some of my own binds get overwritten each time (these don't conflict with CTS).

*edit: I tried this on a 2nd PC with essentially a fresh DCS/CTS install and no VR and can confirm RIO related issues like Warthog trim position switching and APU/Lantirn functionality persist, or I'm stupid twice :) Also I cleaned up some of the bullets I wanted to inquire about a few issues I'm having with the F-14. Apologies if this has been covered, I tried to read the documentation and this thread for tidbits. Seeing as I'm apparently the only one experiencing this stuff I'm going to assume it's just me and hopefully provide enough information to get pointed in the right direction. Some of these issues are likely just because of a very complex and new CTS profile but thought I'd surface them. If there is a better way to do so like Discord, please let me know. CTS Version: 2.31a Warthog VR User Head Tracking Hardware set = 2 | Default POV Hat Function in VR = 1 | Issues: Station switching via HAT does not appear to work, I can do it via keyboard but actually have to hold S3 to go back to pilot Wheel braking via paddle seems ignore the decoupling option that applies to other profiles (this is minor and I didn't look too far into it tbh) RIO Lantirn mode toggle via APU seemingly does not work, my axis defaults to the little warthog nub, I checked both stick and also toggling wht/blk hot options to verify Loosely informed feedback Unsure if this is intentional, but fuel dump toggle seems to be reversed off/on vs the landing light Swap MFD right top / bottom rows to more resemble the actual console layout For VR (or shifted) would the FOV zoom be better served as a legit DLC wheel or analog flaps? Tailhook up/down seemingly missing, while I know it's a bit 'off brand' for you perhaps a S3 Long on the stick MMC button? Otherwise, personal preference is losing landing lights (redundant to MFD) as a switch and move that to an S3 pinky switch. Worst case map to one of the open MFD slots For open MFD positions, unless you had some ideas already down I'd suggest adding canopy control and a secondary catapult hook-up. In use, I've found it's not overly difficult to inadvertently disconnect from the cat and careen off into the drink trying to salute. Things I've tried to solve my own problem Did a full CTS update Imported, and then reimported very carefully the KB and WH binds into the right areas Toggled the VR and trim related general settings to see if that was it Read the documentation provided Thanks for your help, this aside I'm LOVING the profile - great work as always. The MFD mappings are great!

This statement is akin to telling a toddler that if they don't brush their teeth you will take them to the police station and have them thrown in jail. In your defense, for some reason, I only could see what/who you were responding to by quoting your post helps me understand that this wasn't the most asinine post within the last 10+ pages of all the intermittent and highly entertaining emotion-fueled screeching. :prop:

Just use the Oculus Debug tool, it's super powerful and has all the output you'd ever need. https://developer.oculus.com/documentation/pcsdk/latest/concepts/dg-debug-tool/ You can build your own custom overlays within it, the .exe is in "Program Files\Oculus\Support\oculus-diagnostics" DCS also has that overlay built in still ya? ctrl-shift-break or something like that, I'm sure you could find it with a search.

Hi, I assume this update where we can push buttons/switches was either included on accident or it's very premature, hence lack of announcement. I may be a minority, but I have made little touch holsters that mount underneath my WH throttle on the left and a little hook I mount under the right side where my mousepad is. This happens to be right inside one of the right consoles, but even if I put the touch controllers on the floor I end up hitting buttons on accident. Not too big a deal when it's just the lighting or a total non issue on FC3 but I've definitely hit important things like ejection seat arming, generators etc. I'm SURE you guys are still working on this, but in the interim could you make it to where you have to have the grip "middle finger" button held to engage the free push feature? Might also help solve where you basically need to jab a UFC button like a boxer to not double press :) X plane 11 if you haven't checked it out actually has a pretty well implemented system for buttons. Obviously that style might not work with your engine but certainly good to inspire some engineering if you hadn't tried it.

I was on the fence if this should go under the Huey forum or general, but since it seems like changes to a core system likely caused this its getting posted here -feel free to move. Issue: When spawning in the Huey with the engine running it behaves as if you have full collective regardless of where your HOTAS actually is. Qualification: I experienced this when loading the Huey in my own mission, then in someone elses multiplayer lobby which I wrote off as something we did wrong. When it happened during the NTTR instant action--> free flight I knew it wasn't just a problem with amateur mission editing. Could it be some other settings or otherwise a "me" problem? sure but I haven't changed anything since this last open beta with my setup and it wasn't doing this previously. I don't want to go into much more details because you guys know if you fooled with anything regarding the spawn logic/behavior of the asset and it should otherwise be pretty easy to replicate. If it's just me doing something stupid I'm not aware of I'm sure I'll figure it out.

That looks AWESOME. My only skepticism is that in all the videos I didn't see them use a HOTAS that is attached to a desktop. They got a giant fat guy to demonstrate the weight, they had another dude doing some 360 stuff with a laptop literally in his lap but nothing external. Until I see them, or someone does a review where they show me that you aren't winding your cord(s) to death with a 360-degree chair I'm hesitant. I don't really see how you could avoid that short of a software restriction that limits you to 180 degrees or something forward or just buying like a 70ft+ USB cable so it won't matter.

I have a question about the detent settings as well, this has been ongoing so I don't think it's related to any of the recent stuff. Before I go too far down a rabbit hole I was hoping you could confirm that the import files for the WH have custom user curve values built in? The reason I ask is because for at least the F18, F15 and F5 my afterburner (with physical detent) would juuuuust barely engage at the top. I played with the CTS settings for this for a while one night and couldn't ever get it quite right. Finally, I just unticked user curves and everything worked fine. This could be a few things... I do have the custom 3d printed detent that allows for pushover, it might be a mm or two short causing the 'issue' I once upon a time followed a guide to add my own throttle curves, they might be stuck While unlikely there is an issue on the CTS side or I got a bunk throttle etc As an aside, would it be possible to have a toggle in the software to map either the coolie switch or TMS to serve as slew controls for the TDC? I hesitate to call it VR favored option but maybe it is considering the trades in various profiles. I used to use NOiDS profiles in my jets and that is the biggest thing I miss, not having to use that little makeshift mouse. For the F-18 in particular if you wanted to stay as true to life as possible the coolie would make sense as the current function is redundant to the TMS and you could always map the radar elev as a /I for the TMS up/down. For the FC3 (I just fly the F-15) I think the same thing is basically true where you could use the DMS switch, which TBH works better as a TDC controller but I understand and appreciate how you try to keep it realistic as possible.

Good point, that is worth mentioning that the Harrier is the most 'janky' of the early access experiences I've been a part of. But I owed it to my 10 year-old self that watched True Lies to give it a go. Another good point Harlikwin made is that the startup sequences should almost be in their own bucket. It's either going to be boring/tedious or an integral part of the fun. The harrier in particular for me while one of the 'easier' ones gave me the most headache. The A-10 which is one of the more complex I could do in my sleep, however, I attribute that to failing the startup mission in the excellent Maple Leaf Qualification campaigns 45 times or so. Slight change of subject but are you flying in VR? If so for SURE devote some time to getting VR performance mod unless you have like 1080ti's in SLI or something. If you use the Warthog or Cougar HOTAS I also highly recommend Home Fries's excellent CTS software for centralized and most importantly consistent mapping solutions. It even has on the fly profile switching so you can switch aircraft without a lot of hassle.

Hey man, I was basically you a few months ago so I can actually put myself back in your shoes and hopefully add some anecdote or new information (I wish I would have known) to what already has been said. I think I now own 70-75% of the modules and have really enjoyed the game. YouTube is terrific, almost essential when it comes to DCS. Aside from the reviews there are a few channels that are really digestible for some of the complex things. https://www.youtube.com/channel/UCqH078Ef0HENo01LF3xwIvA has great "1 minute DCS" series where he goes through many aircraft/systems in a very concise manner. Find some channels you like and you will likely be referencing them a good bit. I personally enjoy Growling Sidewinder as well for tactic breakdowns and some others. I'd agree w/ everyone on the F-5 being a good plane but maybe give some perspective from where I think you're coming from. Like the one guy said, buy the plane you are passionate about which is excellent advice, but I had no idea how 'passionate' I'd be about the F-5 until I flew it. The most important reason is that it represents a great foundation of commonality with systems you will find in other blue aircraft like the F-18 and A-10. To me, a lot of the systems and weapon deployment knowledge is cross-functional. If you master the A-10 for example, moving to the F-18 will have a much lower learning curve. So starting from WWII is good, but like folks are saying I'd almost put that in a box. Going from your Mustang to an F-5 isn't going to be like going from an F-5 to the A-10, harrier, F-18 etc. The only thing that is 'harder' than it needs to be with the F-5 is navigation, which is really minor considering the benefits. Try not to look at complexity as a linear thing starting from the era. I too was a bit overwhelmed by the A-10 and learned the F-18 in depth. After learning the Harrier and F-5 I went back to the A-10. Not only was it super easy to get the hang of now that I knew how to work many of the systems and what a lot of the acronyms meant - I found it is actually one of the most intuitive aircraft to operate from a design (IRL) standpoint. It took a certain "base skill level" to even appreciate that though. I say that hoping that the A-10 didn't like scare you back to WWII like it's the minor leagues. If you want to spend time learning things that will transfer well from YouTube or whatnot. Radar is a good general thing to know as the knowledge is fairly universal, learn how TACAN works and maybe some landing patterns/procedure.

Is it? I mean by what metrics are we qualifying this as a "disaster?" . This part reads almost like exactly what you should have mentally said to yourself before posting the message :) Hypothetically, lets say you were not fine with it, what then? There was a demo from the virtual airshow on 12/9, a two hour long live mission with 4xF14s a few weeks ago that showed inside the pilots view, takeoff, landing, refueling, jester AI, A/G and A/A. I'm not positive but I'm pretty sure one of the folks on the livestream was a "member of the community"but it's kinda like check, check and check. You just gotta pay attention to the relevant channels (like HB facebook). There have also been what I'd describe more than we probably deserve and close-to-dangerous anecdotes from the HB team within this forum and on a few podcasts I've seen. Those tidbits are (likely) in this thread and have been dissected and theorycrafted to death. Aside from you slightly misreading what was said, You're assuming that 1) those critical items are fully within HBs control and 2) these "items" existed on October 7th and 3) these will cause a launch **WINDOW** slip. Look at it this way, by them NOT giving a date on October 7th they essentially did tell you that there were still items remaining to be done. In saying "Winter belongs to the cat" or whatever. Not December 21st, not before XMAS not day one of winter etc. When these items are resolved and/or release is imminent that is when you will likely get a date, and after spending a few minutes looking around here - I can't say I blame em. It's hard to feel bad for you as a consumer when by your own acknowledgment above you realize they haven't even hit the start of a season-long release window and are basically writing the post you would be more justifiable in writing the first day of spring. Maybe I'm misunderstanding you here, but how much more disclosure do you feel you are entitled? Personally, I think they were more than clear, even following up (which I'm sure Cobra regrets) to say that their internal target is XMAS but they are promising winter. I don't mean to be overly critical or aggressive towards you Brian as you are probably one of the more milder and even in some parts actually reasonable comments on this thread, you just happened to be the last when I read through it :) As a relative newcomer to the DCS community all I see is shit show after shit show between the chastising of real-life pilots who would dare not be 100% serious while playing DCS or give validation that anyone who owns the DCS F-18 module is qualified to operate the aircraft IRL. Causing another guy to shut down his YouTube channel for fear of undue career impact all the way to developers that are understandably terrified of their own customers. Usually, on the internet, you can write that type of behavior off to social misfits, kids, the "mom's basement" folks etc. The thing is that this isn't the Call of Duty community, you can't be a complete moron stick around to learn some of these airplanes. That tells me that the vast majority of people are reasonably intelligent adults which is the most disheartening thing. I'm getting off track now so I'll shutup - anyway hope to be flying this thing with everyone here soon.