Diesel_Thunder

For those curious on the Morse code heard in that video, it says “coming soon” Characters as I heard them (backslash as character separator) - . - . / - - - / - - / . . / - . / - - . / <pause> / . . . / - - - / - - - / - .

I know the D models evolved somewhat, so not sure if she came from the McD factory that way or was upgraded at some point. She is a block 28 and still fitted with the DVST radar scope.

I'm kinda partial to the F-4D

Here’s a video I put together covering nearly all aspects of the 109. Cold starts, taxi, takeoff, engine management, weapons, landing, and more. Hope you guys find it helpful! https://youtu.be/_uwnsK3E1dU

The canopy is an easy way to tell the Zero apart from the Fw-190. The Zero has a more rounded canopy with the "window frames". Definitely an A6M Zero in the video!

Not sure about putting them on the inners, but one of my favorite loadouts has ATGM's, rockets, and a pair of heaters. If I need more ground pound weapons, I sub more ATGMs in place of the R-60's.

A Warthog without the extension would work, but leaves the seat notch without it's intended purpose. In my opinion, this is the seat's biggest flaw that it cannot accommodate extended sticks without modification. Their latest flight seat does, that being the Flight Simulator Pro, though it is more expensive than the Boeing Military Edition. Anyway, here are the pictures you requested. I did slide the seat back for a better shot. Also added another picture from before I modified the mount showing the extended Warthog. That put the grip about chest level, and would not work at all for me. Was very much worth having the mount shortened. The grip is about at the perfect height, and my forearm for the most part rests comfortably on my thigh as I'm flying. The extension I use is 200mm and still has full range of motion. The only issue with the shorter mount is that the bolts holding the mount to the rail, which also anchor the center pole support bracket, have to be inserted from the bottom instead of the top as called for in the manual.

That's pretty much where I've had the crashes as well. Pretense Caucasus and Pretense Syria. Also had this happen in Foothold Caucasus too.

Awesome! Wonder what it could be? One of my favorite sayings when it comes to troubleshooting, we're not only trying to find what it is, but also what it isn't.

@Flappie Here you go. I've attached both my normal settings and the ones that I set for the test that I did earlier. normal options.lua test options.lua

Other than the cannon rounds, I didn't have anything loaded on the pylons for that test. My typical combat load would be the cannon, 2x Ataka tandem HEAT on the outer pylons, R-60 Aphid missiles on the center pylons, and the S-8 rocket pods on the inner pylons. If it's a heavy ground assault, then I'll replace the Aphids with another rack of Ataka ATGMs.

@Flappie Was able to reproduce this issue on the first attempt after having DCS create the new DCS.openbeta folder. I loaded into a server, started up the Hind, took off for a short flight and intentionally had a "bad landing". Immediately upon respawn into the same slot, DCS froze and then crashed to desktop. Even with the short flight, the track file is 17 MB, too large to upload here. Here is the log file, plus the crash dump. Hope this helps narrow it down. dcs.log dcs.log-20231118-215413.zip

I experienced this last night, while on our squadron server which was running a mission on the Syria map. No problems spawning into the first Hind. After landing at one location, I went to spawn at another location. I slotted into a Harrier first which spawned normally. I re-slotted into the second Hind which froze DCS immediately and then crashed to desktop. I was in multiplayer, so that track file is way to large to upload. Do have the crash log attached though. dcs.log-20231117-035941.zip

I noticed the same thing last night as well. The backrest, collective, stick, and seat frame are hidden, but the cushion remains.

@Flappie I think there may be something up with the Hind. Since we've solved that issue with my system a few weeks ago I've had no crashes, except when flying the Hind. Only had this happen in multiplayer. Can't narrow it down to a specific event, but I've had this happen after getting shot down and re-spawning a 2nd time in the same player slot. Also had this happen when changing to a different slot (going from one Hind slot, to another Hind slot). Similar how it happens each time, your view changes to the Hind which starts to render. You also hear the sound of the cockpit door opening. Within a second to two the sim freezes and the DXDiag box pops up after a moment. Since this was MP, the track file is way to big to upload. I do have two of the crash dump files which I've uploaded. EDIT: Had this happen on different maps, with different missions running so I can’t correlate this issue with a specific server/map/mission dcs.log-20231112-032858.zip dcs.log-20231115-045811.zip

