Rex

Yeah, I first thought it had been released based in the changelog. So I went to the planes section of the main site, had it show 'all', searched for 130, and paged through but could not find the plane. The only thing the main DCS homepage was the "Pre-Order" thumbnail so I figured "I guess it's still in pre-order". Talk about confusing. I did manage to buy it, from the Thanksgiving Sale page. I got a 20% discount, which is still good (cost $63.99), but speaking as someone who owns 100% of the maps and around 80% of all of the planes/helos in DCS ... this was the most confusing item I have ever purchased. Awesome release, though.

I may be stupid, in fact, my mom thinks I may very well be the dumbest person currently inhabiting the planet. Despite visiting the DCS homepage several times, I cannot figure out how to pre-order the C-130. There's a little thumbnail that says "C-130J Pre-Order", but clicking it just goes to a preview video. It doesn't actually take me to a page to pre-order the thing. The end of the video just says "Pre-Order Now with 30% Discount". Okay, I'm sold! Now, how do I ... you know, pre-order now with 30% discount? Given my cognitive limitations, can someone explain to me how to make this transaction? If you could explain it like I'm five years old, I would appreciate it. I'll likely still not understand the instructions, but I have people who can help me from there. Thank you! Nevermind, I finally found it, on the Thanksgiving Sale page.

Is anyone else finding extremely long waits to exit a mission, or worse, a sever? When I want to exit a mission back to the Mission Editor, or change servers, there is a super-long wait before the transition happens. It takes a single-player mission from 30-120 seconds to return to the ME, and for Multi-Player servers, it takes upward of 5 minutes to be able to disengage and leave the server. This did not used to be the case. Thinking it was mods, I disabled everything. Well, except for Tacview. But I've been running that for 6 years without issue. Has anyone else encountered this? I have DCS on a fast Samsung 990 Pro SSD, and I have 64GB DDR5 RAM, an i9-14900K CPU, and a Nvidia 4090 GPU ... so it really shouldn't be hardware resource constraints.

Holy crap, I can't believe how much of the walls are still standing. It's such a small area for those shockwaves to have stayed within.

The prison building is more robust than a normal DCS building (which is necessary to recreate the mission more realistically), but the prison building does indeed take damage too.

The south wall has been breached! Run for it!

You can at Amiens Prison! 31 segments at a time!

If you put trigger zones on the Amiens Prison walls, you'll notice that they break down into sub-sections, 31 sections in total (about 40 feet of wall to a section). This is awesome because in Operation Jericho the pilots targeted sections of walls and the way it was designed in DCS, it gives us the ability to recreate the mission with quite compelling precision. Remember, if the building demolishes when you hit the walls, the mission is ruined, so they made the buildings more resilient so we could hit the walls without leveling the entire compound. By the way, I don't know if you noticed, but the individual sections of walls have good damage models ... they don't just fall straight down, a realistic-looking chunk is taken out of the wall instead, with a fire-scorched outline. Sublime! The damage model of Amiens Prison is totally correct for the mission that took place there. The building catches on fire, but doesn't fall to the ground like most buildings in DCS. So yes, it is very hard to demolish the building, but most buildings in DCS come down too easily, so this is exactly what we need to focus our attention on the walls. Huge props to Ugra because they clearly know they history of the mission, and they knew what the needed to do to help us recreate it. The attention to detail on this one small property desperately wanted by probably only a handful of us is just outstanding and truly appreciated! They obvioulsy created Amiens with the needs of mission-makers in mind, and it's a bg reason Normandy 2.0 is my favorite map. Although, come on, there's also, what ... London, Paris, the Eiffel freaking Tower, Arch Du Triumph, Big effing Ben, Windsor Castle, Palace of Westminster ... did you check out the trams running in Paris now? Another unexpected helping of bad assery served up. I've even learned from the map. I had no idea Mont St. Michael even exists until I flew over it, was intrigued, then looked it up. Ugra did an exemplary job with this map, and things like this really increase my enjoyment of DCS. I don't know why they didn't brag about Amiens Prison in the release notes but they definitely should have. It's real quality work!

Every source I can find says that the Kurfurst and Mustang are closely matched in speed, with a slight nod typically going to the Bf-109. Yet, as any DCS MP pilot will attest, the Mustang is WAY faster than the Kurfurst. It is not possible to either out-run, or catch a Mustang. They are anywhere from 20mph - 40mph faster depending on altitude, and their climb rate is absolutely astounding. This does not even come remotely close to correlating with reality. What gives? Bf 109 K-4 – Top Speed (All values are with MW-50) Sea Level: ~374 mph (602 km/h) Optimal altitude (~7.5 km / 24,600 ft): ~452 mph (728 km/h) High altitude (~9 km / 29,500 ft): ~445 mph (716 km/h) P-51D-30 Mustang – Top Speed (All values are with 67” Hg WEP) Sea Level: ~370 mph (595 km/h) Optimal altitude (~25k ft): ~437 mph (703 km/h) High altitude (~30k ft): ~435 mph (700 km/h)

