All Activity

Come join VWA today to learn pretty much any airframe in DCS!

ooooo! sorry to hear that.

did you by chance make a manual edit to your HOST file located in C:\Windows\System32\drivers\etc? probably not since the hostname is resolving to the correct IP address. not sure how easy it would be but you could try to get your ISP involved.

i personally upgraded recently and had no issues. i think there was a tad better performance.

welcome back. rename the DCS folder within Saved Games to DCS.BAK. Restart DCS and see if DCS will start. a new DCS folder will be created. if DCS runs, great. then you can grab your INPUTS folder from the backup DCS folder.

I seem to be having a problem downloading the DCS OH6A Zip file from Github, there seems to be a 1Gb limit on file downloads as I get the following error every time that I try and download the ZIP file ( The download stops and I get "Check Internet Connection" message) This happend for both the OH-6a as well as the A4 zip files both of which are over 1Gb in size. Does anyone know of any other sites that these files can be downloaded from?

As an airplane increases or decreases speed, the amount of lift generated will also change. This requires that you move *and hold * the control stick forward (nose down) or backwards (nose up) to maintain any give altitude. This is true of any airplane where the control stick is physically connected to the elevator surfaces. For example, if you increase speed by adding power, your airplane naturally wants to climb from the additional lift. That means you must push forward/move control surfaces downward, *and hold* to counteract the lift of the wings if you want to maintain your current altitude. With sufficient speed, this will mean the elevator surface will be visibly deflected in order to cause the nose to lower. The stick in the cockpit will also be in a new position because it’s directly connected to the elevator. If you are continually accelerating, the force needed to move the elevator further nose down to maintain altitude continues to increase greatly, to a point that the pilot would not have enough strength to continue pushing any further forward. At that point, the plane would simply continue to climb, until you reduce your power. Trim is necessary because it relieves the heavy forces necessary to hold the control surfaces at that new position. This means that after you trim the airplane for a new airspeed, the control stick no longer requires force to stay in that new position necessary to maintain altitude. But critically, as a natural consequence of the stick being physically linked to the control surface, the stick *MUST* be in a new position if you go “hands off”. So, in other words, the stick will be in a new position after trimming. There is simply no way around this for planes that use cables, push-pull rods, and bell cranks to connect the stick to the control surfaces. My apologies for being so wordy. The way trimming works is harder to understand when it’s being explained in words. Once you fly an airplane and viscerally feel the control pressures and movements needed to maintain level flight as airspeed changes, it becomes much easier to understand how it works, and what it looks like when it’s used. Force feedback joysticks were created solely to simulate these forces.

The issue is back for us too despite the alleged fix by removing the sa-11 and sa-10. The servers are crashing every 2-3h now and pisses off alot of players. Our servers hit 30-50 players almost daily and we have no clue why it keeps crashing. Sometimes its the wSimCalendar Event and sometimes the log just ends suggesting the DCS_Server.exe just crashed. It would be great if we could get an update on this issue or atleast help you find the cause.

I saw some YouTube videos showing test footage of ZEL in West Germany during the 1960s.

Armed Blackhawk v6.0 is still a "sub-mod" and requires the UH-60L to be installed first, currently v1.4. Glad its working for you!

Thanks! It does, but only with absolute paths (relative paths fail with error: 31) and string literals. That is not ideal, because the literals differ for every dedicated server instance. That requires to modify each config file instead of relying on auto-configuration. Attempting to dynamically set the writedir in options.lua via ["tacviewExportPath"] = lfs.writedir() .. "Tacview", fails for lack of the lfs module. Same with environment variables for lack of os.getenv(). Trying to set it from a hook script as follows net.dostring_in("config", [[ options.plugins.Tacview.tacviewExportPath = lfs.writedir() .. "Tacview" return options.plugins.Tacview.tacviewExportPath ]]) does set the configuration value, but Tacview fails to honor it. It uses the value set in options.lua. If you ever happen to have time on your hands, an option to save the .acmi files relative to lfs.writedir() would be greatly appreciated. Will do.

Totally worth a shot, IMHO. The Pentium only has 6% less single thread rating than my current Ryzen 9 5900X. DCS will only max out a single core and the OS scheduler should be able to manage that, unless its simultaneously transcoding some videos. Should achieve performance roughly comparable to my benchmarks with the 5900X.

In case you don't already use these solutions, I find Open Kneeboard paired with DCS Moving Map as a more than adequate replacement for the spotty implementation of the AMPCD Map. I know it's not great to have to rely on 3rd party stuff, but at this point it's sort of a ED/DCS tradition.

My bad, I was looking at the "base" model equipped with Intel N100, that is a 6W CPU created for mobile/embedded device. Is listed as 1906 points for single thread on that site. The 8505 is definitely better, but since the NAS has their own os, I don't know if it's still a good idea

I encountered the same problem. I tried various methods, including using a VPN, but still couldn't resolve this error

