Hexypu

Thanks draconus! Will try that out.

I didn't quite experienced the above as Wolf333 did, but along the same line with comm. I basically tried practicing my Case 1 recoveries from cold start (F-14B). After the first go round, following procedures with calls and such, landed, then got re-setup at catapult 1. What I experienced was that the deck crew just stay in "landing" (behind the foul lines) and did not spread out to support the next catapult shot. So I went to my comm menu and tried to request takeoff from the tower, but there were no options to do so. Therefore, I couldn't start another cat shot. Went to shutdown. When my engines came to a stop, the cat crews redeployed... and the comm menu then once again have the option to restart. Bug?

Interesting. I'm only seeing this thread now but I've had similar experiences before the 2.5.6 update so I don't know if it's still relevant. I remember at least twice it had happened. Once I was doing an auto throttle ICLS landing with flaps down, gear down, DLC on and wings on auto (I was on glideslope). The other, when I was approaching the boat from 20NM out doing ACLS with auto throttle (same setup for landing, also on glideslope). The aircraft would pitch up with no reason. I found myself having to push hard forward on the stick to land in the ICLS case (Case 1 scenario). I even tried DLC to compensate to no avail. It occurred fairly close to the ship within 1 to 3NM. As for the ACLS case, I aborted the landing and went around... can't remember the exact distance to the ship went it started (around 9 to 12NM?). No pitch up during the second go around. So it seems intermittent and only at slow speed.

Catapult problem. I tried launching in the Tomcat and after the salute (Shift U) would not launch the jet. At first I thought it was because of my pre 2.5.6 mission, but then tried making a new mission and the same is true. Carrier just won't launch aircraft.

I'm not seeing rain droptlet effects even with the option turned on (checkbox) in the Harrier after OB 2.5.3.21107 hotfix. Is anyone else having a similar problem? (PG map)

+1

When I was starting in the Harrier with AI wingmen, either ramp or hotspot, my AI wingmen would plow right into me from behind... like he was trying to takeoff before me. Can this problem be looked at? Note: I was in the Persian Gulf map if that matters any.

Game crashing Game crashed while flying Harrier multiple times on Nevada map. Error logs attached. dcs.log-20180806-053306.zip dcs.log-20180806-215537.zip

