Lascaille

OK this seems not to work. The DCS editor shows the buttons as bound but only one function is activated.

Teej, I had a thought. I've found multiple controls mapped to the same button within the DCS editor after upgrades - i.e. the DCS 'edit controls' window shows the same joy button bound to multiple actions. You can't create that scenario in the DCS editor but it does display it, therefore it's not erroring out immediately. Is it possible/easier just to edit the saved input configuration files directly, adding the same button to multiple actions? That would also avoid integrity check issues.

This is honestly one of the best threads I've ever seen. No attitude, just incredible advice. Need to set up some multiple actions myself (I want the wheelbrakes and weapon drop combined on the warthog paddle switch for some aircraft) and will get into it. Huge thanks.

All, please consider: Radar modelling within DCS, from what I have read, is not based on radar theory. The radar system works on the position, aspect, size and speed of the objects - basically it's like a passive system, it relies on being able to 'see' the object, presumably there is a master 'object array (array as in programming terms)' which defines the position, speed, aspect, type etc of all objects in the game and the relevant countermeasure/radar code for each module consults this array when deciding what to display to the user. I am not sure how much of this is abstracted by DCS or if DCS just exposes a list of objects and the developer can do their own work. With that in mind there are no 'radar waves' in DCS being generated by the aggressor to be received by the SPO-10 code. So the SPO-10 code has access to the same 'object array' as any other radar/countermeasure code object, so it can see which objects are at which distance, and whether they are emitting, whether they are facing towards/away, etc. LN do not control modules aside from their own, so I guess they have to give their SPO-10 a list of modules (aircraft, SAMs, etc) and an effectiveness (range) value depending on the modernity, etc of each unit. The SPO-10 code then does a calculation: how distant is the object, is it facing me, what is the altitude, is it emitting, is it behind terrain and decides whether to alert. This is my conjecture but from all the reading I have been doing this is fairly accurate as to how radar within DCS works. It is not a simulation of radar, it is a system designed to allow radars to be functional in game. So, you are not going to find in any manual anywhere details about the real world effectiveness of the SPO-10. 'Detects radar emissions up to 20km' or something maybe, but versus specific radars, including more modern ones designed long after the SPO-10 was last in production? No chance. So I believe you have to accept that any modelling of the performance of the SPO-10 - beyond the behaviours exposed in the manual, i.e. the manner in which the lights flash, the beep patterns - will be original research / original fiction. Of course if anyone has more details about how things _actually_ work in game - if I am wrong - I would be interested. Maybe we can come up with some potential ideas to improve, in that case? Not just 'make it better' but a different way to model the system.

Track attached for anyone who's interested. Note there's no actual kill, the Magic II didn't lock in time. I had the target well within the seeker window though with the airframe under control. Can you use the radar to guide the seeker head? Rearward Missile.trk

Thanks B

The first person to die to this is going to be SO butthurt they'll probably develop haemorrhoids. [ame] [/ame]

Just got the Mirage which is behaving very nicely, congrats to RAZBAM on a great release. I'm sure I'm not the only person to notice how different the viewpoint/angle is from other DCS mods. I made changes in the views.lua (mods\aircraft\m-2000c\views.lua) and provide it here as a starting point for anyone who has a similar feeling. This gives a similar cockpit feel to the A10C - which I think is itself a bit more zoomed in and 'up front' than the FC3 mods - and reduces (to zero) the eyepoint/pivotpoint differential thus reducing viewpoint position shift with trackir pitch/roll (so when you look down, you will no longer feel like your head is moving down also). ViewSettings = { Cockpit = { [1] = {-- player slot 1 CockpitLocalPoint = {0.00,0.000,0.000}, CameraViewAngleLimits = {20.0000,140.0000}, CameraAngleRestriction = {false,90.000000,0.500000}, CameraAngleLimits = {200,-90.000000,90.000000}, EyePoint = {0.000000,0.000000,0.000000}, ShoulderSize = 0.25, Allow360rotation = false, limits_6DOF = {x = {-0.050000,0.450000},y ={-0.100000,0.100000},z = {-0.30000,0.30000},roll = 90.000000}, }, }, -- Cockpit Chase = { LocalPoint = {-10.0,1.0,3.0}, AnglesDefault = {0.000000, 0.000000}, }, -- Chase Arcade = { LocalPoint = {-21.500000,6.618000,0.000000}, AnglesDefault = {0.000000,-8.000000}, }, -- Arcade } SnapViews = { [1] = {-- player slot 1 [1] = {--LWin + Num0 : Snap View 0 viewAngle = 48.000000,--FOV hAngle = 0.000000, vAngle = -45.000000, x_trans = 0.120000, y_trans = 0.020000, z_trans = 0.000000, rollAngle = 0.000000, }, [2] = {--LWin + Num1 : Snap View 1 viewAngle = 48.000000,--FOV hAngle = 45.000000, vAngle = -45.000000, x_trans = 0.120000, y_trans = 0.020000, z_trans = 0.000000, rollAngle = 0.000000, }, [3] = {--LWin + Num2 : Snap View 2 viewAngle = 48.000000,--FOV hAngle = 0.000000, vAngle = -75.000000, x_trans = 0.120000, y_trans = 0.020000, z_trans = 0.000000, rollAngle = 0.000000, }, [4] = {--LWin + Num3 : Snap View 3 viewAngle = 48.000000,--FOV hAngle = -45.000000, vAngle = -45.000000, x_trans = 0.120000, y_trans = 0.020000, z_trans = 0.000000, rollAngle = 0.000000, }, [5] = {--LWin + Num4 : Snap View 4 viewAngle = 91.040001,--FOV hAngle = 157.332764, vAngle = -28.359503, x_trans = 0.063872, y_trans = 0.082888, z_trans = -0.116148, rollAngle = 0.000000, }, [6] = {--LWin + Num5 : Snap View 5 viewAngle = 50.000000,--FOV hAngle = 0.000000, vAngle = -8.722581, x_trans = 0.212078, y_trans = 0.057813, z_trans = 0.000000, rollAngle = 0.000000, }, [7] = {--LWin + Num6 : Snap View 6 viewAngle = 80.000000,--FOV hAngle = -143.000000, vAngle = 0.000000, x_trans = 0.350000, y_trans = 0.020000, z_trans = 0.100000, rollAngle = 0.000000, }, [8] = {--LWin + Num7 : Snap View 7 viewAngle = 80.000000,--FOV hAngle = 45.000000, vAngle = -5.000000, x_trans = 0.120000, y_trans = 0.020000, z_trans = 0.000000, rollAngle = 0.000000, }, [9] = {--LWin + Num8 : Snap View 8 viewAngle = 80.000000,--FOV hAngle = 0.000000, vAngle = 10.000000, x_trans = 0.120000, y_trans = 0.020000, z_trans = 0.000000, rollAngle = 0.000000, }, [10] = {--LWin + Num9 : Snap View 9 viewAngle = 80.000000,--FOV hAngle = -45.000000, vAngle = -5.000000, x_trans = 0.120000, y_trans = 0.020000, z_trans = 0.000000, rollAngle = 0.000000, }, [11] = {--look at left mirror viewAngle = 80.000000,--FOV hAngle = 0.000000, vAngle = 10.000000, x_trans = 0.120000, y_trans = 0.020000, z_trans = 0.000000, rollAngle = 0.000000, }, [12] = {--look at right mirror viewAngle = 80.000000,--FOV hAngle = -20.000000, vAngle = 8.000000, x_trans = 0.120000, y_trans = 0.020000, z_trans = 0.000000, rollAngle = 0.000000, }, [13] = {--default view viewAngle = 71.000000,--FOV hAngle = 0.000000, vAngle = -19.000000, x_trans = 0.000000, y_trans = 0.010000, z_trans = 0.000000, rollAngle = 0.000000, }, }, } Changes: Line 8: EyePoint = {0.000000,0.000000,0.000000}, Line 134: viewAngle = 71.000000,--FOV Line 136: vAngle = -19.000000, Line 138: y_trans = 0.010000, No whining please! I am not complaining about the module, I am just making viewpoint changes for my own familiarity. Don't forget to backup your views.lua!

