Hardcard

Check your drive. In my case it was the freaking SSD partition that gave me grief. Problems didn't get sorted until I performed a wipe and created a new NTFS partition, as I mentioned. AMD drivers also seem to conflict with DCS, btw. Don't include DCS.exe to AMD gaming profiles, otherwise it'll give a d3d11.dll access violation (at least that's what happens when I do it).

:doh: My bad, I didn't realize it's a Strait of Hormuz mission (I don't own the map), that's probably why I don't see it :megalol: Looks like I can't be of any help then, good luck fixing the issue.

I'm using DCS 2.5.2 open beta... The Hercules Down mission just fails to appear when I look for it in the "Missions" folder (where I put it). I can see and open the rest of my missions, though (which are located in the very same folder)... Looks like Hercules Down isn't compatible with 2.5.2 open beta, can you confirm this?

Sedlo, is the Hercules Down mission compatible with DCS 2.5? I've downloaded it from here and my DCS 2.5.2 doesn't even see it.

I was getting lots of access violations too, which caused DCS to either crash or fail to launch, especially the edterrain4.dll one (although I remember getting the D3D11.dll error too at some point). Fully reinstalled DCS several times, but files were constantly getting corrupted during installation. Turns out that the last Windows 10 update had apparently messed up my windows installation, I had to repair it by running the following commands in cmd (admin): DISM.exe /Online /Cleanup-image /Restorehealth ...and then run: sfc /scannow Also, the NTFS partition in my gaming SSD (which contained DCS) was apparently causing trouble, which didn't disappear by simply formatting it. I had to perform a wipe (secure erase) of my SSD, reflash firmware and create a brand new NTFS partition (this new partition didn't use all the available SSD space, I left 3GB out of it). I then installed DCS World 2.5.2 open beta again and I've had no more trouble since. Btw, I also removed all antispyware software from my system (don't trust exclusion lists, tbh) and made sure that I had full permissions for DCS folders. Also, I made sure that I had ALL the VC++ Redist packages installed (from 2005 to 2017, both 32 and 64 bit versions.) I hope this helps

I recently had a lot of trouble with DCS 2.5.2 crashing in ME and also during missions. Here's what I did to solve the problem once and for all: 1- I repaired my Windows 10 installation by running the following commands in cmd (admin) DISM.exe /Online /Cleanup-image /Restorehealth ...and: sfc /scannow 2- I removed all antivirus/antispyware software from my system and made sure that my windows user account had full permissions on DCS folders. 3- I had to wipe (secure erase) my OCZ Vector SSD (where DCS was installed). I also performed a firmware reflash of my SSD, just in case. Turns out that the NTFS partition that it contained was causing trouble, so every time I downloaded and installed DCS files, they were getting corrupted, which led to DCS not working properly. This problem wasn't solved by formatting the existing NTFS partition, the SSD had to be wiped clean. So after the wipe and firmware reflash, I created a brand new NTFS partition in my SSD (3GB short of total capacity this time). Then I performed a clean install of DCS 2.5.2 open beta in that SSD, I've had no more problems since. Summarizing: 1- Uninstall any antivirus/antispyware software (exclusion lists might not be enough) 2- Make sure that your OS has no errors, file corruption, etc. If it does, repair it 3- Perform a clean reinstall of DCS 4- If problems persist, wipe the drive you are installing DCS on (reflash the drive's firmware if you feel like it) and create brand new partitions (with a bit of space to spare) 5- Perform another clean reinstall of DCS, it should work. If it still doesn't work, provide PC specs (CPU, Motherboard, RAM, HDD and SSD if you have one)

Testing done. beaconsilent.ogg is just 1 minute of silence, you should be able to create audio files like this one on your own without problems, no need to download it. I've been able to open and play beacon.ogg without issues too, both in CoolEdit and DCS 2.5.2 open beta, which means that the problem must be somewhere in your system. When you get back home, post your mission file here so we can take a look. Btw, I recently had to repair my Windows 10 installation, wipe my SSD, reflash its firmware, create a brand new NTFS partition and reinstall DCS in it... just to get rid of some nasty DCS file corruption issues which caused a lot of trouble. I'm not saying you'll have to do the same, but... ;)

