Sérvalpilot

Hey! Source code has been updated. I have some problems with the MiG-31 mod. It handles in a very weird way compared to the other mods I've tried; but the biggest problem is that landing gear doesn't work. Trying to land always results in an explosion, even with invincibility on. I can't figure out how to fix that. Luckily for everyone, Eagle Dynamics seems to be reworking the AI flight model! Hopefully this "general flight model" is good enough to not need my mod any more. For those of you with installation problems, here's a part of the readme: Step 1: Go to the directory for the mod you want to integrate this FM with in your /saved games/DCS/mods/aircraft folder. Step 2: Paste the contents of the .RAR archive in there. Step 3: Open the "entry.lua" in the mod's folder and add the following line of code below the "info" line: binaries = { 'CustomFM', }, Step 4: Further in the file where there's lines written "dofile...", add these lines of code: local cfg_path = current_mod_path .."/FM/config.lua" dofile(cfg_path) FM[1] = self_ID FM[2] = 'CustomFM' FM.config_path = cfg_path FM.old = 4 Step 5: Go to the line, usually near the end that reads "make_flyable..." and add "FM" instead of {nil, old = 4} to the line like shown below Before: make_flyable('[modded aircraft name]',current_mod_path..'[usually /cocpit/scripts]', {nil, old = 4}, current_mod_path..'/comm.lua') After: make_flyable('[modded aircraft name]',current_mod_path..'[usually /cocpit/scripts]', FM, current_mod_path..'/comm.lua') Step 6: Save the .lua file, boot up DCS, and enjoy a smooth flight! If that doesn't work, let me know.

@impalor Thanks for the help! I found the problem, it is indeed thermal trottling. When my CPU gets above 100 I get the framerate drops. I wonder why it's happening just with DCS though.

@impalor I don't think I had this problem before 2.7 so I don't think it's a hardware issue. I took your advice and checked the resource monitor for any changes during these spikes. Memory hard faults don't seem to change when they happen. However, I found this: What does the blue line represent?

I have DCS on a solid-state drive. I don't think specs are the problem unless it's a driver problem, but here you go: CPU - AMD Ryzen 7 3750H GPU - NVIDIA GeForce GTX 1660 Ti 16 GB RAM 500 GB SDD (where I have DCS installed) 1 TB HDD Here's my settings:

Sure, maybe in a couple days as I'm still cleaning it up internally.

I've been having this issue for a while and I finally decided to report it after reinstalling DCS didn't work. In desktop mode, I get a fairly consistent 60 frames per second with similar CPU and GPU usage on busier missions. Sometimes my framerate drops to between 5 and 8 for a few seconds and my processors' usage drops as well (see the image below). It goes back to normal after a few seconds. I tried to pin down what causes this painful slowdown, but no luck. Verifying file integrity, disabling all mods, and reinstalling DCS doesn't work. Log files don't seem to show anything unusual either. Edit: Turns out DCS makes my CPU heat up to the point where thermal throttling kicks in.

@2IAE-CrashBG Thanks for your feedback! That has been added to my to-do list. @sublimeswell I've tested the mod with the MiG-31, although it handles quite differently from other aircraft. I think the problem here is that it's dependent on locked files that can't be easily edited. Fortunately, I have some ideas on how to make it work, including making a version of this flight model specifically for the MiG-31. For now, here's some files that made it work with my flight model, just drag and drop into the MiG-31 mod's installation directory. MiG-31.zip Thanks for the feedback!

I'm trying to edit the .sdef files for the sonic boom (from supersonic aircraft) and light sonic boom (from weapons) but I can't get it to work. To be clear, I can edit the sound file, but the .sdef file doesn't work. I'm trying to edit the gain, minimum/maximum distance, and make it select from a random list of similar sounds I made when it's played in DCS.

I wanted to check out the old version of DCS world but I can't find it in the ED downloads page or the Steam betas menu. They used to be there but now the oldest version I can get is 2.5.6 through Steam. Is there still a way to get any older versions?

I discovered that fire isn't a light source; this is especially noticeable at night when it doesn't illuminate objects or terrain. The smoke screen dispensed by vehicles is self-illuminating.

The radar never warms up during startup. The flashing "P" light never goes solid. Is there a new step I need to do for startup or is it a new bug? This seems to have appeared in the latest stable update.

@Flappie You're absolutely right. Having a full moon makes the NVGs work. Mirage-2000C, full moon: Ka-50, half moon:

I know it has been reported earlier, but it's impossible to see the ground at night when using green NVGs. Here's what Kutaisi looks like from the ground (full brightness): Here's what it looks like from the air (Mirage-2000C, full brightness): Here's the weird thing: The NVGs on the Ka-50 work just fine! (not the same location)

Interesting... So what's the model or variant of the MiG-31 we see in DCS?

Nice! That tail hook looks a lot more realistic!

I checked the model viewer and, sure enough, they show up as connectors. That would be an interesting design choice...

On either wing of the MiG-31 there's a pylon that can't have anything mounted on it. These pylons don't show up in the editor/mission planner. Before the .lua files were locked, modders were able to make these pylons usable, but guess what? Now we can't do that!

Hi everyone! Version 7 is out, and with it, much better stall recovery and post-stall behaviour! As always, feedback and feature requests are appreciated. Have fun!

@Seyv You did a great job on the AASM! I'm also glad someone agrees that the pilot's head looks like an egg. The Rafale C and B do have tail hooks, but they are a lot smaller and less visible than the one on the M variant. They look a bit like the one on the F-16. Here's a photo of a Rafale C taking off. Do you see the hook? And here's a photo of the Rafale M taking off. In this mod, the B and C variants have the base of the tail hook from the M variant.

Yeah; we all want this mod to be the best it can be, myself included, and I was just sharing my thoughts on how to make it better.

Hi, I'd just like to share my thoughts on this new version. The B and C variants still have the base of a tail hook. The new pilot helmet is a bit better, but still looks like an oval. The AASM "HAMMER" model looks much better, but the 3D model has over 442,000 triangles, which is A LOT. For comparison, the Mk-82 has around 6,000 triangles, the Mirage-2000 has 196,000, the F-15C has around 153,000, and the Su-27 has 146,000. This could be a big performance hit due to unnecessary detail.

I did a little experiment. I changed the smoke/fire texture to a bunch of arrows pointing up. This is what burning vehicles look like with that modified texture: Here are the same vehicles but seen upside-down: Notice the way the arrows still mostly point to the top of the screen? These screenshots were taken in "flat" mode, but they behave exactly the same in VR.

The fire effects from vehicles and aircraft debris introduced in 2.7 look nice.... But they tilt to align with the player's head, same for the smoke trail from missiles and contrails. This is especially noticeable in VR. Also, in VR, the effects frequently flash but only in the left eye. I'll need to add a video at some point to demonstrate this.

I made a mod to fix this. Check it out! https://www.digitalcombatsimulator.com/en/files/3317524/

Same here.