The Mig-21 has neither trim tabs or a fully moveable tailplane. Therefore trim is effected by changing the neutral position of the elevators themselves. Yes in real life this reduces control authority (adding back trim has the same effect on the control surfaces as pulling the stick back. As the position of the stick directly reflects the position of the control surfaces the stick will move as you trim.

The actual situation seems to be both - if you have the crosswind directly on your right wing (88-92 degrees) wing the aircraft will yaw right _into_ it, but will stabilize at some angle to it. If you have the crosswind barely off the nose (i.e. 2 degrees) the aircraft will yaw right _away_ from it and also end up stable.

So to host 50 players you would need 40Mbit? As in nearly half a 100mbit ethernet connection? I am not doubting you just astonished, I used to do some managed hosting stuff and that would be well over $2k per month for B/W alone. I am going to be selfish asshole here but ask, I am in Asia and see ~225ms to your server. I would like to get back to it once the beta calms down a bit. I understand pings have to be for the benefit of all people but warping that I could see was caused much more by packet loss than simple high ping. If the limit could be set 'considerately' that would be appreciated. No matter what connection I pay for I won't get that ping below 225 due to physics. Also: have you seen any reduction in b/w due to the beta? Or just due to fewer clients?

30m/s is the crosswind limit? What is the headwind limit? I would guess small and light aircraft have limits due to ground handling. If you were to land C172 for example in 50kts headwind (I think you would land at full throttle to achieve positive ground speed) I don't see how you would get it off the runway. Either the wind would blow it straight whenever you tried to turn (that weathercocking effect) or it would turn upside down once the wind to the downwind wing was blocked.

A clarification would be nice. As I said, I measured the bandwidth of my client with WMI and on the 104th I was not seeing more than approx 17.5KBps / 140Kbps / 0.13Mbps down, and less than half of that up. If people do see benefits on their clients from setting huge bitrates - when these observed bitrates are about a 1/10th of the standard limit - then... why?

Crosswind speed limits are because the aircraft has to be brought level and oriented to the runway heading centerline (decrab) before it contacts the runway, or the gear will shear off. With crosswinds greater than a certain amount the aircraft cannot safely decrab without running out of runway width or a wing strike. Headwind: I read what you say but B777 has NO headwind limit for manually flown takeoff and landing! (FYI crosswind limit 37kts, autoland headwind limit 25kts) Tailwind limits are due to various technical limitations, runway length and gear speed limitations. B777 10kts.

There is a need to clarify turbulence vs wind. Turbulence is 'wind within wind' i.e. the air as a whole has a speed of 50kmh at 0 degrees, a small 1m^2 sector of that air might be moving downwards at 20kmh but another sector next to that might be moving upwards at 20kmh. Turbulence ofc will rock the aircraft and can cause it to roll - e.g. if one wing is in an updraft and the other in a downdraft. We are not discussing turbulence, but wind. Wind with zero turbulence (both inside and outside of DCS) involves the entire air mass moving stably as one. In that wind there is NO effect upon the airborne aircraft (yawing, rolling, pitching, no effect at all) because it is impossible, there is no reaction point or pivot point for the aircraft. The wind does not 'blow' on the aircraft, the wind just moves the air and the aircraft just moves inside the air. If there is delta (moving from a region of 50kmh wind to 150kmh wind) there will be inertia forces but that is not the case for this scenario, this involves a static constant global wind.