I'm also using 2.5.2 open beta and I'm able to add and play my own ogg sound files without issues. The log that you posted does seem to indicate that DCS can't read those ogg files that are giving you trouble. I'm thinking that perhaps you have some kind of format compatibility issues going on. Which program are you using to create those ogg files? Are you sure that those ogg files aren't corrupted or just using a kind of ogg format that DCS doesn't admit? I still use my beloved CoolEdit Pro 2.1 for audio recording/editing (with several extra plugins, including an ogg one). All the ogg files that I created using this program work fine in DCS. Why don't you put those nasty ogg files in a compressed zip and then post it here? We can take a look and test them, see if we can reproduce the issue.

Seems like I've finally solved all my file corruption/access violation problems. DCS 2.5.2 openbeta is now running fine on my SSD. There were several problems, which I'll list just for reference (in case other players ever find themselves in a similar predicament): 1- The last Windows 10 update had apparently messed up my old windows installation. I followed the steps described here to repair my Windows 10 installation. Basically, it's just a matter of running the following commands in cmd (admin): DISM.exe /Online /Cleanup-image /Restorehealth ...and once that finishes, run: sfc /scannow 2- My OCZ Vector SSD apparently needed a complete wipe (secure erase)...I also performed a firmware reflash, just in case. The NTFS partition that it contained was clearly causing problems, which didn't disappear by simply formatting the drive. I created a new NTFS partition (3GB short of total capacity this time), which is working well for now... (fingers crossed). I can finally continue working on my SP mission, after 3 days of... :badmood: :crash: Btw, sorry ED, it seems like my system was the culprit this time! :doh:

Yes, I removed the DCS folder under "Saved Games" with each installation attempt. When I said "clean reinstall", I meant it. Other than the DCS key registry, there was no trace of DCS in my system as far as I could tell. As I said, corrupted files were being installed and DCS_updater.exe cleanup-repair didn't solve the problem. You should be able to replicate it by using the corrupted file I provided. You'll see how DCS_updater.exe cleanup and repair functions fail to identify the corrupt code and replace the file. Now I'm stuck with another problem, though... I'm getting constant Access violation crashes when ME tries to load edterrain4.dll Something seems to be seriously messed up, since the problem persists when I move DCS to a separate drive (and even when I run it from another Windows account). EDIT: I've been able to access Nevada map without problems, which means that the problem is probably unique to the new Caucasus map.

My DCS 2.5.2 installation started crashing regularly yesterday for no apparent reason, so I decided to perform a clean reinstall. Problem is that it has taken me over 12 hours to install DCS 2.5.2 successfully (just the basic game, no modules yet), here's why: 1- DCS 2.5.2 installer consistently downloads/installs corrupted files without returning any kind of warning. This happened to me with both "stable" and Openbeta builds of DCS 2.5.2. (No antivirus, no other programs actively running, just basic services and device controllers running on the background , full permissions everywhere, DCS allowed through firewall and added to the exclusion lists of all programs I could think of, etc. ) 2- DCS_updater.exe consistently fails to detect corrupted files. I've run it on repair mode (via command prompt) dozens of times and it has simply failed to detect and replace corrupted files in every single installation attempt. I've attached a corrupted "db_weapons_data.lua" which was preventing DCS.exe to launch after my last installation attempt (no error message returned). The corrupted code can be found between lines 1701 and 1732. DCS_updater.exe failed to "flag" the file as corrupted when I ran it in repair mode. It just finished the whole verification process normally, as if all files were ok. You should be able to replicate this by creating a backup of your "healthy" db_weapons_data.lua and then replacing the original by this corrupted version. DCS.exe should fail to launch (without returning any error message) and DCS_updater.exe should fail to detect and replace it when running on repair mode. I discovered the issue while checking the attached dcs.log , btw. I fixed the problem by deleting the corrupted file and running DCS_updater.exe in repair mode again. This time the updater "saw" that the file was missing and provided a "healthy" one, at long last. 3- The initial download (via torrent) is quite fast, however, the subsequent update downloads (non-torrent, I guess) are extremely slow, especially if we consider the massive size of the updates. It takes forever to download a 20+GB update at a speed of around 1MB/s, by comparison, downloads via torrent run at a consistent 30+MB/s in my rig. Please, ED: -Implement a working file integrity check during installation. -Fix the DCS_updater.exe repair functionality, so it's actually capable of detecting and replacing corrupted files. -Force DCS.exe to automatically return an error message whenever a corrupted file is found. Players shouldn't be forced to analyze the dcs log and figure out this kind of stuff by themselves. Getting the game to launch successfully shouldn't be this hard. Thanks db_weapons_data.lua dcs-log.rar

