sideshow

So I've noticed that when the Cowl flaps are fully open I have this issue. If they're closed, or mid position, the flaps, wing fold, and tail wheel work. So to test this, start with the cowl flaps fully open, and attempt to spread the wings. For me the wings get stuck. I close the cowl flaps, and they spread as they should. This is also the same when it comes to flaps and the tail wheel getting stuck down.

Thanks!

Can anyone post the updated EFM.lua? I've been trying to figure out where in the scripts to paste the new line to bind the wing fold to the flaps unsuccessfully. Thanks

For me, excluding the DCS folder as a whole did not work. First, the folder was already in my exclusions. Second, when I ran a repair it immediately flagged the .dll and wouldn't install it. I had to disable Windows Virus and Threat Protection, run a repair, exclude the F14-HeatblurCommon.dll file, and then turn virus and threat protection back on. At least for now that works.

You need to enable the system select knob to both on the trim panel. The startup tutorial doesn't mention this. I tried taking off and had the same issue. The taxi takeoff tutorial mentions it.

Hello. DCS Multithread has worked fine for me until 4/7. I flew a mission, quit, and tried loading the sim again. From then on out I've been getting a crash at the splash screen. It's like the sim doesn't even attempt to load. I fly in VR with an HP reverb. I know there's a crash affecting Oculus users, but I don't have an Oculus. Any help would be appreciated. Thanks. dcs.20240410-041117.crash dcs.20240410-041117.log

On Mission 14 I start up, head to cat i when directed, and fly to marshall. The rest of the group radios in as they push and leave the stack. I check the boat and there's 3 tomcats on deck, Olive, and the one hornet that has the VMFA-122, think the stand in for the ea6b on deck. All the jets are turning with pilots visible in them. However, they don't take off. I sat at marshall waiting for Olive, and got the play-by-play on strike as the Tornados arrived and, and one gets shot down. Am I doing something wrong? Will try pushing to the tanker and seeing if that changes anything. Running Open Beta 2.9.1.48335.

It started working again for me the next day.

Good to know. Thought I got hacked.

I renamed the folder and started DCS. Once I switched to VR I got the same black screen. I tried updating windows, but it says I'm up to date. My I7 processor isn't compatible with Windows 11 per windows updater. I also checked my drivers for the Oculus and graphics card. They're showing up to date too.

I updated to Open Beta 2.7.17.29140 and now have a black screen once the game starts. I get the UI music, therefore I don't believe it's a crash. The screen is black in both the headset and monitor. I went into the config folder and deleted the options LUA which reset the sim back to 2D. However, when I put it back into VR I get a black screen. I attached my logs. Any help would be appreciated. DCS-SRS-InGameRadio.log dcs.log DCS-SRS-GameGUI.log dcs.log.old

I’ve started remapping everything in RSmapper to simplify things. The key binds are a bit much, but so far my only complaint.

The first mission was awesome. Good way to start the campaign. The first raven one campaign hooked me till the last mission. Played out like a good book. One thing to remember when you divert is to turn that antiskid on for the runway. Otherwise you’ll lock the brakes up.

I have yet to get ACLS to work. I set everything up in mission editor. In mission I get and follow all of the DATA queues. When I get the ACL ready command on the MFD, and the boat says "switch mode 2" I engage auto throttle and couple the auto pilot. Right under 6 miles, at 1200 feet and on angle. Instead of getting the CPL P/R, I get CPL HDG and the aircraft starts climbing. I feel like I must be missing one little step. Any suggestions?

I was wondering if that would be the case. I only had a short time to try it out, so didn’t dig to far into it after I ran into the issue.

I had the same thing happen. They say "copy". then that's the end of it. It's as if because they never prime the engines, the tutorial can't continue.

Thanks. I did back to back repairs and finally got it to work. Had never experienced that, and I haven't hade any issues since, so all is well.

I launch the SLAM around 40-50 miles, but I set the camera to power on at around 10-15 miles from the target. Even then I don't dare attempt to steer it until it starts it's terminal dive. By then it's usually diving right the target set by WPDSG or the flir pod. I don' think the point of the camera is to pick your target out as the missile is flying through the air.

I noticed the same thing. Problem isn't being able to locate the folder, it's the fact that the files don't populate after you enter the game.