You’re flying the ball properly, which is the problem. In real life the IFLOLS was set according to the aircraft flying the approach, because the hook to eye distance is different. DCS currently doesn’t account for this, and the IFLOLS is set for the Hornet and never changes. For the Tomcat, fly the ball higher than you normally would (about three balls higher I believe) and you’ll start catching the other wires.

I'm using a Thrustmaster Warthog which has an 8" extension, paired with a Virpil collective and a set of Saitek pedals.. The collective also has the large cam installed, allowing for a longer throw. The range of movement is really nice and adds a lot of precision to the controls. Before I bought the collective, I would use the right throttle of my Warthog as the collective, but with the axis set backwards so pulling back the throttle worked in a similar fashion to a collective. Whatever setup you choose, I would recommend one that you can expand with, and add an extension to later if you want. Joystick extensions are wonderful to use, warbirds and helicopters in DCS benefit the most in my opinion when flown with an extended joystick.

@Flappie Think we solved this one! So nothing was wrong with the memory, but one of your counterparts over on the ED Discord noticed my BIOS version was old, and has never been updated since I bought it. AMD's AM5 socket was still pretty new when I put this system together. Several BIOS revisions address memory compatibility and stability, especially when running EXPO. So with some trepidation, I updated the BIOS. I did the chipset drivers as well for good measure. Flying both on Wednesday and Thursday in MP, with re-slotting and respawning several times in each session, I didn't crash once! Funny how some things can reveal a system instability. Thanks for the help!

@Flappie RAM? That’s odd since I’m not getting any issues in my other RAM intensive program (video rendering with Davinci Resolve). Flying last in the night on the server I was getting consistent crashes. Each time it was on the second spawn. DXDiag popped ip each time, and crash reports were submitted.

It varies. I was on our squadron server last night for most of the crashes, which is running the latest version of Foothold. I was in the Mi-24. Seems to be sporadic. Sometimes it'll happen when I first hop in and the textures are loading. Other times it's after I've been shot down and go to respawn. The only common thing is it's when spawning in. I've also had this happen in single player, in a mission I made with multiple slots (for a Spitfire video I had made). I found more zip files from last night, and the evening that I did the Spitfire flight. Both are attached and have track files. dcs.log-20231026-012518.zip dcs.log-20231031-023939.zip

@Flappie Here you go dcs.log-20231031-035354.zip

Good evening. I've experienced crashing with MT with both variants of 2.9, usually when selecting a role (MP and SP). PC listed in signature. No overclocking, DCS on dedicated NVME drive. Attached is the DCS log from the last crash. Noted these lines in it: 2023-10-31 03:53:54.793 INFO EDCORE (23764): try to write dump information 2023-10-31 03:53:54.807 INFO EDCORE (23764): # -------------- 20231031-035354 -------------- 2023-10-31 03:53:54.809 INFO EDCORE (23764): DCS/2.9.0.47168 (x86_64; MT; Windows NT 10.0.19045) 2023-10-31 03:53:54.811 INFO EDCORE (23764): D:\DCS World OpenBeta\bin-mt\enlight.dll 2023-10-31 03:53:54.813 INFO EDCORE (23764): # C0000005 ACCESS_VIOLATION at 00007ffca4b96a74 00:00000000 dcs.log

I noticed this as well last night when our squadron was flying a Foothold mission. Was doing alright with Petro but had difficultly with one tank (a T-72). This tank was near a tree, probably about 20 feet from the tree. I had no problem spotting the tank visually for me. Petro never spotted it at all, from far away or in close.

I took a bunch of measurements the old fashioned way and posted a thread about it. It’s from a D model, but I believe the cockpit dimensions are the same as an E. Hope this helps!