Diesel_Thunder

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.

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!

Just recently learned that is possible to assign OFF states of toggle switches as key bindings now! Not sure when this happened, but it makes setting toggle switches way easier. Made a short video highlighting on how to do this, and seems to work in every module I've tried so far.

I suppose I need to clarify things. I got this error on the night I posted this when I was on the server list screen, not when joining a server. The little shield at the top of the screen had turned red, and when I clicked on it, got the error message. The following night, with nothing changed, the shield was green and no problems whatsoever.

What's odd is that I flew today, did not change anything, and it passes IC. Also of note is that I edit the Hornets lua file for this too, and that one never flagged at all.

As the title says, it seems adjusting the countermeasure programs via the LUA file breaks IC now. (Open Beta 2.8.84704) This hasn't happened in the past so am curious if this is intended or a bug. For reference, I am only adjusting the chaff/flare programs in the CMDS_ALE47.lua file, (D:\DCS World OpenBeta\Mods\aircraft\F-16C\Cockpit\Scripts\EWS\CMDS\device\CMDS_ALE47.lua) to the quantities and intervals listed by @Raptor9 in his post here: I adjust the LUA file instead of changing the programs in the jet, as that only needs to be done once per update instead of each time one hops in the jet.

Glad you enjoyed it! To answer specifically, the generator doesn’t produce much, if any, power at low RPM. So that’s part of the cockpit flow for me either during the runup to make sure it works, or when lining up on the runway. Opening the radiators ensures that they aren’t forgotten later, like during takeoff. Plus if you open them before starting the engine, you can hear the door drive motors and know that the doors move and that they are wide open. Closing them does not help as much for warmup. One exception I have is in winter missions, I’ll close the oil door to help keep the oil warm, but open it up again when taking the runway. Way to easy to forget that they are shut leads to a very fast overheat shortly after takeoff. Really wish the Mustang featured the door position indicators like the Jug has. They still need to work on the AI for the warbirds, very hard to keep with them in most situations. For climbing, @kablamoman has a great technique posted above. I run my climbs at max continuous as well. Descents I run the engine as needed, usually leave the prop at whatever I was running for cruise, throttle as needed. If I need to slow down, I’ll speed the engine up to 2,700 RPM. Sounds counterintuitive, but that extra RPM adds drag and slows you down. Situation dependent on combat power. If I’m about to be engaged, I increase power to max continuous. If I need more, I can run both handles forward for 3,000 and 61 inches, and can run that for 15 minutes (watch your temperatures). And from there I’ll engage war emergency if needed.

I ran into the same problem with my seat since I use an 8 inch (200 mm) extension on my TM Warthog. Wanting to take advantage of the seat notch, I took my center pole and mounting plate to a local machine shop. They cut the pole square about 1/4” above the bottom mount where it would bolt to the crossmember. I also had them cut the bracket off of the mounting plate and then had the plate welded to the cut pole. The end result works very well and puts the stick at the right height for me. And even with the stick mounted lower, the seat does not interfere with the range of movement at all!

I'm impressed so far in the sightseeing flight I did yesterday in Israel. Great performance (90-130 FPS in MT) and good RAM utilization at around 27 GB. For comparison, Syria pushes my RAM utilization into the low 40's. I'm glad to see that Israel will get developed further. I have limited knowledge of the region but when I saw Jerusalem on the map and flew over, I looked for the Dome of the Rock which is a very prominent landmark, and didn't see it. Hopefully gets added later as well

You have to have logged in once and then set it to offline mode. With an update, you also have to log in the first time too.

You wouldn't see Saipan from that direction at all. The angle of that screenshot in question is from west, looking to the east. Saipan is over 120 miles to the north-northeast. Guam's closest island neighbor is Rota, which is only about 40-ish miles away to the northeast, which also would not be visible looking the direction that the screenshot is taken. That cove to the left of the foreground Corsair is Haputo Beach. That set of cliffs near the fleet is Puntan Dos Amantes (Two Lovers Point). That smaller point of land to the south (right hand side of the screenshot) is where the Hotel Nikko is located, and also marks the northern end of Tumon Bay.