It's the same error that we saw at Hamburg(?) earlier, where changing the beacon number (the suffix after beaconId = 'airfield163_) for some reason fixed all the issues not related to the direct errors in the beacon entries. After fixing the GPs (the "position", "direction" and "positionGeo" entries were shuffled around a bit) but before changing the numbers, only 07R would work, and it was only activated when there was a tailwind! Strange stuff indeed... Replace 'airfield163_0' up to 'airfield163_10' with the following, and you should be good to go (I left the TACAN and NDBs unchanged). I tested all four approaches, and they all work now -- Frankfurt 07L { display_name = _('Frankfurt'); beaconId = 'airfield163_20'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IFM'; frequency = 110700000.000000; position = { -443583.906250, 100.000100, -851177.812500 }; direction = -100.841391; positionGeo = { latitude = 50.047996, longitude = 8.598907 }; sceneObjects = {'t:73852303'}; chartOffsetX = 4593.000000; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_21'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IFM'; frequency = 110700000.000000; position = { -444432.531250, 100.000100, -855199.875000 }; direction = -97.789731; positionGeo = { latitude = 50.034575, longitude = 8.546010 }; sceneObjects = {'t:212951504'}; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_2'; type = BEACON_TYPE_AIRPORT_HOMER; callsign = 'FR'; frequency = 297000.000000; position = { -442648.875000, 128.143317, -844779.937500 }; direction = -101.576053; positionGeo = { latitude = 50.065653, longitude = 8.684068 }; sceneObjects = {'t:73862380'}; }; -- Frankfurt 07R { display_name = _('Frankfurt'); beaconId = 'airfield163_23'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'DLF'; frequency = 109500000.000000; position = { -445032.750000, 100.000100, -855591.500000 }; direction = -99.485803; positionGeo = { latitude = 50.028721, longitude = 8.542056 }; sceneObjects = {'t:212951505'}; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_24'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'DLF'; frequency = 109500000.000000; position = { -444262.406250, 100.000100, -851914.812500 }; direction = -100.825012; positionGeo = { latitude = 50.040944, longitude = 8.590415 }; sceneObjects = {'t:73852304'}; chartOffsetX = 4222.000000; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_5'; type = BEACON_TYPE_AIRPORT_HOMER; callsign = 'FW'; frequency = 382000.000000; position = { -445875.125000, 90.751128, -863257.500000 }; direction = -118.128176; positionGeo = { latitude = 50.009882, longitude = 8.439541 }; sceneObjects = {'t:73828942'}; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_6'; type = BEACON_TYPE_TACAN; callsign = 'FFM'; frequency = 114200000.000000; channel = 89; position = { -443403.843750, 118.535061, -848339.000000 }; direction = -12.414079; positionGeo = { latitude = 50.053775, longitude = 8.637223 }; sceneObjects = {'t:214106112'}; }; -- Frankfurt 25R { display_name = _('Frankfurt'); beaconId = 'airfield163_27'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'RHM'; frequency = 110100000.000000; position = { -443643.500000, 100.000100, -851917.625000 }; direction = 78.659737; positionGeo = { latitude = 50.046376, longitude = 8.588953 }; sceneObjects = {'t:214099125'}; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_28'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'RHM'; frequency = 110100000.000000; position = { -444506.750000, 100.000100, -855987.625000 }; direction = 79.143587; positionGeo = { latitude = 50.032752, longitude = 8.535441 }; sceneObjects = {'t:73846094'}; chartOffsetX = 4591.000000; }; -- Frankfurt 25L { display_name = _('Frankfurt'); beaconId = 'airfield163_29'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IRF'; frequency = 111100000.000000; position = { -445112.812500, 100.000100, -856363.250000 }; direction = 79.197218; positionGeo = { latitude = 50.026870, longitude = 8.531721 }; sceneObjects = {'t:73835198'}; chartOffsetX = 4222.000000; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_30'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IRF'; frequency = 111100000.000000; position = { -444321.468750, 100.000100, -852673.437500 }; direction = 81.530957; positionGeo = { latitude = 50.039301, longitude = 8.580205 }; sceneObjects = {'t:214090990'}; };

Thanks for your reply. I tried renaming options.lua. No joy. Any other suggestions? (I had high hopes for that idea).

I'm having a blast so far, i really like the realism of long flights to the target area and orbiting providing overwatch and the potential for retasking mid mission it adds a lot to the immersion. My only complaint is that the comms are really hard to understand and hear. Most of the time i find myself pausing and reading through message history to figure out what is happening

The brakes seem plenty powerful to me. And regardless, in a real plane, if you were moving at running pace, it only takes a little bit of differential brake for the tail to swing to the side, after which it would continue due to momentum without any braking. The issue seems to arise from friction. It acts as if it has a wooden skid instead of a tailwheel… Or as if the tail wheel is not castering and only turns if you can get the tail tire to skid a across the the pavement by using excessive power and differential braking. (As an aside, I don’t think the rudder is playing a part in the turning problem being discussed here. At slow speeds, with zero wind, and with no prop blast, the rudder doesn’t contribute much to initiating or stopping a swinging turn. The video of the corsair turning with the engine off shows the rudder turned, but it’s not because it was necessary for the turn. It turned because the differential braking is accomplished by pushing the top of the rudder pedal, which is easier to do with the rudder pedal bottomed out) If the tailwheel is in reality a stick that touches the ground, do you think that it’s possible to solve this by changing the “friction value” of the stick?

Holy smokes... 100+ thousand feet, sustained. Just tested real quick the 31K variant, nice work! Steering on the ground is a bit wonky. There is some small white noise during the afterbuner sound, sometimes. Other than that seems pretty cool

Well, SP dwarves MP, so I assume SP wants it more than MP. Sent from my SM-A536B using Tapatalk

That look like the all seing eye when "game mode" or something is enabled in the settings. Sent from my SM-A536B using Tapatalk

Almost as my FFB2 then. Except. That one has a firmware deadzone, which makes it really sloppy, and it's very noticeable, while it makes AAR somewhat daunting. Hovering in helicopters not so much, as you don't really move around in the center. If movement is still registered on the Moza, (have you checked for raw values in the VPC control panel or dbview or similar?), I'm positive it could be fixed with firmware. As I'm sure it could be with my FFB2. There it's very noticeable that there is no resistance when you move around in the deadzone.

OK Rudel, thank you very much. I have a small suggestion, It would be nice if one could fold away the mirrors just with "one mouse click" over them, as most DCS planes do, instead of "click and drag mouse" or "click and mouse wheel turn" as it is the case now in the Corsair.