Jump to content

FalcoGer

Members
  • Posts

    1192
  • Joined

  • Last visited

Everything posted by FalcoGer

  1. I'd very much like the 2 and 3 way switches to have bindings to have them automatically switch back when the corresponding button is no longer "pressed" (for example the behavior for the warthog switches). Or as I have suggested before a new feature for the input system that allows you to bind "on release" buttons to controls. so if your 3 position switch on your physical controller has BTN 12 - OFF - BTN 13, then you could bind one cockpit function each to BTN 12 and BTN 13 and bind the center position to BTN 12 Release or BTN 13 Release. This way every aircraft would be more flexible and you could get rid of some of the specific control bindings to declutter the list. For example I have the master arm and laser arm in the ka-50 on the EAC and Radar altimeter power switch, but there is no option to disable those systems when those buttons are no longer pressed. so i have to flick them twice to make that happen, which is inconvenient. It would save the aircraft makers from making lots of key bindings and it would allow users to add whatever they wanted to the off positions for their switches. More here:
  2. I would like the grouping as well, but for single targets it should also display a type, not just SR SAM but maybe "SR SAM - SA-8 Gecko (Osa)" and instead of "TANK" it should be "TANK - T80". Mostly because HUMVEE = APC and BTR-90 = APC. You get them both in the same list and your CAS mission will turn out to be interesting.
  3. Repairing george and giving him an oil change makes him wake up again, but unfortunately he's too scared to press any buttons after that.
  4. In the daytime, my preferred method is to just turn down the video brightness on the HDU 1. Select HMD as sight, so that the brightness rocker controls the HMD video brightness and not the TEDAC display 2. TEDAC BRT down a few times 3. TADS as sight 4. (ACQ -> GHS) That way you can still look around and slave to your view, but also not be having trouble seeing through the green image. Unfortunately I don't have VR so I can't just ignore it. Of course this also disables NVS overlay. So either you have to add the brightness back, use NVG or deal with the video or use another method. Alternative ways HDU off when using TADS Sure that works, but then you can't precisely slave to your head, only the rough area. You also have to bind an extra button to your hotas or take your hands off to find the I key on your keyboard. Of course you can just select wide FOV and use the slew controls, but that's slow, imprecise and you don't know exactly where the TADS is looking and it's just awkward. Select HMD Sure it gets rid of the video, but no TADS control, in particular no slaving to head either. Turn TADS intensity (LVL) to 0 Advertised by Mr Wagner himself, the most useless option. Because it just turns the TEDAC screen AND the video overlay off. HMD as sight is faster and you get at least something useful. On the bright side, you get to slew your TADS around blindly. I think that's all the ways to get the video to disappear aside from shutting down the TADS completely (WPN -> UTIL -> TADS).
  5. "Needs track replay"? Are you serious? I told you exactly what the problem is. MULTIPLE people confirmed it, including raptor9 which is a SME. There is no need for a track replay. If you need a track so bad, then just put your hot apache on the ground in syria in the middle of summer and torque up and wait 50 seconds. The time it takes to do that: about 120 seconds, including loading time. The time it takes me to do that for you: 15 minutes, including saving the track, uploading it here. On top of that I'd need to try to get the "needs track replay" nonsense out of the way because apparently even IF i were to add a track, nobody ever checks anything again after it has gone onto the "needs track" pile. I'm not your bug hunting team, I report bugs as I find them. If you need more, then reproduce the steps outlined by me and others. There is no need for a track that is clearly a visual or formatting error that appears 100% of the time in conditions that are reproducible reliably. I like to fly the products I have bought from you, not debug your problems for free, thank you. If you were to pay me, I'd happily send you all the tracks you want. PS: Please check your messages @NineLine
  6. It might be related but the radio depress that is supposed to cycle through the radios uses a separate list to the RTS rocker switch. When pressing the rocker switch it switches radio, but it seems like internally there are two states for which radio is selected, and they're not the same. For example you start with VHF selected, then you move the selected radio by the RTS rocker switch to FM2. When you then push the radio depress it switches (presumably from VHF) to UHF instead of to the next in line, which would be HF. When then selecting down on the rocker switch again it selects HF even though UHF was selected, but the last rocker switch selected radio was FM2, from which such a change would make sense. To reproduce: 1. Start aircraft, don't touch anything radio related 2. RTS Rocker down 3x, selects FM2 3. Radio switch depress, selects UHF, expected HF 1. Start aircraft, don't touch anything radio related 2. Radio switch depress 3x, selects FM2 3. RTS Rocker down, selects UHF, expected HF
  7. This has been reported at least 3 times already.
  8. When the TGT exceeds safe limitations for continuous flight a 30 minute timer appears on the engine page. if the seconds on that timer are below 10, the leading zero doesn't show such that it reads for example "29:4" instead of "29:04". It's a minor thing but it looks awkward and should be easily fixed.
  9. As it stands now you can't add control measures or target points to the mission for the apache with the mission editor, only waypoints. You might also want to look at Show -> Coords to enable enemy control measures to show up.
  10. Acquisition source: Thing to look at Sight: Thing to look with (at the things that will die when you press the trigger) As the pilot you only get the HMD (until the FCR is implemented) as a sight. If you set your acquisition source to GHS you will see where the gunner is looking on your HMD. It doesn't mean anything though. It's just what you chose as your "Look here!" cue. As such you can't set your current sight as your acquisition source. That would make no sense. You are already looking at your "Look here!" cue, and it would always be that way.
  11. Doesn't seem impossible to implement, and also seems like it might work. from me. What should happen if you trim, then move the stick halfway back towards (0,0), effectively not adding any input on the helicopter, and then hit trim again? I would suggest that nothing should happen at that time, aside from whatever the helicopter thinks should happen when you press the trim button without moving the controls.
  12. I think this should also be extended to the flight ai, having some kind of indicator what the button presses do on screen.
  13. Well you can verify what he sees on the VID page, but it kinda sucks. He should be able to do it on his own.
  14. Ok then. Also is the Acquisition source supposed to return to FXD when swapping from TADS to HMD as sight? Would be convenient if it returned to the last acquisition source used for that sight instead of going FXD, which is almost never helpful, at least to me.
  15. I like to fly around with TADS as sight and GHS as acquisition source, so when I see something I can quickly slew the tads over and identify and potentially engage. But sometimes the pilot sees stuff before I do. Then I need to look down, press R6 and R1 on the MFD to get my acquisition source to PHS, which takes like 2-5 seconds, in which the pilot can't take his eyes off the target. Is there a quicker way to do that?
  16. They seem to fall short when engaging from a long range. I found them to be unusable from 4000m+ Best results from 1500-3000m.
  17. Enable freelook with left alt + c Then you can move the mouse to rotate your head. If you hold down the middle mouse button you can translate your head. you can also set your head position with right ctrl + right shift + numpad.
  18. I think george should be able to tell the difference between a HUMVEE and a BTR in the target list. But right now they're both "APC", especially when close enough (aka within 15km), or tell the difference between a rifleman and a manpad at reasonable ranges. Though I think the classification should still be in that list for those people that don't know what a BTR is. Or whatever confusing names the chineese come up with.
  19. When asking george to slave to your HMD, he will ask which target to lock up if there are multiple. However if there is only one, I would still like him to tell me what he sees. For example I ask him to slew to some area and there is a AAA and a truck, for example. Then I fly along and suddenly there is a building in the way of one of them. He just says "Target stored" (and he stores nothing, by the way) and I don't know what he locked up now. Should I shoot a hellfire or not, is it the truck or the AAA? I like the target selection to pop up, even if there is just one item in the list, just so I can confirm what he is actually going to shoot.
  20. I certainly cuss a lot at george refusing to fire, coming off target because there is a tree in the way for 0.2s, or flying me into a mountain
  21. I had a funny moment of the engines keeping running after I shut off both, one of which was a shot up one. The rotor would spin, I could even take off again with no engines running. Just to test it I defueled the aircraft to 0% and it would still be going. I was hosting that mission but it was like 4 hours. I did stream it on twitch though so if you want a video I can probably upload that to youtube or something.
  22. I hope this gets fixed. then. Will you write a bug report about it?
  23. can this be set to TADS video without having to press 3 buttons (VID - R1 TADS, T6 TADS)? Would be nice because sometimes you just can't avoid the low rotor rpm autopage and I like to have the video on the left.
  24. It's not just george either. all optically guided systems should be affected. That includes ground units like the rapier, tunguska (at least the missile part), zsu-23 emplacements, machine gunners on vehicles, etc etc. same with IRST on jets.
×
×
  • Create New...