Smashy

Amazing work, @Protek438! That looks great - super clean and functional.

@Flappie - I was having this problem off and on since 2.7 dropped and have submitted a bunch of crash logs via the dialog that pops up. Hopefully someone got them. A few days ago, I was able to temporarily remedy the crash by unchecking the fullscreen box. The crashes returned after I toggled fullscreen back on (stupid, but I was trying to see if I lost any FPS with fullscreen disabled). Since then I've been plagued by the "second mission or shift-R" crash. I tried all the things listed here, cleaning up those temp AppData files, quit-to-desktop, removing options.lua, removing my saved games folder but nothing helped. I also tried updating GPU drivers, multiple reboots, closing all other apps, avoiding alt-tab, changing from 2 monitors to 1, alt-enter. This is not the sort of thing tech support like to hear but I just shotgunned random things and yesterday my crashes disappeared. I just now loaded up a simple Huey mission in Nevada and had no problem with a shift-R restart. I wish I could tell you what fixed it but tbh, I don't remember everything I did yesterday to get it working. I'm running Windows 10 Pro 10.0.19041

I was able to move the AI panel from my secondary monitor to my primary one by editing the following file: <DCS installation path>/Mods/aircraft/Uh-1H/Cockpit/Scripts/AI/ControlPanel/g_panel_page.lua Look for the following line: local shift_X = -0.65 Back the original file up and play with the value. The value of "-4.22" worked for me. I don't play multiplayer so I don't know if this fail IC or not. I'd also like to find a way to move the cargo view panel but that's not super high priority for me so I haven't looked into it yet.

Good question! I'm still trying to find my around DCS and am in the process of learning to fly and operate the Hornet and Huey. In this context, I'm using assists that: compensate for what I feel are inevitable shortcomings with a 2D single-player desktop sim that provides nothing to help proprioception or the vestibular system. So dot labels and perhaps control position indicator. facilitate the learning process (i.e., immortal against SAMs so I can try various tactics and techniques to see what works and what doesn't without having to constantly restart) simply to enjoy the game as I want to. For example, I find the stick and rudder things most fun and have spent a ton of time on AAR and finally am able to do it at a mediocre level. Same with hovering in the Huey. I'm continuing to work on fine-tuning my Huey control and Hornet AAR and am working on the Hornet's Case I recovery procedure and execution. I prefer easy comms because I know I won't miss having to twiddle radio frequency knobs while learning these difficult skills. I do like knob twiddling in certain situations so I do enjoy cold starts and complete shutdowns. As I progress I imagine I will take more of a purist approach and eliminate some, if not most of the crutches I'm using now. Things like F10 map might help me learn to interpret what my Hornet's sensors are telling me but I feel would detract from the total experience in an actual mission. Oh, I've already turned off the BDA window. That thing always reminded me of a score counter in an arcade game

I was reading the various and polarizing "can we get an easy AAR option" discussions and got to wondering what cheats and assists everyone uses. DCS is a game after all and I don't think there's any shame in a player adjusting the options to make it as fun as possible. For context, I've only been playing DCS for roughly 6 months and only play single-player. I mostly fly the Hornet but lately the Huey has been taking up nearly all of my time. Here are the cheats/assists that I'm using: Dot labels (with mod). This one is invaluable to me since spotting is next to impossible without labels. At the same time, I think full labels are too intrusive so the modded dots are a good compromise. Easy communications. Pretty important but not essential. I just don't find managing the minutiae of all the radio gear that interesting. I'm especially curious to hear other's thoughts on this option. F10 View Options - All. Just because it's the default. Player aircraft immortality. Very rarely, and only when practicing specific things like SAM evasion/defend tactics. Plane-to-Plane view (F5). I'm embarrassed to say I use this every now and then in a gunzo fight but really, really, REALLY try to avoid using it. BDA window. It's cool to see instant results for released weapons. Sometimes I disable this but often forget to do so. Controls position indicator. On rarely for Hornet, nearly always on for Huey. Huey autopilot - enabled. It's an immersion-breaking assist but I justify using it by thinking it's the copilot taking the helo so I can dial in ADF/VOR/ILS freqs or fiddle with other knobs and switches. Huey rudder trim - enabled. Just to make things easier on my feet. There are likely more "cheats" I'm using but really do try to stay away from using too many crutches. For me, a lot of the fun in a game like DCS is meeting the challenges presented and working to overcome them.

Thanks for sharing a link to this. Great interview! My favorite quotes from PilotMi8: "The good thing about simulators is that you can experiment limits of aircraft which pilots can’t, due to constraints of equipment, regulations and the desire to live." Q: What will the team work on after the Mi-24 releases? A: After the Mi-24 is out, we’ll work on the Mi-24. The amount of bugs 1000 users find instead of 10 is obviously going to be higher, so we’ll be working on that for the foreseeable future. Q: How does the Apache compare to the Mi-24? A: Why do you people care so much about the Apache? It’s too early to get a feel for it anyway, whenever there is one we’ll talk. (Friendly rivalry at ED. Love it!)

I've been using your Hornet kneeboard pages for awhile now and have found them beautifully formatted and crammed with useful information. Thanks for putting these together. I really like how information is organized on the various pages. I have ne question regarding the PDF format after doing a quick search for info. Does the PDF format require something like "Kneeboard Builder" to use in-game? Or can they be used as-is? Thanks again for creating these!

Thanks for the update, Badger! For those interested, here it is.

At the end of the day and whatever you call it, DCS is a game. It's entertainment software and I'm all for having options that maximize the fun for the widest possible audience. It's a timely topic for me because I just started focusing on in-flight refueling and if you asked me 3 weeks ago if I'd ever be able to do it, I would've said it's impossible. But I'm pretty stubborn and am the type that finds such challenges "fun" so after a couple of weeks of focused practice, I'm finally able to perform air-to-air refueling. I'm not good at it yet, but I can top off a 60% internal fuel load with 2-3 attempts (on my best days). Would I use an easy-AAR option? Probably not, but that's just me. However, I can totally understand how such an option would be great for someone else who isn't as fortunate as I am when it comes to free time or is simply not interested in learning this one thing in a game that has a thousand other things that might offer more entertainment.

I'm not so lucky. After 2 weeks or so of trying, I'm only now starting to get the hang of it. I do seem to be making progress - quicker plug-ins and staying on the hose longer. I still have a way to go to consider myself "good" at it.

Speaking of crowning achievements... This was a pretty big deal for me

All of a sudden, I recently started getting similar crashes/hangs. While I did notice similar types of error messages in the crash logs the crashes weren't as consistent in terms of time before failure. While investigating, I eventually found a large number of "The IO Operation At Logical Block Address for Disk was Retried" in the system event logs. Up until I found that, I did a bunch of troubleshooting that involved video card driver updates, memory tests, disk tests, reseating DIMMs, moving my game install to another drive, swapping SATA/power cables. The last 2 actions had positive results so I focused on that. I decided I had a bad drive, bad cables or bad onboard SATA controller. After reseating all cables, I couldn't reproduce the crash. Oh well, it looks like it's fixed for now. I'm just posting this in case anyone has similar crashes - check the event log and go from there. Also my crash logs also contained errors like this: # -------------- 20210304-173533 -------------- DCS/2.5.6.61527 (x86_64; Windows NT 10.0.19041) G:\DCS World.beta\bin\edCore.dll # C0000006 IN_PAGE_ERROR at C467BB5A 00:00000000 SymInit: Symbol-SearchPath: '.;G:\DCS World.beta;G:\DCS World.beta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Smashy' OS-Version: 10.0.19041 () 0x100-0x1 tl;dr - I suspect my crashes/hangs were caused by bad SATA and/or drive power connections. Reseating all cables to the SSD where DCS was installed seemed to fix things for me.

The effort->reward cycle with DCS makes it such a great experience and keeps me going. The Hornet module is especially brilliant in this regard, I think. Yeah, Usenet was the Wild West. Unmoderated flame wars, LOL!

Great "how it started, how it's going" screenshots, @wilbur81! I played Hornet 3.0 and Hornet Korea for countless hours in the past and it's one of my favorite all-time games. I also had Jane's F/A-18 but am embarrassed to say that I was too intimidated by the level of detail presented to get very far with that one. Call it being younger, impatient and lazy. . That's all changed and I'm really enjoying the complexity and challenges of the DCS Hornet module. Of course, now there's so many readily available resources to help overcome the steep learning curve. Before, it seemed the majority of my information came from documentation that shipped with the games and chatting about sims with others on comp.sys.ibm.pc.games.flight-sim. It's unbelievable how far PC sims have come and I feel fortunate that such a high quality product exists in such a specialized and small market. To the entire ED/DCS team, thank you for the great work. You keep shipping these incredible modules, I'll keep buying them. The passion and excitement of the development team and the community in general is infectious.

I just finished listening to the F-14 episode and really enjoyed all three parts. I especially enjoyed getting a glimpse into how the sausage is made with the Heatblur interview. Hearing the team members speak really hammers home the extreme complexity of the F-14 module and how it is such a labor of love for these guys. I mean, they're not doing it for the money and certainly not for the armchair pilot critiques from these forums :). One especially interesting thing I learned about the team was the varied backgrounds of each member. PhD in artificial intelligence, EEs, and theater/stage director in the case of Alex (IronMike?). Their enthusiasm and dedication to creating the best product possible is clearly evident. I heard the same kind of pride and excitement in Matt Wagner's voice in his appearance on the Fighter Pilot Podcast. I remember seeing the same kind of developer and community excitement with Flanker 1.x/2.x, Falcon 4.0, Jane's, et al. Unfortunately all the excitement in the world couldn't save the hardcore combat flight sim from going virtually extinct. Let's hope that doesn't happen again.

The reformatted tables look great! Thanks for doing this. I've used this post as a reference during the free-to-play events to install/uninstall modules en masse from the command line. It's so much quicker and easier than the in-game module manager.

Odd. Fighterstick/Pro Throttle/Pro Pedals user here and I had no problem assigning the throttle mini stick to TDC slew control. It works as expected. The weird thing is how it works for you with one module but not another. A couple of ideas that might help isolate the problem: use CH Manager to test the throttle X/Y axes to make sure they're working as expected. I'm guessing this is the case since it works with the A-10, but doesn't hurt to check. temporarily move the diff.lua files out of the way to make sure there's nothing in there causing issues. My Hornet control config files can be found here: C:\Users\<username>\Saved Games\DCS\Config\Input\FA-18C_hornet\joystick. Yours should be in a similar location. Don't delete them, just move them someplace safe. Good luck and I hope you get things sorted.

New DCS player here and I have the PG, Syrian and NTTR maps. I've spent most of my time with the NTTR map, setting up test/training missions in the ME. Count me in as someone highly interested in an NTTR paid update.

I'm always looking out for new content to listen to. Thanks for the heads-up on this podcast.

I saw this thread was updated and thought you were planning on giving the Huey a go during the free-to-play period. Instead you just went for it. I don't think you'll regret it. I suck terribly at it and have spent most of my time with the Hornet but something about the Huey is so cool. Maybe it's the fact that the systems are simple but the operation of it is pretty complex and requires more artistry than anything.

I tried to reproduce the crash today 3 separate times with 2.5.6.60966 and everything worked fine. I'm fairly sure I did not do anything differently today but I can't say that with 100% certainty. The only thing different is the uninstallation of that Steelseries package but I did see crashes last night after uninstallation. I'm puzzled but not going to complain since everything is working for now. @Flappie - thanks for the feedback. I use the default Windows 10 security program. Since everything is working, I'll leave things alone with that until the next time I see problems. If the crashes/hangs reoccur, I'll post updates here.

After a bit more testing: First I uninstalled the SteelSeries management software that updated itself earlier today. No luck. I then did some testing with the release version, 2.5.6.60966, and 2.5.6.60720. With both open beta versions, I was able to reproduce the crash only with a specific mission. All other tests were crash free. The problematic mission was a test mission that I was using to practice cold starts and VFR landings. Over time, I've added/removed objects from it to play with various things but right now it's just my Hornet sitting cold on the ramp. If I have time tomorrow, I'll see if the same mission file will cause the release version to hang.

I've tried a few more times and even tried rolling back to 2.5.6.60720. No luck, so I don't think it's version 2.5.6.60966. It's got to be something on my end. The crash logs mention different .dll files. I'm continuing to dig into this but any suggestions would be appreciated. crash.zip

I just updated and had 3 hangs that required using Task Manager to kill DCS. Cold start from McCarren in Hornet. The only mods are modification to pluginsEnabled.lua to remove module icons on homescreen and CMDS_ALE47.lua to save custom expendables programs. I've tried a repair but no luck.dcs.log The last hang showed something interesting in the log.

To be honest, this sounds way more fun and exciting than your previous experience!