Just tried updating, and got an error which states incorrect data. It opened a log, which I've included. It appears this has something to do with unpacking a file? Anyone know hotw to fix this? Thanks log: 00000.061 --- Log file: c:\Program Files\Eagle Dynamics\DCS World OpenBeta\autoupdate_log.txt 00000.000 === Log opened UTC 2020-12-17 23:14:02 00000.013 INFO : DCS_Updater/2.10.6.63 (Windows NT 10.0.19041; Win64; en-US) 00000.013 INFO : src-id: baf92d0a5bb967be5dcb68784e54459d083e8c3d, lib-id: bae3744c50d64647d7c5ee5a1236d3ae42dbbb1e 00000.013 INFO : cmdline: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe" --apply update C:\Users\jimmy\AppData\Local\Temp\DCS.openbeta\update_info.json 2.5.6.59398 00000.057 STATUS: Initializing... 00000.058 INFO : basedir: c:\Program Files\Eagle Dynamics\DCS World OpenBeta 00000.058 INFO : dcs_variant.txt: openbeta 00000.062 INFO : DCS/2.5.6.58125 (x86_64; EN; WORLD,YAK-52,FA-18C,RAZBAM_AV8BNA,NS430_MI-8MTV2,NS430,WWII-ARMOUR,AJS37,F-5E,POLYCHOPSIM_SA342,RAZBAM_M-2000C,MIG-21BIS,F-86F,MI-8MTV2,UH-1H,A-10C,CA,P-51D,F-15C,LAIVYNAS_MI-8MTV2_OILFIELD_campaign,A10C-BFT_campaign,A10C-REDFLAG_campaign,F15C-REDFLAG_campaign,PERSIANGULF_terrain,NORMANDY_terrain,NEVADA_terrain,AVIODEV_C-101,HEATBLUR_F-14,MAPLEFLAG_FA18C_AGGRESSORS_BFM_campaign,MAPLEFLAG_F5E_ACM_campaign,F-16C,DEKA_JF-17,SU-33,L-39,SPITFIRE-MKIX,RAZBAM_MIG19P,SUPERCARRIER,P47D30,THECHANNEL_terrain,SYRIA_terrain,BALTICDRAGON_FA18C_RAVEN_ONE_campaign,NS430_C-101EB,NS430_C-101CC,A-10C_2) 00000.062 INFO : branch: openbeta 00000.905 INFO : Got reply from www.digitalcombatsimulator.com 00000.906 STATUS: Verifying cached version info... 00001.536 STATUS: Verifying installed files... 00012.410 INFO : 0 files are changed or missing. 00017.964 STATUS: Preparing download... 00018.556 INFO : To download: 6278108560 bytes in 1 files 00018.556 STATUS: Searching for already downloaded files... 00019.502 INFO : Found 0 local source(s). 00019.506 INFO : To download: 6278108560 bytes in 1 files 00019.507 STATUS: Downloading delta index... 00019.873 INFO : Got delta index. 00019.893 INFO : 0 bytes in 0 deltas to download. 00019.893 INFO : Found 0 matching deltas. 00019.897 INFO : To download: 6278108560 bytes in 1 files 00019.898 STATUS: Downloading update... 00019.899 INFO : Using 4 threads to decompress. 00019.899 INFO : Using HTTP download. 00087.791 ERROR: UNPACK_FAIL: (17028)->[GzipError: inflate: (-3) incorrect data check] c:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/terrains/Caucasus/Surface/Caucasus.surface5 00088.995 STATUS: inflate: (-3) incorrect data check 00093.754 === Log closed.

Thanks. I only asked because I can't get it to work. I can see the external model, but even when I click on client, it doesn't put me in the cockpit. Looks like an awesome mod though.

Does this mod require LockOn, or is it stand alone?

Here's a track of my last mission. LastMissionTrack.trk

Waypoint entry is broken for me too. Next time I fly I'll grab a track. But basically set a static object on the map. In game click on the object, and type it's coordinates in as a waypoint. When you hit WPDSG, the Coords listed in the FLIR will be the same, but the camera is looking off somewhere else. If you manually slew the FLIR over the static object, the coords displayed don't match what F-10 is saying. This has created issues with a SLAM mission I created, and have flown dozens of times in the past. Now using TOO mode, with WPDSG set, causes the missiles to not fly anywhere near the static object I used as a target. Everytime they fly to the same point, about a mile or so south of the target. I also tried setting a precise waypoint and still have the same issue.