I don't think that this is a bug per-se, more like something new that I've noticed. It now takes an excessive amount of time to quit a mission and go back to the Mission Editor. Like if I'm doing some trial-and-error mission building, each time I try something and then want to go back to the ME, it takes 30 - 120 seconds to do so now, with an average of around 60. It is a moderately-sized mission (about 700 units), but it didn't used to take this long. Expected?

Interesting, I am launching from the launcher, so it's choosing that. Let me see if I can change it. Thanks. Fair enough. I'll wait until I make a vanilla one. Otherwise the mods may pollute it.

I'm getting access violations too just about every day, although mine are in `VCRUNTIME140.dll`. Mine are single-player in a self-developed Normandy mission. Problem is, my mission won't load without some mods being enabled so I can't really officially report it. I may have to make a vanilla version because the access violations are becoming more and more common. 2025-11-16 00:12:47.577 INFO EDCORE (22808): # -------------- 20251116-001248 -------------- 2025-11-16 00:12:47.579 INFO EDCORE (22808): DCS/2.9.21.16552 (x86_64; MT; Windows NT 10.0.22631) 2025-11-16 00:12:47.580 INFO EDCORE (22808): C:\windows\SYSTEM32\VCRUNTIME140.dll 2025-11-16 00:12:47.581 INFO EDCORE (22808): # C0000005 ACCESS_VIOLATION at 00007ff99fbc23e7 00:00000000 2025-11-16 00:12:47.582 INFO EDCORE (22808): SymInit: Symbol-SearchPath: 'E:\DCS\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'Rex' 2025-11-16 00:12:47.584 INFO EDCORE (22808): OS-Version: 10.0.22631 () 0x100-0x1 2025-11-16 00:12:47.585 INFO EDCORE (22808): 0x00000000000123e7 (VCRUNTIME140): memmove + 0x317 2025-11-16 00:12:47.586 INFO EDCORE (22808): 0x00000000000375fd (ModelDesc): model::ShellNode::intersectStat + 0x147D 2025-11-16 00:12:47.587 INFO EDCORE (22808): 0x0000000000038302 (ModelDesc): model::ShellNode::intersectStat + 0x2182 2025-11-16 00:12:47.587 INFO EDCORE (22808): 0x0000000000039982 (ModelDesc): model::ShellSkinNode::proces<profanity>Pos + 0x62 2025-11-16 00:12:47.587 INFO EDCORE (22808): 0x0000000000048469 (NGModel): model::NGModelLodsMT::testWithSegment + 0x5019 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x0000000000048d32 (NGModel): model::NGModelLodsMT::testWithSegment + 0x58E2 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x0000000000046916 (NGModel): model::NGModelLodsMT::testWithSegment + 0x34C6 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x000000000003e4b4 (NGModel): model::NGModelLodsMT::ParseMT2 + 0xBE4 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x000000000003de6e (NGModel): model::NGModelLodsMT::ParseMT2 + 0x59E 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x000000000000d3c4 (GraphicsVista): Graphics::GraphSceneObject::collectRenderables + 0xC14 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x000000000000f95e (Scene): (function-name not available) + 0x0 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x000000000001755a (Scene): Graphics::SceneBase<DCSDemoSceneCollections::ObjectCollections,DCSDemoSceneCollections::LightCollections>::allowSceneWriteAccess + 0x86A 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x0000000000047a04 (edCore): ed::SyncTaskQueue::push_task + 0x13534 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x0000000000049113 (edCore): ed::SyncTaskQueue::push_task + 0x14C43 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x00000000000331e1 (edCore): ed::thread::_get_current_thread_id + 0x71 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x0000000000029333 (ucrtbase): _recalloc + 0xA3 2025-11-16 00:12:47.588 INFO EDCORE (22808): 0x000000000001259d (KERNEL32): BaseThreadInitThunk + 0x1D

I'm a software developer, and to be fair, there isn't a lot to understand. Here is the relevant section of the manual: Huh? So my expression should evaluate to a Boolean? A binary? No wait, my expression sets the CONDITION for the RANDOM group spawn? So it should evaluate to a 0-1 float representing a percentage? A 0-100 integer representing a percentage? The weight in grams of a ham sandwich, rye bread, not white? The link from the manual go to the SSE table of contents, not a specific section. And as you mentioned, Jesus (the Mexican shortstop not the diety) help you if you try and figure it out with trial-and-error since it's a little "broken". Fortunately, your explanation helped a great deal, but I'm not sure Stephen effing Hawking would understand the manual.

Create a mission in January with -2 C temperatures. Absolutely beautiful.

OMG you're right! I didn't see it in the release notes so I assumed it wasn't there, but sure enough. What an awesome surprise! Thanks guys! It looks outstanding. Identical the actual compound. Now we can make Operation Jericho missions! Historical: DCS Normandy 2: