All Activity

Had no idea… Many thanks for the .zip

Thanks! Original post updated with this info!

Nothing like playing the whole mission through, then after refueling and sitting happy off the tanker's right wing, lead breaks HARD right after fuelling, straight into me. Boom, done. 2 hours down the drain. After fuelling is it just fly back to the ship and land? Anything else I'm missing if I just skip? Really don't want to fly the whole thing again... On a side note, maybe a suggestion, can we make the player immortal during certain phases (primarily when we're expected to fly form off such an unpredictable AI?) Those sudden breaks that AI makes are just too damn unpredictable (not to mention unrealistic)...

Is there any way to get some of turbo mode working for SteamVR? The OpenXR toolkit obviously won't work. This is the best headset I've used for DCS, but I have more microstutters than the Quest because I can't use it.

У кота очень ободраная кабина.

I do not know where the Tail number from the Mi-8 have gone.

The F-16 Early Access Guide Page 465 defines the small circle on the DLZ as the Radar Activation Range: However, as of DCS 2.9.19.13478 that small circle is now located above the current range caret although missile activation is still 50 seconds away. Documentation and actual implementation are inconsistent. From the looks of the documentation screenshot, the docs may be in need of an update. Track file from which the screenshot was taken: F16_DLZ_Radar_Activation_Range.trk

i don't know how to get the track from multiplayer mode! It literally just happened to me again.

So, I just have to ask, why wasn't the radar ever updated by most end users? If I understand correctly, the F-4J and S got a pulse doppler radar. But the F-4B,C,D,E,F,G, and N, other than those few later updated with modern radar by foreign users, did not get any updates. As a side note, I understand the B,C,D, and N had a different radar than the APQ-120 but other than perhaps longer range due to the bigger dish I understand it to be quite similar? I have no idea what the British F-4K/M had. Seems kinda odd to me though as the radar is the one part of the jet that, at times, really seems to be lacking and hasn't been improved by the time of our E model.

UPDATE: Refined this, to precisely match the Options/System/External Field of View = 55°. Found that the [1] 'snap view' (keypad "0") could be re-tasked to an Instrument Panel "Look in/back" from a off-axis panned view. Really handy both fighting and landing, for a quick check of the gauges. Noticed this view was a little off of the 55° Ext. FoV setting, though always very different from the [13] 'default view', and figured that since they were on different scales, the 'snap view' was probable the same as the External. So, set the [1] 'snap view' to 55°, and then readjusted the [13] 'default view' by selecting the 'Panel View' w/ the control stick button, and then (keypad "0") snapping back and forth to it, looking for anomalies. Wiggled it into a perfect match, which is a little wider than the original "40", which is good for FoV, but not enough to create an unwanted effect. Win/Win. SnapViews["P-51D"] = { [1] = {-- player slot 1 [1] = {--LWin + Num0 : Snap View 0 viewAngle = 55.000000,--FOV Cockpit Zoom 55.000000, OEM 80.000000 "P-51D" viewAngleVertical= 0.000000,--VFOV hAngle = 0.000000,-- (Snap View)/(Cockpit panel view in)(-30°) vAngle = -30.00000,-- Cockpit View Angle -30.00000, OEM -9.500000 x_trans = 0.160000,-- Cockpit View In_Trans 0.160000. 0.150000, OEM 0.120000 y_trans = 0.060000,-- Cockpit View Up_Trans 0.060000, OEM 0.059000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, [13] = {--default view viewAngle = 40.200000,--FOV Cockpit Zoom 40.200000, OEM 80.000000 "P-51D" viewAngleVertical= 0.000000,--VFOV hAngle = 0.000000,-- (View Center)/(Cam View Dn-Slow)(-30°) vAngle = 0.000000,-- Cockpit View Angle 0.00000, OEM -9.500000 x_trans = 0.160000,-- Cockpit View In_Trans 0.160000, 0.150000, OEM 0.120000 y_trans = 0.060000,-- Cockpit View Up_Trans 0.060000, OEM 0.059000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, Enjoy. Bowie

My BUK-M3 site is tracking target, but not firing. How can I fix it?

Thank you. . That was kinda obvious, now I feel stupid…. But nevertheless it worked. Piece of cake actually.

I'll fix this in the next update. There was another preset that had the same issue.

yes sure, any additional costs will be passed on to the user

Ну да, с нашлемкой лажа какая то ))

Its 2 seperate things. See the video of the real life corsair few pages back that makes a 180 deg turn. Idle engine, and then turns on the spot. In the DCS Corsair you can do a 180 turn, but you need excessive power to do so, compared to the RL example, that does it with a cut engine, having enough momentum. You can do it in any other warbird aswell. But not in the DCS Corsair. The wheels are sort of "skiddy" for lack of better words. The wind is another factor, that one it goes above 10 m/s its impossible to steer her past 90 deg of wind direction. Which also, the other warbirds have no issue with. It is two seperate things, but it renders in impossible ground handling. With zero wind its possible, but not correct. With stronger winds, its impossible.

Does it really work well, last night we tried it again 8 user, 5 with issue of not being able to hear players on the same radio frequency, not being able to talk, its still broken for us so we will try again in another year.

Curious if this was still available? The link seemed to be dead. Or does anyone know of another mod to add these as static objects for Kola?

Dear ED teams, I have seen recently a post regarding incorrect mass after recent API update. I took the liberty to further dig into the subject after being hit by shots in HOJ mode by F-4 with Aim-7F. The F-4 was notching at 90-110° (so no lock on me) and I still got hit without RWR warning. Track is 90 Mb, so I can share with separate file if needed. My understanding is that irl HOJ (without aircraft guidance) is functional on -MH and -P versions only. But it seems -F and -M are equipped with HOJ also. I looked into the file "aim7_family.lua" and found the line "hoj = 1" for all these versions. I guess this explains it. By doing comparison on data (I tried to reverse engineer to understand, but I don't to be honest), I also found differences on other parameters. On versions -M and -MH, there are parameters set as "sensors", with height error lower than on "seekers" parameters. I assume these are for shorter distance, with better guidance or proximity fuse. The "sensors" parameters do not exist for the -P. Also, same reasoning for paramerters such as "gimbal" and "ap", they are not there for the -P. So I guess missile -P has a default behavior for these missing parameters, and thus behaves worse than -M and -MH in specific areas. Areas that I don't know about. I am not sure if all this is correct, nor do I know if that is realistic. But I saw it, so I thought I could raise it and maybe help to fine tune the missiles without too much workload, that is: removing hoj for -F and -M, and adding the missing parameters for -P. If that is indeed correct. Thank you very much in advance for taking care of Fox-1, many cold war enthousiasts like me appreciate it very much. JAR. Example Aim-7 M sensor = { delay = 0, op_time = 80, FOV = math.rad(12), sens_near_dist = 100, sens_far_dist = 60000, ccm_k0 = 0.2, aim_sigma = 4.0, height_error_k = 25, height_error_max_vel = 60, height_error_max_h = 300, hoj = 1, }, seeker = { delay = 0.6, op_time = 75, FOV = math.rad(120), max_w_LOS = math.rad(20), sens_near_dist = 100, sens_far_dist = 30000, ccm_k0 = 1.0, aim_sigma = 5.5, height_error_k = 100, height_error_max_vel = 138, height_error_max_h = 300, hoj = 1, }, aim7_family.lua

I can’t manually start/shut down the jet so am I a bit screwed for this mission?

So... Moved the 'eyeball' back 0.02 (x_trans = -0.020000,-- 0.000000), which is about as far, until the canopy shield gets unrealistically intrusive. Somewhat of an improvement. Bowie

Just enable the dlls overlay at dlss swapper options and you will see the version thait is running in this moment, with the preset and the scale

ok, see your problem. Your first entry in the Advanced (Waypoint Actions) table is FAC -a. This is an enroute Task where the FAC looks freely for targets and he has chosen the target with above coordinates. Your FAC - Assign Group("Ground 1 ") command is number 5 in the list. If you want the FAC only assign the "Ground 1" you have to delete the first entry, the FAC -a

hello, as is always the case, please post your dcs.log. also do you have exceptions in your AV software for the DCS install folder and the DCS folder in Saved Games?

LOL!! I was just coming here to ask about this!! Sad to lose my daytime AN/AVS-7 HUD, but I guess I will survive