All Activity

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 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.

Dummy response to mark as solved.

The CPU (Pentium Gold 8505) does have a fairly decent cpubenchmark.net single thread rating of 3272, which is only 36% less than a Core Ultra 9 285K. See CPU comparison. Should do fine for an average mission.

Ordered the Asus ROG Swift OLED PG27UCDM today .. looking forward on how it performs.

During my research I've read a couple of times that people fixed it by upgrading their CPU - the L3 cache seemed to be the issue. I've gladly upgraded to a Ryzen 7 5700X3D with a cache of 96 MB as compared to your (and my previous) 32 MB. That's the only real solution I could find however that hasn't fixed it for me personally. My Afghanistan DLCs haven't been showing up in-game and I've reinstalled them. While they're still not showing up, the issuess with the F-4 have disappeared after that. Maybe it's connected, maybe it's just coincidence.... But yeah. People on the Heatblur Discord were saying the CPU was their issue.

Wow... likes RWR?!

@JMW Check if you have lens effects enabled (and maybe Bloom in VR settings). The recommendation is to have both disabled. @Morat Try DLSS in Performance setting and raise sharpness. Crucial is to have Preset K and DLSS version 310.3 running for a crisp image.

Moza feels great on helis. I will admit. On planes though, especially with my 100mm extension, there's a lot of slop around center where there's virtually no force at all, yet the encoders( or whatever) still register the movements. So you have this area of "free play" where you can still control the plane before and real force ever kicks in. ( not really noticeable on Helis though. Not sure if that's a firmware issue or mechanical design issue. Deadzones aren't the way as the area is more than just " oh its drifting a bit". Its a noticeable lack of force in the center 5-10%. Even with every setting cranked to the max. Feels more like mechanical play to me. Either way I'm happy with the purchase still, but I won't be holding on to it forever. Unless they address that problem before other products hit the market. I'm not opposed to WW hardware, just not a fan of their software. I've become a Virpil fanboy over the years but here in the US almost everything is back ordered and when containers come in, its all spoken for. So you order with the expectation that it will be a few months before you get your item.

I perfectly get that the amount of dev-time is limited and people want different things as, sadly, we simply cannot have it all. Still, as upyr1 pointed out: ED is working on the F-35A - which in turn I have very little interest in - and HB is working on a Eurofighter Typhoon.

none of those sound like the best, when asked "what are the best VR headsets" those don't count because they aren't. If you are looking for the best in a particular category then maybe. If you want small form factor and are willing to give up some fov then probably the bigscreen beyond 2.... if you are looking for standard size with all the features probably the pimax super the Super and BSB2 are often considered the best... categorized or not. Between those two some will say large heavy old style HMDs are dead and that's why they used the BSB2 others are all about wide FOV and large sweet spot and eye tracking then those people will pick the Super. Everything else pretty much becomes best only when when you add category to to. For example "whats the best Vr unit made by playstation" Or whats the "best vr headset that still has screendoor effect" then arguments can be made for those use cases or needs.

Ack i see your point. I guess amongst all the "this doesnt work" posts i missread a thing or two. It appears as if the tires arent tacky enough, or brakes dont have enough bite to do that swing and low speeds. In the rl video he also uses full rudder, so that must also have some sort of effect on the turn and not only by differential braking.