It would be cool if you could post the final script here once you get it working. Nice function to have in any mission :thumbup:

@Habu_69 Thanks for taking the time to answer in such detail! I've been wrestling with different menu/command script examples these last days and I think all the frustration/cluelessness I've been through is starting to pay off. I've just written a script that provides custom nested command menus for each plane group, which in turn trigger custom messages and sound files. Tomorrow I'll figure out a way to remove the commands after execution (I hope). It'll probably take a general overhaul of the script, but I'm feeling confident after today's breakthrough. :v: Once my script is polished and perfected to my satisfaction, I'll probably post it here as an example for desperate people (like myself). Thanks for your help. PS: I joined the MOOSE Discord channel like you suggested, I already got valuable help from Pikes. It seems like a great place to get quick help with specific things and also to learn from what others have done :thumbup:

Hi Delta! Sadly, the "settings" parameter doesn't seem to be the problem. Intellisense adds it automatically when I select the "MESSAGE:ToGroup" function... I think it adds an F10 settings menu that is already included in MOOSE by default (not sure though). Anyway, if I remove it, the problem persists. Just to make sure, you are referring to this, right?: Su33AirRefuelingBriefingRed:ToGroup(SochiGroup,[b]Settings)[/b] Su33Briefingmessage:ToGroup(KuziGroup,[b]Settings[/b]) For some reason, the script I wrote only works for the first group being referenced, it ignores instructions for the second group. I'm probably writing it wrong or just using an invalid logic or whatever. @Habu__69 Wow, thanks a million for that! There are several things in that script that I don't understand, though: 1- Function "ReqHelp()" (which includes BanditsHot:Remove) being written on top of the MenuScheduler function (which declares BanditsHot when the player is partly in zone, as I understand it). Shouldn't it be written the other way around? I mean, first declare all the stuff, then execute the functions that use the declared stuff? 2- What does "{}" mean ??? I understand it's used to create arrays, right? Intellisense is telling me that's supposed to be a...function argument? It's included in timer.scheduleFunction and then repeated at the end...:huh: 3- The whole timer.scheduleFunction / menuScheduler thing eludes me. Why do you need those and what do they do exactly? 4- How would I go about turning this script into local instead of global? 5- Are zone triggers needed or can this be done without them? 6- Where does that "EnfieldMsg" function come from? Please, don't get me wrong! I'm not questioning your scripting style or anything like that, just trying to understand how this all works :shocking: Also, could you please attach a simple mission example with that script and all the required triggers in place? I think that would help me figure things out. (I don't own the F18 module, btw, just FC3, Mi8, Huey, CA and a couple other modules I haven't even installed) Thanks again!

