-
Posts
166 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by deltatango
-
why am i doing this smashing rotors
deltatango replied to Ed Hunter's topic in DCS: Ka-50 Black Shark
I feel your pain I've been here and been through this before. http://forums.eagle.ru/showthread.php?t=42374 I feel your pain -
Are you using the Saitek X52 with an SST profile for DCS? If so, what type of key stroke have you set for weapons release? simple, advanced or macro command?
-
Ok after reading Pogo's first post in this thread and all the FAQ posts, etc elswhere in the forum and the flight manuals and readme files and the rest of this thread: I still don't understand the logic of the trimmer in the helicopter! This is why: 1. An aircraft (especially a helicopter) with simple hydraulic/mechanical flight controls can be unstable and require many inputs to the flight controls to get it to fly in the desired flightpath (or change flightpath) that the pilot wants. This can only be relieved by 2. So, to relieve the pilot and make the aircraft easier to control and electronic flight control system (FCS) can be incorporated into the aircraft. This changes the way the controls are operated (subtly, but importantly), so that manipulation of the flight controls produces the desired changes in flightpath. So, for example, moving the anti-torque pedals to the right, makes the aircraft yaw to the right a corresponding amount (the amount is adjusted by the FCS, depending on the airspeed and a heap of other parameters) and leaving them centred keeps the yaw rate zero. In the background, the FCS computer is adding a HEAP of extra control inputs to the flight controls, that the pilot is blissfully unaware of. Without that, he would have to make those him/herself. 3. Ok we all understand that, *BUT*, the very bizarre (IMHO) FCS of the Blackshark omits the second part of the FCS regime. That is, it will keep the helicopter steady on the current flightpath (or rate of change of flightpath), but it will FIGHT any attempt by the pilot to change the flight path by introducing control inputs. Again - to me - this BIZARRE. Flying it is like flying something attached to a giant rubber band. You make a control input and when you release it, the aircraft goes back to what it was doing before you made the input. You have to actually press a button before it wil let you make an input. So as a comparison. In a modern helicopter (EG an EH101 Merlin) if you are in a hover and you add some pedal for 2 sec, then centre the pedals, the helicopter will yaw left, then stop and hover in the new direction. In the Blackshark, if you are in a hover and add some pedal for 2 sec, the helicopter will begin to turn. When you release the pedal input, the helicopter will snap back to the heading it was holding before. Like it is attached to some big rubber band! 4. So to summarise. A "normal" FCS works like this: New Flightpath = (current flightpath + pilot inputs) - inputs by torque, wind and other aerodynamic forces. The bizzaro Blackshark flight control logic works like this: New Flightpath = (current flightpath + pilot inputs - pilot inputs) - inputs by torque, wind and other aerodynamic forces. Yes I understand how to fly it and yes I can fly it, by I will never understand why it is designed like this.
-
Most idiotic thing you've done in BS
deltatango replied to wickedpenguin's topic in DCS: Ka-50 Black Shark
Wingy calls "Bandit!", so I break off my attack on the tank column to look for bandit. Oh, it's an A-10. Haven't seen one of those on DCS:BS campaign before. So I try to maneuver to get SHKVAL lock. Jeez this is hard to do with a jet. Oh wait, he's stopped moving. Oh, getting bigger now in SHKVAL. Just adjust the SHKVAL gate a bit, turn a bit, just getting ready to fire. Oh my, he's getting bigger in the SHKVAL now. Almost filling the display now. Wait, what's that sparkly thing under his no............................... -
How to attack targets while moving forward ?
deltatango replied to repsol's topic in DCS: Ka-50 Black Shark
Tactics I use successfully in Campaigns -Track toward target using waypoint mode -after you have passed closest waypoint to target (make sure waypoint is still >11km from enemy front line), change to target mode and select first TP that is your mission goal (usually TP1). -Turn on turn to target mode and hit uncage button on cyclic. SHKVAL will slew to target point and helicopter will turn towards target. -Ground speed should be <150. Altitude low as possible to get line of sight on target. -Slew SHKVAL around to acquire target and lock. Laser range finder should already be on. Master arm on, select ATGMs. -Close to Rmax. Fire as soon as you reach Rmax. -While missile is in the air, slow to a hover maintaining same altitude. Be careful not to balloon and or enter Vortex ring as you approach the hover. While you are doing this monitor the missile. -After impact slew to next target (there are usualy numerous targets near each TP), lock and fire. Rinse and repeat. -Don't get any closer than just inside Rmax, until all SAMS, MANPADS, AAA and MBTs are dealt with. -Get you wingy to target air defences. -After attack complete, re-assess you position and possible threats (have you drifted into enemy territory?) -Change to next TP. If necessary, reset SHKVAL (Backspace) and uncage again to slew to next TP. -Make sure you don't have to fly across enemy positions to get to next TP. You may have to fly back towards to your lines, before turning again to next TP. -Throughout this, don't be afraid to use your wingman to attack targets, cover you, or conduct recon, but remember - he is STUPID STUPID STUPID and he will fly right over air defences. Once he is gone, you don't get another one and you may need his ordnance to complete a mission successfully. Criteria for breakaway. >>>This is the bit that is gonna save your a$$<<<< If you encounter any of the following situations break off attack and re-assess. You may need to to do an immediate 180 deg turn to get to safety, or avoid traveling further into other danger zones while dealing with the first threat: -Your wingy calls bandit. Order him to attack bandit. Break off attack if bandit is hostile (ie not a UH-60, MH-53, etc) and/or wingy can't deal with it. -You get an "under attack" warning from your laser warning kit. Immediate 180 degree turn and re-assess. -Your wingy calls Missile launch. Immediate Flares. Look for missile and turn 90 degrees to missile. Continue to maneuver until missile is evaded, then turn way from launch site, as another one is sure to follow. If possible, make a note of the location of the launch site, and teach them a lesson (from a safe distance) for daring to shoot at you. -Tracers flying past your field of view/pinging off your hull. Immediate turn away and dive to get terrain shielding, if available. Retreat to stand off range and teach as per SAM site. REMEMBER: The most dangerous situation is when you find yourself SURROUNDED by other defences and threats after evading the first one. Try to remain on the edge of the threat area and take little bites off it. This may be unavoidable if you are striking a target deep within enemy territory.If there are multiple threats along your flightpath, you may need to change you path to the left or right and probe a bit along a new flight path. Feel your way in slowly, using terrain shielding where possible. This was written from lessons learned the hard way in DCS and other classic sims (F4.0, LOMAC, etc). The advantage you have in Blackshark, is that you can't feel your way along SLOWLY and not end up in a real mess -real quick - thanks to your super fast jet. -
Min stated range is 800m. That is REALLY close. I've found in the campaigns, that the best way to engage ALL targets is at max range. Use the TPs preloaded in the PVI to find the target location (see page 6-20 of the manual), hit uncage and the SHKVAL will slew to the target point (I love this feature!). Then manually slew around and lock on. At max range fire the first shot and then slow to a hover. After the first round hits, stabilise in a hover and slew to other targets in the area. If you're getting the 'UNDER ATTACK' warning you're too close. This is the way I have found to succesfully employ VIKHRs in missions without labels on. I might write a full how-to on this based in my 32hrs 26min (and 29 deaths) of lessons learnt so far. I reckon employing VIKHRs well, is the key to this sim. Until I understood how do this well, I got nailed every mission.
-
I get closer to 99% accuracy. Do you have the Laser standby ON/OFF switch to ON? This is right next to the RESET button on the panel just in front of the Engine cut-off valve levers. If not, you'll still get the launch authorised 'C', but range will not be accurate and they'll miss.
-
This mission annoyed me sooo much, I changed it so you start in the air, just above the dam. I also chose unlimited weapons - just for this mission. It's the only way to complete it without your suicidal wingy.
-
But when you play ARMA online, you end up in just that situation. There are numerous ground battles going between players in FPS style. At the same time, other players are flying around in Helos or jets. The experience you get in helos in this situation (WRT draw distance and terrain) is at least as good - or better - than DCS:BS. The same could be said for arcade shooters like the battlefield series -albeit on a smaller map scale. Granted, in a jet, its still too much of an ask to draw far enough ahead for the speed you are going and the ground you cover. It's just that the helo systems and flight model are VERY simplified. So, if someone bothered to (and if it were possible to) improve the Helo systems and flight model in those other games, you could very well have such a world. That would be rather cool...
-
checklist for iphone and ipod touch Hi, Great Checklist! I've just used your data to make an electronic checklist that can be used on iphone or ipod touch. It uses an App called "Aircheck". I've made a few changes in the order that things are done, so the flow of the switch selections is a bit more fluid. You can get the App from the itunes App store here. You can get my checklist for the App from here http://www.airchecklists.com/main Just look for Kamov KA-50. Follow instructions with app for downloading shared checklists.
-
Detailed Startup Checklist w/ Explanatory Notes
deltatango replied to hilikusopus's topic in DCS: Ka-50 Black Shark
checklists for iphone and ipod touch If you have an ipod touch or iphone, there are various checklist Apps available. I've just bought 'Aircheck', for the princely sum of AUD$2.49 (about USD$2.00) which lets you create checklists online and share them. I think I might make one for the KA-50. Stay tuned... EDIT: I've made an electronic checklist, but it's from another person's checklist here http://forums.eagle.ru/showthread.php?p=707713#post707713 Yours is great too. There is just so much great stuff created by members around here! -
It's not a new idea. But it is a good idea. Aeroworx KingAir for MS FS9 http://www.aeroworx.com/b200.html "To add to the realism, the B200 has realistically animated wipers, control surfaces, and an aircraft maintenance module that monitors engine hours, airframe hours, oil usage, tire wear, engine wear, and prop wear. The pilot can replace/repair engines (when damaged by hot-start), props, engine oil, tires, gear and flaps (gear and flaps are damaged if extension/retraction speeds are exceeded) via the maintenance module. " Aerosoft's Dornier DO-27 for MS FSX http://www.flight1.com/products.asp?product=DO-27 "- Panels and instruments may be damaged by hard landings. - All circuit breakers work. - Instruments are affected by flight conditions; the panel may vibrate, instrument needles may be influenced by vibrations, g-forces, or other disorders. - Engine and gear can get damaged by a number of factors. - The flight model is affected by a number of different conditions - so it means you must pay attention in Pro mode. - Structure and controls can get damaged through high speeds and extreme maneuvers. - Windows get dirty."
-
Found this thread after getting the same problem in deployment campaign. Nailed the 'Back to Teberda' mission, but failed in the next mission after my AS (Artificial Stupidity) wingy flew right over the top of the town we were attacking and got shot down, leaving me with not enough weapons to complete it. So when I went to try it again, I am back to the "Back to Teberda" mission. If this is not a bug, it's a very annoying 'feature' of the campaign engine.
-
A-10C simulator used by Air Force - is this the DCS Hog?
deltatango replied to gillers's topic in DCS: Ka-50 Black Shark
No, I think that is the new really bad haircut simulator (RBHCS). Lt Col Brown is simulating an extremely bad one! -
Saitek has a poll going over at their forums on who would be interested in FF HOTAS setups. http://www.saitekforum.com/showthread.php?t=11746 That's from 2007. Guess they missed the boat....
-
Hey! I have a suncom HOTAS collecting dust in my garage. Sitting next to it is a Saitek X45. I am thinking of transplanting the guts from the X45 into the Suncom (which doesn't work and has a Gameport connection). hmmm...
-
Ok, I've uploaded a TRK file. It's recorded in the same location that I had the problem with left turn before. Its shows a couple of left and right turns, before the blades meet in a nose up manueuvre. It was recorded with TrackIR and I have noticed that if you manually change the view, it doesn't come back to the right spot in the cockpit. What would be good is some kind of graph in the Flight manual that shows areas of the flight envelope to be avoided. The graph would show airspeed vs altitude or collective position. Because there must be parts of the flight envelope where full or at least high collective settings can be used. This links shows such a chart for a KingAir (U-21G) http://www.tpub.com/content/aviationmaintandmisc/TM-55-1510-215-10/TM-55-1510-215-100159.htm Although this one is for a fixed wing aircraft, similar charts exist for all rotary wing aircraft, usually to show the 'deadman's curve' - an area which recovery from autorotation is not possible. high alt crash.trk
-
That 11.5 was about a second after the BANG, when I had the presence of mind to hit PAUSE. So the engine power indicators were also indicating zero at that time. I don't know if the blade angle would have also instantly changed in response to the blades being all of a sudden half their original length.
-
Yep. On the Rotor RPM gauge near the landing gear indicator lights. So 98% = between the two red lines on the gauge. No. I always have the throttles to auto. I have them mapped to 2 axes on my Saitek Pro Throttle quadrant (I use an X52 pro for the collective). I will post a track soon.
-
it's still doin' it Ok, I've just successfully completed the epic campaign mission that involves flying over the snowy mountains to take out enemy supply depot (artillery and cargo) and then flying back. As I was climbing away from the target area on the way home - BANG. Blades julienne... I immediately paused the sim to take down the parameters, which were: -Climbing LEFT turn. Not aggressive. -High collective setting (at upper detent on Saitek X52 Pro) -Airspeed 200km/hr (no warning tones heard) -Groundspeed (in HUD) +251 -Altitude 2797m -Nr ~98% (no warning tones heard) -Blade angle 11.5 -Fuel Aft 3.2, Fwd 3.8. No bullets, no Vikrs, about half S-8s fired. -Pitch, Bank & Heading buttons engaged. FD AP disengaged. Route mode not engaged. So why is it still doing it?
-
test results. Ok after extensive (well 20 minutes and about 25 flights) the results are in: -Flights conducted with full fuel, Vikrs outboard and S-8s inboard. Altitude sea level to 1000m. -As mentioned above, right turns are the danger. -A right turn with low rotor rpm (anywhere < 85%) will cause the blades to clip every time. Scenarios that cause this. 1. High speed right turn with collective in same position as cruise. So if you are crusing along near Vne and you break right: BANG. 2.Any sharp right turn, anywhere from hover to Vne, while pulling max (or just high) collective, especially if it results in the low rotor RPM warning going off. At higher speeds just right cyclic will do it, but as the speed decreases, added right pedal helps the blades meet. This exactly what you do anyway. Ie: low speed maneuvers require more pedal. More pedal and less right cyclic will also do it. 3. A right turn during a descent, as you are leveling off (and so pulling on more collective). An example of this is when you descend towards a valley floor, then level off and turn to follow the valley. You must keep your rate of descent low to avoid low rpm. This can be a problem if the valley walls are steep and you are flying NOE. Vortex ring is not a problem if you have forward speed. EDIT: I forgot to mention about the Flare dispenser. By default, flares are dispensed from the left side only. So a couple of times when I have seen a missile launch, I have dumped flares and Broken right (away from the flare). I was wondering how I still got hit so quickly. Of course this was the blades hitting - not me getting hit by the missile. So from now on, I shall set the flare dispenser to the right side first and break left. cheers, DT
-
No, That's what I'm saying. There was NO warnings and NO limits exceeded. No high G, High roll rate or high alpha-dot. It just broke. As someone else was saying, the blades do come awfully close on the right side in high speed cruise. I took a coupla screens during one mission that show my blades doing this, but my 3xAI flight member's blades were parallel. As someones else said - the AI seem to cheat a little. Maybe this was what happened to me. Is there any warnings in the flight manual that advise against certain parts of the flight envelope? I'm off to do some test flying to see if I can replicate the problem reliably. I'll report back findings...
-
I am getting [seemingly] random crashing of the helicopter. One minute I'm flying along happily, the next minute - BANG! An explosion, followed by uncontrollable roll and soon after, a crash into the ground. I've checked that nothing is around to shoot at me and a couple of times, I paused it after the bang, for a look at the outside. All I see is the Rotor blades seem to be half their original length. I thought I might have been overstressing the aircraft, as the first time it happened, I had been following the other chopper on the Campaign mission #1 for ages and doing heaps of overspeed and rotor RPM warnings. But it has since happened without ever exceeding any limits. Any ideas?
-
logbook = Falchon 4.0? Is it just me, or does the BS logbook feel a lot like the Falcon 4.0 logbook? Without going to the bother of re-installing F4, I reckon even the default picture is the same one! This is good though, as F4 had the best logbook to date.
-
Any chance you could change the download hyperlinks on the website so download managers (I use getright) can be used for downloads. I am currently unable to get getright to capture the d/l. Even though I have broadband, I still like to set up a few downloads before I go to bed and have the computer shut down when finished. Alternatively, does anyone know how to make getright (ver 4.5d) work with the current system? Note, I don't want to install another d/l manager as this one works fine with 99% of all other sites and I know it shas no spyware, etc. Yeah I know. I'm nitpicking...