Jump to content

Havner

Members
  • Posts

    347
  • Joined

  • Last visited

Everything posted by Havner

  1. I think I already tried it. Definitely tried with the sequence: EDIT knob MODE button (WPT, TP) NUMBER button RESET button and it didn't work Does the OPER afterwards make a difference? At work now so can't try it.
  2. As in subject. I know how to reprogram it (overwrite). I know how to add a new point. But how to completely remove a point as if it was never programmed. Let's say I have a pre-programmed 4 WPT flight plan. In the EDIT mode I can change the coordinates of any of the 4 points. I can add 5th or 6th. But how to make the route consist of 3 points? Or I added N target points while flying and I want to clean them not to obscure when I fly to a second location.
  3. Couldn't you just move the lua profile you prepared for 1.2.7 from user directory to the game directory in 1.2.8? Name it either default.lua or name-of-your-controller.lua and it should work. If you made 124 buttons I can't believe you haven't made a backup.
  4. With lots of messages message log on the upper left side of the screen gets bugged. It doesn't disappear by itself anymore and is not displaying new messages. Might be DCS world, not Ka-50 specific, but I only fly in Ka-50 for now.
  5. Could you please try to open Deployment campaign, mission #10 and fly to either Torba or Skala and tell me whether you can actually refuel there? Maybe some conditions has been changed and the missions were not updated accordingly. I can live with stupid AI, it's been a problem since the beginning. But the message log is also annoying like hell.
  6. Seems I'm not alone. Exactly same the same problems. Different plane. http://forums.eagle.ru/showthread.php?t=118018 The most important issue for me is being unable to refuel. Completely stopped the engines, tried to talk through the open door (intercom turned off). Rearm works, refuel: "unable to comply". Looking at BeachAV8R AAR those FARPS were able to refuel you before.
  7. Despite constant crashes at startup I have a few problems (some general with the Campaign but can describe them with this mission as an example). 1. Refueling as SKALA, doesn't work. I'm low on fuel, I leave the ingress point, fly to SKALA and land. I can rearm, I can't refuel. Always "unable to comply". I had this in few previous missions as well. I can see trucks with barrels of fuel at the FARP, but they refuse to refuel me, only rearm. I tried powering down the helicopter completely, doesn't help. 2. After trying to refuel all the chat log becomes persistent on the left side of the screen and doesn't disappear. Obscures the view and new messages aren't shown anymore. This looks like a bug in the DCS itself. Does anybody know how to mitigate this? 3. After the initial wave of targets my wingman destroyed (pointed with DL) there comes a point where he refuses any engage order I give him. I select DL target, he refuses. I order him ground targets (targets of opportunity), he refuses. I send him to reconnaissance, he finds 2 targets. I order him targets of opportunity again, he refuses. He still has some Vikhrs left. I can see them on the external view. Besides he rearmed together with me. We're about 3-4 kms from the edge of the village, so it's not outside of his range.
  8. I get this a lot. With NEAR GUNDELEM and few other missions in the Deployement campaign. Eventually they seem to load after few tries, but this is getting annoying. 1.2.8.27203 here, but it happened on earlier versions as well.
  9. Does anybody have complete macros for Flaming Cliffs 3 airplanes generated from the LUA config files? Something like Sim2TARGET generated files. Something like the Black Shark macros attached. I've managed to generate those using outdated and modified by me Sim2TARGET for BS2, Huey, MI-8 and the Mustang. But I failed for FC3. The FC3 LUA config files are generated from the default input template + differences and didn't manage to marry this with Sim2Target. Would be grateful if someone could share them. aaa-DCS-ka50.zip
  10. Thanks. Looks promising. Will try using GameOutput() and see if it makes a difference for me. EDIT: Funny thing, what did seem to help me was your modified target.tmh.
  11. It's described in the TARGET manual :-)
  12. The point is exactly the opposite. It is to use them and make them display meaningful information that you need :-) I have no problem to learn how to use them, I know this pretty well. I have a problem with a hardware (or drivers for that matter) that blow up under certain conditions.
  13. Since I bought them, which is 2 days ago ;-) I seem to have this problem now sometimes even when changing one LED. I use GAINU/GAIND to switch "pages" on the MFDs and the LEDs tell me which page I'm on. I will investigate this further anyway. I need to get to a working setup anyway. EDIT: Warthog throttle leds seem to be resistant to the issue.
  14. I think I found a reason. You can't change both MFD leds at the same time, or even with little time in between. Could somebody try this? After 2-3 presses of GAINU/GAIND the MFD should hang or even restart. MapKey( &RMFD, GAINU, LED( &RMFD, LED_ONOFF, LED_CURRENT^LED1^LED2 ) ); MapKey( &RMFD, GAIND, LED( &RMFD, LED_ONOFF, LED_CURRENT^LED1^LED2 ) );
  15. In general mine is as well. They do work. I'm asking about some fancy TARGET constructs. Have you tried the above for example? EDIT: the above is not enough, I have pretty big profiles. Will try to prepare some use case.
  16. Has anyone noticed any incorrect/poor behavior of the TARGET software when the MFDs are connected? I have Warthog + 2MFD, so that's 4 TM devices in total connected. I recently bought the MFDs and some completely valid constructions cause all the TM inputs to hang. E.g.: MapKey( &Joystick, S3, TEMPO( EXEC( [color=#a52a2a]"f1();"[/color] ), EXEC( [color=#a52a2a]"f2();"[/color] ), 300 ) ); If there are 2 EXECs in TEMPO hitting the key hangs all 4 TM devices. If I disconnect 2 MFDs or put just one EXEC in TEMPO it works properly.
  17. You don't necesserily need the leds. They are just for the looks. I know if I hit the button 3 or 5 times. No need for the leds to tell me that in normal cases.
  18. Hi, I wanted to be able to use the comms menu directly from HOTAS, but assigning 13 keys was too much (PTT + F1-F12). So I scripted this and thought I'd share. It allows you to complete and conveniently use the comms menu with 3-5 keys. PTT NEXT PREV (optional) CONFIRM BACK (optional)You hit PTT, and you are at position 0. Then you hit next as many times as the position you want to reach. You want F5, you hit NEXT 5 times, then CONFIRM. And you're back at position 0. You can also use PREV if you accidentally go to far. Hitting CONFIRM while at position 0 is ignored. You can use BACK to go back in the menu depth (F11). It does remember your history. PTT, NEXT, NEXT, CONFIRM, NEXT, CONFIRM, NEXT, NEXT, NEXT, NEXT, CONFIRMwill generate: ptt, F2, F1, F4Now, let's say you really wanted F5 instead of the last F4, you hit BACK and NEXT (one time, F4 was remembered, so to go from F4 to F5 you hit NEXT once). And you can go back this way to the very beginning and whole history is remembered unless you modify it at some point with NEXT or PREV. Actual position is displayed using leds in binary code (too few leds to display it in any other way). The least significant bit is at the top. 0 means no leds. If you want to quit the comms, hit PTT one more time, all the PTT buttons I've come across in DCS quit the comms menu. I didn't implement F12, but it could be done as well if needed. You can use it even without hitting PTT, just to generate F keys. How to use it: Before you include the header file you need to define the PTT key (every plane might have this different). Complete example: [color=#1e90ff][b]include[/b][/color] [color=#a52a2a]"target.tmh" [/color][color=#a52a2a][color=#1e90ff][b]include[/b][/color] "[/color][color=#a52a2a]your_macros.ttm"[/color] [color=#1e90ff][b]define[/b][/color] COMMS_PTT_KEY SPU_9_PTT [color=#1e90ff][b]include[/b][/color] [color=#a52a2a]"DCS-comms.tmh"[/color] Change SPU_9_PTT to whatever PTT key you might want to use. Now somewhere in the main() assign your keys, e.g.: MapKey( &Throttle, MSP, COMMS_PTT ); MapKey( &Throttle, MSU, COMMS_PREV ); MapKey( &Throttle, MSD, COMMS_NEXT ); MapKey( &Throttle, MSL, COMMS_BACK ); MapKey( &Throttle, MSR, COMMS_CONFIRM ); MS HAT is great for that. Hope someone will find it useful. DCS-comms.zip
  19. Ah, now it does. In the first version it wasn't mentioned. Ok, it's clear now. Thanks.
  20. I'm not asking about clickable cockpit or system modelling. I'm asking about flight model.
  21. According to this Su-27 has PFM: http://forums.eagle.ru/showthread.php?t=122801 I'm quite new to FC3 but I never noticed anything about it having it already. There is a news that Su-27 PFM is in progress but it won't make it in 1.2.7: http://forums.eagle.ru/showthread.php?t=117467 And I see nothing in 1.2.8 changelog. Did I miss something? Or is this post just looking in the future?
  22. Yeah, this one I figured. Ok, thank you.
  23. My point was (as in this thread) how to do this without ABRIS.
  24. In Flaming Cliffs they operate as a helper how you should fly to get you on a path to a selected track. In BS it could work the same way (that's what I assumed). That they point you to fly the same way a Route mode would in a particular moment if it was turned on. Would be awkward if they were meant only for ILS by design, especially in a helicopter.
×
×
  • Create New...