Need pointers for custom menu creation and command insertion with MOOSE Thanks Delta, that did the trick! Problem now is to assign my ogg sound files to custom menu commands without issues... Not only that, though, since building customized menus with MOOSE seems to be already daunting, even with the script examples and test missions available online, I just fail to grasp the underlying structure/order/logic, which leads to my scripts not working. For instance, here I tried to play 2 different ogg files along with their respective text messages for two different groups (when I spawn them for the first time): This script results in only Su33briefing and Su33Briefingmessage being played on spawn (to KuziGroup). SochiGroup never receives its spawn messages (even when I spawn it first on mission start). I noticed that the opposite happens (ie KuziGroup stops getting its messages) when I write the script in the opposite order, like this: So that means I must be writing it wrong. I've tried several different versions of this script, the most I've been able to achieve is make these spawn sounds and messages play correctly ONLY when I assign the script file to a continuous trigger (obviously, the problem then is that the messages won't stop playing :cry:). The only other option that has worked for me is to just write 2 separate script files, one for KuziGroup and another for SochiGroup (running on separate triggers). As for building customized F10 menus with MOOSE, I found this example on github: After spending several hours trying to understand it and failing to make it work in my script, this was my conclusion ---> :helpsmilie: I really want to avoid ending up here all the time, asking people to teach me how to do specific things in MOOSE. I'd love to have the MOOSE menu/command building procedure explained somewhere, so I could just go there and learn on my own :book:. I'm sure many more players would start using MOOSE if this kind of things were explained somewhere, step by step... I mean, like "First you need to declare this, this and that. Then you have to specify this or that, then you must set a logic in place, etc." Eclipse, the github documentation, the mission example files, flightcontrol YT videos, etc. help quite a bit, but noobs like myself need direction to do pretty much everything. We live in a state of permanent doubt when scripting and when our scripts don't work (almost always the case) we just go like this --->:crash: :surrender:

Where do I put my ogg sound files for MOOSE to play? Hi, I've checked the github documentation regarding usersound functionality. While that's probably enough to write a functional script, I still have no idea of how to tell MOOSE where my custom ogg sound files are. For instance: local BlueVictory = USERSOUND:New( "BlueVictory.ogg" ) local PlayerGroup = GROUP:FindByName( "PlayerGroup" ) BlueVictory:ToGroup( PlayerGroup ) This is nice and all, but how does MOOSE know where to find that "BlueVictory.ogg" file? Do I need to set up my custom ogg files in the mission editor first? Do I need to place them somewhere specific? I'm at a loss here, any help would be appreciated :cry:

Hi! Thanks to some old threats like this one, the hoggit wiki, a bit of intuition and luck, I've been able to create a nested F10 radio command menu for a SP mission I'm making (DCS 2.5). I've also managed to get those nested F10 radio commands to actually trigger flags correctly, which has been a massive breakthrough for me. Now, however, I've hit another wall (sort of) and I don't think I can surmount it without help. I basically have two problems: 1- I don't know how to apply a single command to a set of strings/GroupIDs (I don't even know if it's possible with the method I'm currently using) Example: local subN4 = missionCommands.addSubMenuForGroup(5 ,'Su33 air refueling -Kuznetsov-', subR) I would like this single command to also apply to strings/groupIDs 10 and 51, not just 5. I've already tried listing them as follows: 5,10,51 5..10..51 {5,10,51} 5 10 51 No dice... probably because I'm a total noob and I'm trying silly stuff, so bear with me, :Flush: Does the command "addSubMenuForGroup" even accept several groupID strings instead of just the one? The workaround I'm using atm is to just run the command individually for each string/groupID, which significantly increases the number of lines in my script and...well, looks kind of ugly, :thumbdown: 2- I'm having trouble figuring out how to remove those scripted radio commands once they've finished running. I've read several articles, posts and watched some YT videos, trying to come up with a way of doing this, but so far I haven't found anything I can use. I can remove my nested radio commands using this: missionCommands.removeItemForGroup(groupID, path) Problem is that I don't know how to write up a condition/logic, so this command waits for the right moment to run (ie wait for the radio message to be played first). Something like: if flag 1 = 1 (the radio command I want to remove triggers this flag in my script) then run missionCommands.removeItemForGroup(groupID, path) Would this kind of thing be doable in LUA? Also, from what I've read, I understand that if I set my script to global instead of local, I'd have no problem running the removeItem command on a separate trigger... but since someone said this can be dangerous, I'd rather not do it unless it's absolutely necessary. Here's part of my nested F10 radio menu script so far (seems to work without issues): How should I go about removing commands with this? Thanks in advance.

Su-33 carrier takeoff definitely works in 2.5, even at max weight. Here's what you need to do: 1- Set the pitch trimmer to neutral (it's set to negative by default). (Press RightCtrl+Enter to bring up the axis indicator on the lower right corner of the screen) 2- Make sure that flaps are fully extended 3- Open the engine inlet grids (press LeftAlt+I). You can check their status on the gear/flap indicator (the two green lights on top of the "wings" correspond to the engine inlets, I believe). They're on by default, so you'll need to switch them off. Once the engine inlets are open, you should get an extra 10% thrust. 4- Hold down the brakes 5- Maximum thrust (afterburners) 6- Once the two afterburner indicators light up in green, you can activate emergency thrust mode (LeftShift + E), if you do it correctly another indicator will light up in green (on a panel below). That'll run the engines at 103% 7- Release the brakes and start rolling. 8- You should be able to reach the end of the ramp at around 180Km/h. (That'll be enough for the plane to stay in the air, provided you pitch up correctly) 9- Once you jump off the ramp, lift the Su-33's nose sharply, so it stays in the air. At that point you won't be flying a plane, but a kind of rocket, so keep those afterburners pointing down at the sea and you'll be fine. 10- Once you've reached flying speed, disable emergency thrust mode by simply pulling back the throttle until afterburners are switched off. I have no problem taking off when following these steps.

