moggel
-
Posts
381 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by moggel
-
-
I'm using a battered old Saitek X52.
Thrustmaster's Warthog is still on the list I send to Santa every year but the fat judgmental bastard still hasn't granted it! :wallbash:
-
Hi,
I've been flying from Creech AFB lately, while training with the A-10C but taking off from RWY 13 I never get clearance from the tower. Here's a scenario that reproduces this every time:
1. Taxi* short of the RWY threshold and ask for T/O clearance.
2. I wait and then try again after aprox. 1 minute.
3. Still no response I try taxiing a bit further so that I end up at the actual threshold (where TWR would be expected to start yelling at me IRL) and request clerance again.
4. Still no response I line up and make a final request.
5. When I still don't get a response I accelerate to take off.
6. Two different outcomes from this:
a. Just silence from the TWR
b. TWR first calls out "unable to clear for takeoff" (don't remember exact wording) and then, after a second or three, I get T/O clearance when already ready to rotate.
* EDIT: This seems to happen when taxiing via Charlie. If I taxi to RWY 13 via Hotel I do get a clearance.
I don't know if this behavior might be linked to a flaw in ATC or in the AFB simulation itself. Also, please bare in mind that I'm a noob and I might have missed a step somewhere so feel free to correct me if that is the case.
-
I'm not the only one without a clue then? :music_whistling:
-
The throttle axis was indeed also bound to rudders but clearing it didn't remove the need to move the stick around before EAC can be engaged.
-
Just wondering about those simulated air defenses. Are they in the Alpha terrain? If so; where are they and can they be employed for practice?
-
When you get started click on the CDU on the right mfd, youll see the align counter going up. If you do it on the ground without rolling it needs to get to 4.0, then you press the osb next to NAV. After that, press the EGI button and your EAC will function properly.
Sent from my SM-N910P using Tapatalk
Could it be that I was too fast? Turning EAC on after takoff worked. I guess that's because I was moving then?
-
The pinky switch on the left throttle needs to be in aft position for the anti-collision lights to work.
That was it. Thanks!
I don't have a Warthog or Rhino HOTAS so all those switches are a bit obscure to me. What's the left pinky used for?
-
As already stated, I'm a noob to the A-10C, currently trying to figure out the system dependencies and function. I've run through the manual start sequence a few times now, in DCS 2.0, Nevada, and there are a few details I just can't figure out:
1. I can't seem to turn on the EAC. The switch moves to the ON position but then immediately toggles back to OFF.
2. When trying to turn on the anti-collision/strobes the switch reacts just like the EAC, and toggles back to OFF
2. Ignoring the above, I've taken off and then noticed that the flight path marker is not presented in the HUD. Can't help suspecting this might somehow be related to problem no. 1 above.
Is there some step I've missed somewhere in the sequence that makes these functions impossible to turn on?
-
I have run this same sequence a few times now and, indeed, the only way I can get the throttles to hop from OFF to IDLE is actually by first moving the stick back and forth a few times. I guess this is not an expected behavior?
-
Suddenly it worked. I have no idea what I did differently. I was sitting in the pit, just seeing if flaps or ailerons reacted to my stick input (which they didn't) with the APU running. Could it be that I just hadn't waited long enough before? The APU *was* at 100% before, when I couldn't get the engines to start but is there something else I need to wait for, like PSI bullding up more or something?
-
No, go into programs/eagle dynamics/open alpha and there is a repair exe
I didn't find a "repair.exe" in that folder (nor in the 'bin' sub folder within). I did try running a command console in the 'bin' sub folder though, and then "dcs_updater repair". I let it run and then tried again but the throttles remain in the OFF position no matter what I do. :huh:
-
The autostart key is RWIN+home not RAlt+home - the latter will move the throttle from off to idle. This does start then engine during the manual startup but you need to perform a couple of steps before that (do at least: battery on, inverter on, fuel pumps on, apu on and wait for 100%rpm)
Also some keyboards offer the option to disable the right windows key, so you may need to rebind the autostart (cheats section) - you should double check that binding anyway.
Edit: Saw that you are using manual startup.
In that case visually check that the throttle is moving from off to idle when you press the shortcut. If it does you're missing some other step before that (track could help). Otherwise check the bindings. Also do you have an axis assigned to the throttle?
My keyboard does not have a RWin. I have double-checked the bindings and also tried to clear and rebind them, as per the following screen shot:
APU is running at 100% before I try it but the throttles remain in the OFF position. Running the exact same sequence in 1.5 does fire up the engines as expected; I only see this in 2.0.
How do I perform a repair? Do I need to uninstall 2.0 completely and then reinstall, or is there a better way?
[EDIT] Not sure why the screen shot isn't working. I added an image with a link to a screen shot that I've uploaded to IMGUR. Using the URI in the browser address field works fine but not as a link here.
-
The A10C is not a FC3 style plane
press lwin or rwin + home to start up or do it manually
I'm starting manually. It's just that the engines won't start up when I press RAlt+Home or RCtrl+Home.
-
I'm a noob, trying to learn the A10C but I just can't crack how to start the engines in 2.0. I've read up on the sequence and tried it without any problems in 1.5 but when I press RAlt+Home (or RCtrl+Home) in DCS 2.0 nothing happens. The throttle gauges remain in the OFF position and the fans doesn't move an inch.
The same startup sequence in 1.5 works fine though. I've double-checked the key bindings and they really are RAlt+Home / RCrttl+Home to ignite engines in both versions.
Is this a bug in 2.0 or is there some additional step they've added that I haven't found out about?
-
That should do it... Check your NAV is configured (EAC, EGI, etc), it should be OK on a training mission.
It was the A-10C navigation training mission so the nav config should be the default (EGI, I think).
Check HUD SOI ("*") Slew, LCtr+down, LCtrl+up long.You can't lock something not on ground (must look down).
Are you saying I can't just put the marker (in HUD or TAD) somewhere in the terrain, such as the bend of a river or a crossroads, and make that a SPI? Do I need to point at a building or a vehicle or something like that?
-
You are making sure that whatever you're trying to make the SPI with is Sensor Of Interest?
I was using the HUD in this case. I slewed little marker to someplace on the ground and tried L.Ctrl+UP (and also TMS-UP long command) but nothing. No marker on the HUD or the TAD. The instruction video never progressed from that point either so I took that as an indication it didn't work.
Is there something else I need to do? Are the commands different depending on the SOI?
-
Hi everyone,
I'm in the progress of learning to fly the A-10C. I was going through the training videos but couldn't get past the section about how to set up a SPI. According to the videos, and what I've seen in other places, the SPI should be set by long-pressing the TMS up key, or L.Ctrl-UP. Neither works. What happens is that the left MFD goes black for half a second but I've seen no other effects.
I assume this is me misunderstanding something, since a search for the issue here at the forums came with nothing. Can anyone please spare a few seconds straightening out this noob? :helpsmilie:
Cheers
-
My latest experiment had me removing the profile all together. I then tried binding the stick's buttons directly in the sim and that works! It means I can't use the X52 MODE feature but I guess I can live with that.
-
I know this is probably a silly question but have you made sure your stick is in the correct mode (1 to 3) ?
Yes, when programming the POVs as buttons my idea was to only support RDR DES in modes 2 and 3. When that failed I allowed all modes and finally I removed buttons programming and set the POV to "unprogrammed" to set it in the sim instead. None of these approaches have worked out.
-
Hi,
I hope your RDR DES are those
It should work ingame with all keyboard-commands
If not - I have no idea ( after deleting and repair )
Tested it with two different MODIFIERS + POV1
PINKIE
LShift
Yup, those are the bindings I tried. Those and the "button" approach (through the Mad Catz editor) and so far I haven't been able to move the RDR DES a single millimeter using the X52 HOTAS.
I'll try a complete uninstall/reinstall of everything X52 and see how that goes. If not, I guess it's that final incentive I needed to motivate buying a Thrustmaster Warthog, finally.
So, keep your fingers crossed this doesn't work. :music_whistling: :joystick:
Thanks a lot for your effort to try and help. I really appreciated it!
-
Ok, I tried binding the POV1 hat to RDR DES with pinkie as MODIFIER but no luck.
I then removed the settings and tried the POV3 hat instead (as buttons) but still nothing.
The funny thing is if I bind keyboard to RDR DES in the Controls editor I do get the correct keys (already bound to RDR DES). But when I close Settings and get back to the pit nothing happens when I press POV3. Isn't the X52 supposed to act just like the keyboard when configured to?
Weird ...
-
Hi,
This is only the standard setup with TIR ( plugin TIR and no deleting of the standard POV-views in the X52-column)
If TIR is active and not in "PAUSE" - you´ll look around with TIR
If TIR is not active or in "PAUSE" - you`ll look around with the POV
Screenshot above
Click on MODIFIERS
Right window : SWITCHES - ADD - Saitek 52 - JOY_BTN6
I must've been blind! :doh:
I'll try this out as soon as I get back to the sim rig.
Cheers mate!
-
In game : ADD the Pinkie switch (JOY_BTN6) to MODIFIERS
Ok, I have updated the SST drivers but that didn't help.
I also went ahead and deleted the F15 config/input folder before I ran a repair. The configuration is now like in your screenie, with the POV hat tied to view (which isn't very useful to me; I rely on the TIR for looking around). But how do I add the pinkie to "MODIFIERS" in game?
Thanks
-
Yes, having Track IR active would prevent the POV hat from looking around even if it is set to do so. You can pause the TIR and then see if the POV hat does look around when moving it. If it does, then it is assigned to that function and that may be conflicting with what you are trying to do.
Alternatively you can check the bindings in the controller menu and see if the POV hat is assigned to view.
Ok, I turned off the TIR and retried it but nothing happens in the sim when I move the POV. The mouse is what's to be used for looking around. Also, I double checked the binding in config and nothing is bound to the POV in sim.
General frequency?
in DCS: A-10C Warthog
Posted
Hi all,
Back after some non-simming years and still learning the A-10C. I was just about to try out "Operation Bactri" when I realized there's a few things I'm pretty clueless about.
1. How do I know which frequency to use to hear other units? The UHF radio is usually set to 251MHz but it's silent so I'm guessing I need to know which frequency to use for that.
2. What is the name for the above "general frequency"? What term do you guys use for it?
3. Pertaining to Op. Bactri: How do I learn which frequency to use for the AWACS (Chalice 3)? There's nothing in the briefing and I can't find the AWACS by opening the mission in the ME. I'm very inexperienced with building missions though, but I assumed there should be an actual AWACS unit somewhere? Either I'm too blind to find it or the AWACS tasking has been implemented in some different way.
(B t w I'm set up to use realistic radios)
Any pointers would be appreciated.
Thanks