Hey Dflippink, thanks to your hint it seems to solve my problem with my longtime stutter problems. I run DCS on a medium rig and for the last year or two been having fps jumping from 9 to 60fps (I set my VSync on). Update after update I would hope that after each update things would improve... but mostly gotten worse over time. I would crash upon diving bomb runs because the lag would kept me from being able to pull out, not to mention AAR being almost impossible to plug into the basket. So for others who maybe having the same problems clearing "fxo", "metashaders" directories may help after repeated updates. My rig: ASUS Essentio Intel Core i5 4570 3.2GHz NVIDIA GTX 970 4Mb CRUCIAL DDR3 1600MHz 32Gb (recently upgraded from 16Gb but overclock not used so only running at 800MHz) TRACKIR 5 (thought this was the problem but it wasn't a contributor) Viewsonic VX2450 Series monitor (60Hz max) DCS: Texture - HIGH Terrain Texture - HIGH Water - HIGH Visible range - HIGH Heat blur - HIGH Shadows - LOW Resolution - 1920x1080 Aspect ratio - 1.77 Res. of cockpit displ. - 1024 every frame MSAA - 2X Depth of field - OFF Lens effect - Dirt+Flare Motion Blur - OFF SSAA - OFF Clutter grass - 0 Trees visibility - 80% Preload radius - 120200 Chimney smoke dens. - 2 Anisotropic filtering - 16X Terrain obj shadows - DEFAULT Ckpt global ill. - OFF Rain droplets- ON VSync - ON (all other checkboxes - OFF) Hopefully this will help someone else. Cheers! UPDATE: This setup is good on all maps including recent Persian Gulf

Update: Ok here's something interesting. It's probably non-consequential since the rolling short takeoff feature isn't implemented/considered (especially for airfields), but I tried the same load out (full fuel load and weapons) with the Caucasus map and the AI tookoff of the Tarawa no less, not using STOL but VTOL! So my hunch... it's something to do with the Nevada map perhaps? Maybe I'll try again on a Georgian airfield.

Ok, thanks! I guess rolling takeoffs are not in the works yet.

I was playing with my AV-8B, setting up to takeoff at Nellis and Laughlin with an AI wingie (DCS 2.5OB), and found that my AI wingman won't takeoff after a short running start. The AI just remained on the runway with full engine on. Curious, I then set the flight to just AI only to see if both would do the samething just to see if it's because one plane was player controlled... and they both did the samething. Stuck on the runway with full engines on! This happened while at these two airfields, I haven't checked others. Can anyone else see if they have the same problem?

Falling through the port elevator I've tried looking for other threads regarding this bug but haven't found it anywhere else, so moderators if you think it not the right place to post please move it, thanks! Since everyone here is talking about the Tarawa: recently I've been landing in spot "7 1/2", the slot between 7 and 8, with the Harrier's wheel close to the edge where the port elevator and the main part of the Tarawa is, my Harrier's left outrigger gear/wheel falls through the elevator as I passed over it taxiing to park the aircraft. It seems the port elevator surface was not defined to be solid and I have the aircraft fallen through once and stuck precariously twice.

UPDATE: Went in and tried the workaround... and it doesn't work! Looks like I can't use the gun pods because there's no way to turn them on. All these different DCS versions are not helping with bugs it looks like, at least LNS is not keeping up with things.

Oh, so it IS a bug at this moment and I did use ME to set it up. Just wanted to check to make sure of my sanity since it should've been in front of my face all this time [as in what the flight manual mentioned]. :) Can't use those pods otherwise. Thanks for the help Malek! I will give it a shot (literally)!

I wanted to try the gun pods but can't locate the control box when I do ramp start. I looked in the manual and it mentioned the control box is supposed to appear in the cockpit whenever I have the gun pods mounted in the inner pylons. Can someone give me a hint as to why the control box doesn't appear? Thanks!

Update Apparently the flaps weren't the problems either... let me recount what I found. Here is the scenario: I was playing around with the MiG-21Bis trying to see if I could scramble from a small airfield with RATO. I picked Boulder City Airport in DCS 2.0 (near where I live). I made a very basic setup in ME for a ramp start - dropped the aircraft on a spot literally. Initially ME automatically set me on parking spot B03, but I didn't like that and move my parking to spot B05. On starting up the sim I noticed that there was this loud noise, like a loud bang as the nose (more like the entire MiG) bounced/hit the ground. I didn't pay much attention to it as it has happened before when I started up the MiG at Kutaisi, Kobuleti or Batumi (though the effect was less pronounced or none at all, just the noise). Then as I proceeded to take off, the front gear didn't retract as I mentioned before. Reason? The front gear was apparently damage! I traced it back to that jolt when the aircraft entered the sim with that big "bang". Like I said, I have noticed this noise before in DCS 1.5 on Georgian airfields but not quite like this in 2.0. Curious, I changed to other parking positions and found that on B05 and B06 caused the front gear to get banged up also. But positions B01, B02, B03, B07 and B03 there were the same jolt upon entering the sim but not hard enough to damage the nose gear. So the conclusion that I could come up with is with DCS 2.0 and these particular parking positions on this airfield. Something with the airfield height perhaps. I even noticed that the MiG pulls right as I taxi east towards runway 27 to takeoff, as if the runway was not leveled. I believe my stick is decently zeroed as taxi/takeoff from Nellis has none of these problems. Could someone else confirm what I have found here? For both 2.0 and 1.5? Also, I continued this thread because I thought there was an anomaly/bug with the Fishbed but I'm starting to think it's a problem with the map. In which case could any moderator move this to it's appropriate sub heading? Thanks! PS - I haven't tried the other new airfields in 2.0 but will give it a look later.

This is what I did... Rotational speed: 300 kph Gear retraction speed: ~320kph Loadout: Clean RATO: On AB: 2nd stage So the only thing I didn't notice was that I had placed flaps in full down, oops! That seems to be the problem... I usually set flaps in the correct position but don't know why I left it in full down that time. Guess in my scramble I had set it wrong. My error! That would explain why in DCS 1.5 the takeoff went without a hitch. :P Thanks Obr. Elmo for that quick troubleshoot!

I was flying in DCS 2.0 (build 2.0.4.59428 ) after takeoff I noticed the main gear retracted while the nose gear was still left dangling. I also tried DCS 1.5 (build 1.5.5.58891) but the landing gear retracted fully, all three. I think the MiG has problem with the landing gear in DCS 2.0. Does anyone else observe this same problem?

I did a number of folder deletes and repairs but still didn't start up. So I eventually uninstalled then reinstalled 1.5 Beta and it now starts up. Log file attached below: === Log opened UTC 2016-07-17 00:08:47 00000.000 INFO VFS: Using 'Saved Games': "C:\Users\n2abs\Saved Games" 00000.259 INFO DCS: DCS/1.5.4.54855 (x86_64; Windows/10.0.10586) 00000.259 INFO DCS: CPU cores: 4, System RAM: 8099 MB 00000.327 INFO EDCORE: (dDispatcher)enterToState_:0 00000.586 INFO Dispatcher: 2016/7/16 17:08 V1508170900 00000.720 INFO INPUT: Device [Keyboard] created deviceId = 1 00000.722 INFO INPUT: Device [saitek Pro Flight X-55 Rhino Stick {5E0CF580-482B-11e6-8001-444553540000}] created deviceId = 2 00000.722 INFO INPUT: Joystick created[saitek Pro Flight X-55 Rhino Stick {5E0CF580-482B-11e6-8001-444553540000}], ForceFeedBack: no 00000.727 INFO INPUT: Device [saitek Pro Flight X-55 Rhino Throttle {5E0CF580-482B-11e6-8003-444553540000}] created deviceId = 3 00000.727 INFO INPUT: Joystick created[saitek Pro Flight X-55 Rhino Throttle {5E0CF580-482B-11e6-8003-444553540000}], ForceFeedBack: no 00000.728 INFO INPUT: Device [Controller (Xbox One For Windows) {DD399FE0-4545-11e6-8001-444553540000}] created deviceId = 4 00000.728 INFO INPUT: Joystick created[Controller (Xbox One For Windows) {DD399FE0-4545-11e6-8001-444553540000}], ForceFeedBack: no 00000.756 INFO INPUT: Device [Mouse] created deviceId = 5 00000.765 INFO INPUT: Device [TrackIR] created deviceId = 6 00002.440 INFO SOUND: loaded 1096 sdefs from "sounds\sdef" 00003.133 INFO SOUND: Using driver: xaudio29 00003.350 INFO SOUND: XAudio2: channel layout: Headphones/Stereo 00003.350 INFO SOUND: Using SSE FTZ/DAZ mode. 00005.999 ERROR VFS: Can't mount './CoreMods/aircraft/Hawk/Textures/Avionics' to '/textures/'. 00006.013 ERROR SOUND: can't open proto file ".\coremods\aircraft\m-2000c\sounds\sdef\effects\aircrafts\engines\snecmam53\e_m2kc_combstart.sdef" 00006.013 ERROR SOUND: failed to load sdef Effects/Aircrafts/Engines/SnecmaM53/e_M2kC_combstart referenced in .\coremods\aircraft\m-2000c\sounds\sdef\aircrafts\engines\snecmam53\e_m2kc_combustion_full.sdef 00006.035 INFO SOUND: loaded 19 sdefs from ".\coremods\aircraft\m-2000c\sounds\sdef" 00006.035 ERROR VFS: Can't mount './CoreMods/aircraft/M-2000C/Skins/1/ME' to '/textures/'. 00006.035 ERROR VFS: Can't mount './CoreMods/aircraft/M-2000C/Textures/Weapons' to '/textures/'. 00006.054 INFO SOUND: loaded 10 sdefs from ".\coremods\aircraft\mig-21bis\sounds\sdef" 00006.080 INFO SOUND: loaded 7 sdefs from ".\coremods\aircraft\sa342\sounds\sdef" 00006.174 INFO SOUND: loaded 59 sdefs from ".\mods\tech\combinedarms\sounds\sdef" 00006.277 INFO SOUND: loaded 67 sdefs from ".\mods\aircraft\bf-109k-4\sounds\sdef" 00006.358 INFO SOUND: loaded 53 sdefs from ".\mods\aircraft\f-86\sounds\sdef" 00006.465 INFO SOUND: loaded 59 sdefs from ".\mods\aircraft\fw-190d9\sounds\sdef" 00006.501 INFO SOUND: loaded 27 sdefs from ".\mods\aircraft\hawk\sounds\sdef" 00006.511 INFO SOUND: loaded 4 sdefs from ".\mods\aircraft\ka-50\sounds\sdef" 00006.567 INFO SOUND: loaded 40 sdefs from ".\mods\aircraft\m-2000c\sounds\sdef" 00006.662 INFO SOUND: loaded 70 sdefs from ".\mods\aircraft\mig-21bis\sounds\sdef" 00007.037 INFO WorldPlugIns: No 'registryPath' for 'AVIODEV_C-101' 00018.407 INFO WorldPlugIns: No 'registryPath' for 'BALTICDRAGON_A10C-ENEMY_WITHIN_campaign' 00018.407 INFO WorldPlugIns: No 'registryPath' for 'SU27-ULTIMATE_campaign' 00018.455 INFO GRAPHICSVISTA: Creating Resource "Unicode" of type 1 00018.502 INFO DX11BACKEND: TRUNK renderer init: showShaderError coreCount=1 00018.588 INFO DX11BACKEND: Driver Concurrent Creates - 1 00018.588 INFO DX11BACKEND: Driver Command Lists - 1 00018.588 INFO DX11BACKEND: DX11ShaderBinaries::loadShaders 00018.588 INFO DX11BACKEND: DX11ShaderBinaries::loadCache Bazar/shaders/fxo 00024.444 INFO DX11BACKEND: DX11ShaderBinaries::loadCache done 00024.445 INFO DX11BACKEND: DX11ShaderBinaries::loadCache C:\Users\n2abs\Saved Games\DCS.openbeta\fxo 00024.445 INFO DX11BACKEND: DX11ShaderBinaries::loadCache done 00024.445 INFO DX11BACKEND: DX11ShaderBinaries::loadShaders finished 00024.463 ERROR VFS: Can't mount './Bazar/EffectViewer/envcubes' to '/textures/'. 00024.640 ERROR VFS: Can't mount './Mods/tech/Kuznecow/Textures/TUG_3913' to '/textures/'. 00024.753 INFO RENDERER: Global metashader cache enabled 00024.753 INFO RENDERER: Loading metashader cache from C:\Users\n2abs\Saved Games\DCS.openbeta\metashaders/ 00024.753 INFO RENDERER: Metashader cache: 0 (0) cached shaders out of date 00025.170 ERROR DX11BACKEND: rendertarget "rtDynamicCloudMap" not found 00025.183 INFO EDTERRAINGRAPHICS3: edtg::CreateSurfaceRenderItem() 00025.742 ERROR EDOBJECTS: Destruction shape not found AVIASHTAB_CRASH 00025.744 INFO TERRAIN: lSystem::lSystem 00025.774 INFO EDCORE: (dDispatcher)enterToState_:1 00027.108 ERROR VFS: add_location {"My Missions", "C:\Users\n2abs\Saved Games\DCS.openbeta\Missions\"}: path already added as "My Missions" 00034.572 INFO DXGUI: Cannot load font [D:\DCS World OpenBeta\dxgui\skins\fonts\]! 00036.588 INFO EDTERRAINGRAPHICS3: edtg::CreateSurfaceRenderItem() 00041.550 INFO EDCORE: (dDispatcher)enterToState_:2 00041.721 INFO EDCORE: (dDispatcher)enterToState_:3 00045.638 INFO NET: Login success. 00050.230 INFO EDTERRAINGRAPHICS3: edtg::DeleteSurfaceRenderItem() 00050.232 INFO EDCORE: (dDispatcher)enterToState_:5 00050.347 INFO SOUND: detaching sdef path ".\mods\aircraft\tf-51d\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\mods\aircraft\p-51d\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\mods\aircraft\mig-21bis\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\mods\aircraft\m-2000c\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\mods\aircraft\ka-50\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\mods\aircraft\hawk\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\mods\aircraft\fw-190d9\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\mods\aircraft\flaming cliffs\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\mods\aircraft\f-86\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\mods\aircraft\bf-109k-4\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\mods\aircraft\a-10c\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\mods\tech\combinedarms\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\coremods\aircraft\sa342\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\coremods\aircraft\mig-21bis\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path ".\coremods\aircraft\m-2000c\sounds\sdef\" 00050.347 INFO SOUND: detaching sdef path "sounds\sdef\" 00050.361 INFO TERRAIN: lSystem::Exit() 00050.361 INFO TERRAIN: lSystem::CleanScenes() 00050.361 INFO EDTERRAINGRAPHICS3: edtg::Exit() 00050.522 INFO EDTERRAINGRAPHICS3: edtg::DeleteSurfaceRenderItem() 00050.523 WARNING LOG: 1 duplicate message(s) skipped. 00050.523 INFO EDTERRAINGRAPHICS3: edtg::Exit() === Log closed.

Hmm, interesting. I didn't do any modding at all before the update. I'll try reinstalling and see what happens.

Ok, I did as suggested and performed a repair but it's still not launching. Any other options I could try?

I just updated my Beta and the sim won't run. Can anyone give me a hand? Thanks in advance. === Log opened UTC 2016-07-16 00:07:06 00000.000 INFO VFS: Using 'Saved Games': "C:\Users\n2abs\Saved Games" 00000.095 INFO DCS: DCS/1.5.4.54855 (x86_64; Windows/10.0.10586) 00000.095 INFO DCS: CPU cores: 4, System RAM: 8099 MB 00000.099 INFO EDCORE: (dDispatcher)enterToState_:0 00000.104 INFO Dispatcher: 2016/7/15 17:07 V1508170900 00000.119 INFO INPUT: Device [Keyboard] created deviceId = 1 00000.119 INFO INPUT: Device [saitek Pro Flight X-55 Rhino Stick {5E0CF580-482B-11e6-8001-444553540000}] created deviceId = 2 00000.119 INFO INPUT: Joystick created[saitek Pro Flight X-55 Rhino Stick {5E0CF580-482B-11e6-8001-444553540000}], ForceFeedBack: no 00000.124 INFO INPUT: Device [saitek Pro Flight X-55 Rhino Throttle {5E0CF580-482B-11e6-8003-444553540000}] created deviceId = 3 00000.124 INFO INPUT: Joystick created[saitek Pro Flight X-55 Rhino Throttle {5E0CF580-482B-11e6-8003-444553540000}], ForceFeedBack: no 00000.125 INFO INPUT: Device [Controller (Xbox One For Windows) {DD399FE0-4545-11e6-8001-444553540000}] created deviceId = 4 00000.125 INFO INPUT: Joystick created[Controller (Xbox One For Windows) {DD399FE0-4545-11e6-8001-444553540000}], ForceFeedBack: no 00000.149 INFO INPUT: Device [Mouse] created deviceId = 5 00000.154 INFO INPUT: Device [TrackIR] created deviceId = 6 00000.265 INFO SOUND: loaded 1096 sdefs from "sounds\sdef" 00000.295 INFO SOUND: Using driver: xaudio29 00000.310 INFO SOUND: XAudio2: channel layout: Headphones/Stereo 00000.311 INFO SOUND: Using SSE FTZ/DAZ mode. 00000.666 ERROR VFS: Can't mount './CoreMods/aircraft/Hawk/Textures/Avionics' to '/textures/'. 00000.669 ERROR SOUND: can't open proto file ".\coremods\aircraft\m-2000c\sounds\sdef\effects\aircrafts\engines\snecmam53\e_m2kc_combstart.sdef" 00000.669 ERROR SOUND: failed to load sdef Effects/Aircrafts/Engines/SnecmaM53/e_M2kC_combstart referenced in .\coremods\aircraft\m-2000c\sounds\sdef\aircrafts\engines\snecmam53\e_m2kc_combustion_full.sdef 00000.670 INFO SOUND: loaded 19 sdefs from ".\coremods\aircraft\m-2000c\sounds\sdef" 00000.670 ERROR VFS: Can't mount './CoreMods/aircraft/M-2000C/Skins/1/ME' to '/textures/'. 00000.670 ERROR VFS: Can't mount './CoreMods/aircraft/M-2000C/Textures/Weapons' to '/textures/'. 00000.672 INFO SOUND: loaded 10 sdefs from ".\coremods\aircraft\mig-21bis\sounds\sdef" 00000.680 INFO SOUND: loaded 7 sdefs from ".\coremods\aircraft\sa342\sounds\sdef" 00000.691 INFO SOUND: loaded 59 sdefs from ".\mods\tech\combinedarms\sounds\sdef" 00000.691 ALERT DCS: Error running Scripts/Database/db_scan.lua: [string "./Scripts/Database/db_mods.lua"]:102: table index is nil

I live in Boulder City, Nevada and was so excited when this area was offered in DCS and immediately bought it when I saw it offered. It was a long download but definitely worth it since I got to buzz my house in Boulder City (or roughly where my house is supposed to be) in the Fw-190. I'm sure the neighbors were terrified to see a WW2 German plane roaring so low overhead. I have a mid range rig and the frame rate was suffering but it's so cool to be able to get away from the Black Sea after 10+ years! Can't wait to take the MiG-21bis out and break some windows over the Strip at supersonic!

I'm having trouble communicating with the ground crew from the cockpit of the MiG-21. I created the mission in ME and was running it in World 1.5 (the latest update: 1.5.046x?). The aircraft was at a friendly base and switch RV17 was not set to "on" (to talk to ground crew) but the option was blacked out.