Do you have a mouse with increased polling rate? In my case, the problem went away when I reduced mouse polling rate to normal levels (125Hz). Looks like the new graphics engine in DCS doesn't like higher mouse polling rates, for some reason...

Do you have civilian traffic enabled? If you do, then that's probably the issue. Disable civilian traffic and then report the result here. It solved the problem for me... it appears that civ traffic is a fps rapist, XD

Before doing that, you might want to monitor vram usage. That freezing you described could be explained by DCS 1.5 needing more vram than your gpu can deliver and then switching to RAM (which is slower). To monitor vram usage you can try MSI Afterburner+RivaTuner Statistics Server. If the freezing starts happening when vram usage reaches the gpu limit, then you've probably found the issue. Another explanation could be overheating...check gpu temps, if they are too high when you are in the cockpit, that could explain the freezing too. Another thing to check is the status of your disk. Is DCS 1.5 installed in the same disk as the operating system? How much free space does the disk have? Do you have a paging file enabled in that disk? Freezing can also occur when your disk runs low on space, keep that in mind. Another thing to check are power saving features for the hard drive and gpu, make sure all power saving features are disabled, everything should be running in performance mode. Finally, run "resource monitor" (Windows 7) to find out whether or not you have other programs taking too much resources in the background... (Antivirus, programmed tasks, etc.)

I don't know about you guys, but that made my day, XD.

Well, DCS 1.5 uses another graphics engine which is likely to use more vram. Have you monitored vram usage with sofware like MSI Afterburner+Rivatuner statistics server? I think you should do it. It definitely seems like there's no anisotropic filter being applied... Have you tried reinstalling DirectX? If I were you, I'd eliminate the DCS profile in your graphics driver settings and see if that changes anything. Btw, you haven't provided system specs yet.

Yup, I still remember all those users saying stuff like "EDGE won't improve fps except in dual gpu systems, etc." XD Anything that runs on DirectX11 (rather than DirectX9) will be able to reach higher levels of performance, 1.5 is yet another example of this. I'm glad that EDGE has delivered the performance increase I was expecting, it was worth the wait.

I'm having the same issue, here you have a couple of screenshots: This issue seems to be specific to the Mi-8, the rest of aircraft work normally (as far as I could tell). This happens regardless of the skin applied to the Mi-8, and regardless of the game mode (instant action, custom mission, campaign, multiplayer, etc.). I have a hypothesis (the bug thread guideline didn't say anything about posting hypothesis, it only referred to theories). My hypothesis is that this missing texture issue has to do with the LOD of the Mi-8 model. There's a bugged LOD step that doesn't allow the texture to be displayed. My specs: i7 2600k (oc 4.3GHz) ga-z68xp-ud3 mobo Sapphire R9 290 Tri-X OC 16GB ram (4x4GB config, 1600MHz) SSD OCZ Vector 120GB (AHCI enabled) Windows 7 Ultimate 64bit ... I guess the rest is irrelevant All the drivers I can think of are up to date. I'll keep trying different settings in Catalyst, but, as I said, this issue seems to be related to LOD.