ekg
-
Posts
256 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by ekg
-
-
How do you evade a p-51 that's on your tail? The AI is easy just start doing scissors and eventually you'll shake him off. In MP it's a different story. It just doesn't work... It also doesn't help that the D-9 loses energy fast. Advice?
-
If the turn is steady state then you bring the gyro sight over the target for a couple seconds then fire. Evasive, not so much, because you never have the steady state you need. In that case all you can really do is wait it out for a better shot, or try to lead and take your chances with a potshot.
You can learn to lead the gyro sight and take shots without using the stabilized method, but if you want it to work as it's supposed to, you need to be steady.
And yes, the modern ccip sights are much better because you can hit your target without the sight ever really settling in on it. It's easy enough aim in front of a target and wait for them to pass under your sight.
This leads me to wonder what is the speed of the rounds coming off the Dora? That would likely give a good indication for the minimum to wait before firing when in a "steady" on the bandit's tail.
-
Oh it does, that's the whole point of the gyro sight! You set the target wingspan, then adjust the range to fit the target inside the pipper, aim so the pipper is right on target, and pull the trigger!
The problems with gyro sight are a) your range estimation can easily be a bit wrong because you do it visually, resulting in wrong lead. b) you need a stable target. if the target is constantly rolling and switching directions the gyro reacts too slow and cannot calculate proper lead.
If the target is evasive and the gyro gunsight over the target will result in a miss I wouldn't call it a firing solution.
-
To use the gyro you have to keep your target in the sight for a couple seconds before pulling the trigger.
Would that still be true in a turn fight or an evasive target in a dog fight? I think you'd have to lead even with gyro.
-
If you guys are having problems using your gyro, you need to use it more. There's nothing wrong with not using it, however, the gyro works just fine.
You still have to lead with your gyro though, right? It doesn't give you a firing solution unlike modern planes with radar lock.
-
Interesting... did real pilots use the gyro at all then?
-
What sort of technique do you use when aiming? I set my wingspan, set my distance to around 100m on and turn on the gyro for my gunsight. I usually have bad aim even when shooting at rear of opponent. Against AI I notice that leading the gunsight usually gets me more hits (usually when merging).
-
left ctrl+tab to chat
-
As the title implies. I would like to see a filter for MP servers. It's a bit annoying to have to scroll through them. An easy one would be by name. Another would be to have filters for types of aircraft available (most don't have WWII planes on them).
Thoughts? I hope devs can implement this.
-
I decided to do a dogfight against AI. It took me some time but I've been able to spot them (although in this track I got the ai to bleed smoke early). Anyways, the plane stalls with what I would think are reasonable inputs. The P-51 flys circles around me the whole time. The most bizarre thing is at the end of the track. Watch for the Airspeed Indicator... What was that fluctuation from 100-300 in less than a second? I'm no expert but that seems strange to me.
Thoughts? Is this a bug?
-
What would be the best curves to use for this plane? I find that in a dogfight against AI I stall / spin out of control frequently. I don't even pull past 50-60% in any direction.
-
-
I've confirmed that the editing the controls in game works. Thanks Nealius!
This still should be fixed however.
-
I tried that it still doesn't work :(
Here is the error in the dcs log after trying this. Looks to be the same issue.
00188.249 ALERT LUACOMMON: Error: GUI Error: [string "./Scripts/Input\Data.lua"]:1591: attempt to index local 'defaultCommand' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./Scripts/Input\Data.lua"]:1591: in function 'getCommandAddedCombos_' [string "./Scripts/Input\Data.lua"]:1647: in function 'getKeyCommandDiff_' [string "./Scripts/Input\Data.lua"]:1666: in function 'getKeyDiffs_' [string "./Scripts/Input\Data.lua"]:1729: in function 'saveDeviceProfile' [string "./Scripts/Input\Data.lua"]:1851: in function 'saveChanges' [string "./MissionEditor/modules/Options\TabViewControls.lua"]:77: in function 'save' [string "./MissionEditor/modules/Options\TabsView.lua"]:141: in function 'onOptionsSaved' [string "./MissionEditor/modules/Options\Controller.lua"]:58: in function 'optionsSaved' [string "./MissionEditor/modules/Options\Data.lua"]:142: in function 'saveChanges' [string "./MissionEditor/modules/me_options.lua"]:72: in function 'onChange' [string "./dxgui/bind/Button.lua"]:22: in function 'callback' [string "./dxgui/bind/Widget.lua"]:310: in function <[string "./dxgui/bind/Widget.lua"]:305>
-
TARGET is scripting for the Warthog. Won't work for Saitek.
Hmm... yeah. I think the proper fix is to made in the module. I have no issues assigning these buttons in the MiG-21bis module.
-
you mean you're setting the control in TARGHET instead of DCS?
-
I have solved with instal Targhet
I don't understand can you explain?
-
What is the target for merging the black sea map and NTTR into a 2.0 beta / release?
Is it going to be spring, late spring summer? I know that there is contingency involved but it would be nice to have some visibility into the status. I bought NTTR a while ago but still haven't played around with it since I don't have space for multiple DCS installs.
-
Has this been recognized as a legitimate issue? I would like a dev to confirm.
-
I'm using x-55 rhino throttle and stick. I'm trying to get Button 1 for airbrake toggle and Button 35 for parachute (both) on the throttle. When I click OK the screen goes dark. There appears to be an error in the LUA scripts based on the dcs log attached. I'm running DCS 1.5 OpenBeta (latest)
The Error:
As a workaround you can try editing the bindings in game (i.e. launch cold start instant action and then when in game modify the settings).
00188.249 ALERT LUACOMMON: Error: GUI Error: [string "./Scripts/Input\Data.lua"]:1591: attempt to index local 'defaultCommand' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./Scripts/Input\Data.lua"]:1591: in function 'getCommandAddedCombos_' [string "./Scripts/Input\Data.lua"]:1647: in function 'getKeyCommandDiff_' [string "./Scripts/Input\Data.lua"]:1666: in function 'getKeyDiffs_' [string "./Scripts/Input\Data.lua"]:1729: in function 'saveDeviceProfile' [string "./Scripts/Input\Data.lua"]:1851: in function 'saveChanges' [string "./MissionEditor/modules/Options\TabViewControls.lua"]:77: in function 'save' [string "./MissionEditor/modules/Options\TabsView.lua"]:141: in function 'onOptionsSaved' [string "./MissionEditor/modules/Options\Controller.lua"]:58: in function 'optionsSaved' [string "./MissionEditor/modules/Options\Data.lua"]:142: in function 'saveChanges' [string "./MissionEditor/modules/me_options.lua"]:72: in function 'onChange' [string "./dxgui/bind/Button.lua"]:22: in function 'callback' [string "./dxgui/bind/Widget.lua"]:310: in function <[string "./dxgui/bind/Widget.lua"]:305>
-
Start letting go of the stick at 100kph. This is very important. If you don't get this right then you will try to take off on a stall. Then your left wing dips and you flip the plane on the runway.
Use rudder inputs to keep straight. The effect of the input is "delayed". I personally use the turn and slip indicators, it works well for me.
-
I'll settle for authentic 80s 4th gen planes on both sides. Seriously I don't care about the bleeding edge since it's basically impossible. I'll take what I can get and am willing to pay for it.
-
If you ask to turn the ground power on, you'll see a small jump in voltage. ?
Are there gauges for voltage? If so I'll have to read the manual a bit more carefully :book:
-
Ground power is off by default for cold starts.
I know the switch in the cockpit is but what about the ground power that is supplied to the plane? You have to contact the ground crew to supply it.
What's odd is that it's turned on in the cockpit before calling the crew. I also found that in the M-2000 and MiG-21 that the crew doesn't do anything special. Am I missing something?
Historically Accurate Skins
in DCS: Fw 190 D-9 Dora
Posted
Sounds like a great idea :) but what is it exactly? Does someone do a search for all user content related to this and make an aggregate set in a zip file?