Jump to content

erjdriver

Members
  • Posts

    269
  • Joined

  • Last visited

Everything posted by erjdriver

  1. Thanks - that helped quite a bit.
  2. i'm doing the campaign missions and getting a little bit tired of flying 20 minutes to the target and getting shot down in about 2 minutes...then having to re-fly the entire route. Getting really good at navigation... Any way to speed up this "dead" travel time. Thanks.
  3. Thanks guys... In keeping with the spirit of simming - pressing F10 doesn't seem like the thing to do - that's not an option in the real aircraft. I would think the bullseye can be saved as a fix in the abris. then using the features of abris can draw a line to the approx area - got cords and then use the pvi to navigate to it. seems like a lot of work but i can't see another option. if the instructions are w/ relatively short distances - then one can view the BE on the abris and eyeball the approx location - at least till you get it in the abris.
  4. I'm playing Deployment campaign and in one of the missions there's radio chatter re bullseye. How do I figure where that out? I see it in the mission plan - but are the cords already in the abris or the pvi. how do i get to it and also how do i interpret the radio instructions. Thanks.
  5. When I assign the trackir z-axis to the longitudinal axis and zoom to a slider - it seems to be ok except that when i bring the slider back to the starting position - there's still a little bit of zoom enabled. I like assigning the trackir z-axis to zoom - the problem there is that it assigns a little bit of zoom and am too close to the dash. What do peeps use? I need the ability to move in closer and look at the hud - the default assigning of trackir z-axis to longitudinal axis is not close enough.
  6. disregard
  7. With trackir - my position is a little bit too close to the front dash. It was to do also with the fact that i have the trackir_z axis assigned to zoom - but i prefer that. I understand that I can set the pilot view position (default) and FOV in DCS - how do I do that. Thanks.
  8. Thanks - got it to work. Not too intuitive that I have to uncage something that's already uncaged. I hope my questions allow you to improve your document(s).
  9. I believe I followed your instructions to a T for PVI SHKVAL TARGET POINT (2nd one) - and can't get it to store the coords. I assume the switch is the one to the left of the DL power - labeled I-25I or something somethng similar. In step 5 - i assume I have to lock on to a target - did that. in step 6 - when i press enter - i assume i should see the cord on row 1 and 2.
  10. Thanks. As you might have guessed, I'm going thru each procedure of your avionics cheat sheet. Suggest - you add the location in the footnotes for the next soul. I looked quite a bit.
  11. Where is the PVI UNI/Update switch?
  12. Wow - that's good to know. Then the "FD" on this aircraft is not really a traditional/modern flight-director....that's what was throwing me off.
  13. Thanks fish. I think what I was doing wrong was - i wasn't flying close enough to the waypoint and it wasn't sequencing to the next waypoint. I was thinking it was auto-sequencing (because of the heading bug changes) - but it could be that the bug is pointing back to the wpt i just passed (i.e. 180) - i'll verify that by looking at the heading bug on the HSI next time. On the last image, the FD is commanding a right turn with approx 10 deg pitch up. The speed offset is telling you you're going 20+ km/h too slow. And you're spot on with the altitude. Correct? Now if you pitched up as directed - you would lose even more airspeed and gain altitude. If you tried to fly faster (because it's telling you you're too slow) - you have to pitch down (cyclic forward) - that's opposite to what's commanded. Help? How would you fly the last FD commands.
  14. Good suggestion - but I do. I know because the heading bug at the top jumps to the new desired heading. I get the 2 horizontal '=' symbols but it doesn't bank. maybe because I have bank auto-pilot channel enabled - i doubt that because I have heading channel enabled also and the bug jumps.
  15. Any help here? I've got bank, heading and pitch auto-pilot channels enabled. Following a flight-plan - in route mode. And enabled FD. Anyone know why I'm not getting bank indicator.
  16. Thanks - it's starting to work. As a software guy, I must say the sequences you have to go thru are just not user friendly. Up prt pressing weird sequences - down verify with the abris - up prt send etc. Same button doing different things in different context. Then requiring caging of shkval. you're looking at the target and now you have to lose lock and reset shkval - just because you want to store the data point? You reset - now you have to repress buttons, select weapons. seriously? Then the abris not talking to the pvi - crazy. different default coordinate system. Not complaining...just saying.
  17. I look forward to trying it later. I'm sure you'll add that critical step to your instruction booklet.
  18. Here's the track file https://www.amazon.com/clouddrive/share/GpC-moB8v7QFl9JBAzcH_7tmVkPVKZezoTf7xP1ZCdU I lock and save a target, then I change my heading. Select the target from Abris and try to lock on it.
  19. No I haven't. I have the point blinking in the abris, press reset (backspace) - reenabled a2g and turn2target and then pressed O. nothing - except i think the shkval goes into scanmode (maybe that happens the 2nd time i press O) Nothing selected on the PVI and HMS is stored. I assume if working correctly, the heli should turn to the target and the shkval should be pre-locked on to the target. But I haven't tried it since I got the comm to work. I will try later and report. Thanks for the follow-up.
  20. The key feature I want is buttons with LED inside them. Even though the last one is very interesting - but I think it's 1-way only (so no way to control LEDs).
  21. I'm thinking of creating a panel with a bunch of pushbuttons and switches. Controllable via Arduino + DCS bios. Before I start on the project - has anyone done anything similar. No need to re-invent the wheel. My idea is to create a panel with a sets of pushbuttons w/ LEDs and some switches. Usable for any DCS aircraft - w/ minimal programming.
  22. Ding ding ding! Problem fixed. I'm playing the standard training mission w/ no add-ons. But on reading your email - I copied it to my-missions folder and ran from there - worked fine. Thank you very much - now I can move forward.
  23. I pressed Ralt+\ and that brings up a similar menu except it says R800 at the top. If I press \, it says Auto at the top. Still not working. Re locking on the Abris data points. I selected the point (flashing), reset (BS) and then pressed O - the shkval is not auto locking to target. (I don't have anything selected in PVI nor have the HMS activated.)
  24. Thank you - that clears up quite a bit and i'll put it in practice. Any light you can shed on my comm predicament.
  25. Re the data link - i press \ key and I do get the comm menus F1.. etc. But it's not transmitting - but i'll look at your PTT suggestion. All the symptoms of an incorrect freq. - i've set the radio selector to VHF2 and turned it on.
×
×
  • Create New...