Jump to content

MarcT-NL

Members
  • Posts

    276
  • Joined

  • Last visited

Everything posted by MarcT-NL

  1. Oh please let it be fixed in next update. This is killing ! And if it is possible (I will post this in the whishes too), can we have a method for centering the mousecursor in VR ? Most of the time I point the cursor by moving my head. But sometimes that is not possible (I'm not an owl !) and I have to grab my physical mouse. So that works fine, but then I have to manually put the mousecursor back in the middle somewhere or I can't use it anymore with my headmovement... A method for centering the mousecursor might be a key-binding or a setting that will center the mousecursor after 5 secs not beeing used or something like that.
  2. I have my Stick-pinky button set up as a Modifier. I binded the George-interface to a HAT-switch, with the Pinky-switch pressed. The bug is that when I open the Interface (Pinky+HAT-depress), I cant use another function before a let go of the Pinky, and repress it.
  3. +1, and might I suggest: Use RED for free fire, YELLOW for Return fir (or wait for consent) and GREEN for Hold fire.
  4. I installed it without problems. AH-64D seems to work perfectly ! Thank you so much.
  5. Don't know if this is a bug or a wish... In other aircraft you could place specific kneeboards in saved games\DCS.openbeta\Kneeboard\Ka-50 (for example). I tried the same with the folder AH-64D, but that doesn't work. Also, what properties should an image have to become a good kneeboard ? Like JPG/PNG or what ? Which size ? Any other properties ? Thanks
  6. Thanks very much ! So it is the 2.3.6 release that has the Apache ?
  7. 1. The color-codes of the ROE differ from other aircraft. I would suggest this: Green = Hold fire Yellow = Return fire (or wait for consent) Red = Free fire 2. Could we have an option to bring up George's last target-list again, without him having to slave to it ? 3. Could we have the option to tell George to attack everything on his target-list ? Or make selections of some kind ? 4. Could we have the option to tell George to man the gun, and shoot any hostile within reach ? 5. Could we have the option to tell George to scout out and report targets ?
  8. +1 Also goes for the Mosquito
  9. When I let George as a CPG fire the rockets, he will fire a lot of rockets together. Even if I set quantity to 1. Quantity=1 should mean: fire 1 rocket, wait until impact. If enemy not dead, fire another. Etc. Quantity=2 should mean: fire 2 rockets, wait until impact.... you get my meaning.
  10. Could you set the engine-vibrations to a set value for the time being ? And simulate a transition-vibration at a certain speed ? I do hope ED will make those parameters available ! Can you read out gun- and missile firing ?
  11. IT seems that this problem occurs in every aircraft now. Not just the Apache. This topic could be moved to DCS World bugs...
  12. The mouse-pointer (blue +) doesn't disappear when you leave the mouse alone in VR. It won't follow your head movement anymore, and it will jump back to live when you touch the mouse again, but it doesn't go away, like in all other airframes.
  13. No, I think you have to go back to your control-bindings. In the Pilot-controls there is the option to switch to CPG-seat (kyb 2). There is also the option to switch back to the Pilot-seat (kyb 1), but that is obsolete. When you are in the CPG-seat the Pilot-bindings don't apply anymore. You should bind kyb 1 in the CPG-bindings. I hope that makes sense.
  14. Just to be shure... you cannot buddy lase for Vhikrs, right ?
  15. Hello, I was trying out the delivery mode "Auto loft" for the JDAMS. I looked at the manual but it isn't mentioned there. It still says that this will come later in early access. I know how to programm a JDAM in PP or in TOO. But when I select Auto Loft, how do I know when to pull up for the loft ? Are there any good explaining video's out there ? I saw Wag's video introducing the LAR, but I'm missing something. Oh, and what is delivery method "Flight Director" mode ?
  16. This is probably not a bug, but "correct as is". But I still would like to bring it to attention. When you manually enter target-coordinates in the PVI-800, it assumes the target is at sealevel. Which it almost never is of course. That could be explained by the PVI not knowing groundlevel at that coordinates, like the ABRIS does. That could also explain why the ABRIS shows the correct location of the target, even if the Shkvall can't slew to it. It slews to that target at sealevel. However, when I use the Shkvall to get the coordinates into the PVI, the Shkvall is spot-on. It will slew to the target's exact coordinates at groundlevel in stead of sealevel. This also could be explained because the PVI-800 now can calculate the altitude of the target. It knows its own coordinates and altitude AGL, it knows the angle the Shkvall is looking down and it knows the range to the target (laser). Simple goniometry could calculate the hight of the target. When you compare the coordinates that you entered manually with the coordinates of the same target obtained by the Shkvall, they are exact the same. That must mean that the PVI-800 CAN considder altitude. There is just no way to enter that altitude manually is there ? Did Ka-50 pilots not complain about that ? Will this maybe be different in the Blackshark 3 ?
      • 2
      • Like
  17. Hehehe, no, I meant I am in need of guidance. I need someone to explain to me how to get bombs on target.
  18. Well, this actually works correct. When a Harpoon is fired, it travels to the target point at a set hight. High = 25.000ft. Med = 15.000ft. Low = 5000ft. When it detects a target (at about 20nm) it drops to 300ft and approaches that target. When at 2nm it will either drop and head for the hull (skim) or pitch up and head for the deck (pop). I have been told that POP is better for attacking warships, because of their hardened hull. Not shure if this is true/modelled in DCS.
  19. Wait what ? I am confused. When I reported this on may 25th 2021 together with track and all, it was Just deemed "Correct as is". Now you are investigating ? Am I missing something here ?
  20. Please do not call me a newbe. You know nothing of me. What you are talking about is the inability to slew the IRMAV, once there is a target-designation. That indeed is terrible, and unbelievalbe if true (apparently ED calls it Correct as is), but that is not what I was talking about. The FOV allways kept working until last update as far as I know. That the A10C-2 is way easier to use (matter of oppinion) is totaly besides the point. I do preconfigure. But that also is beside the point. I am pointing out a -probable- bug. I'm not looking for workarounds.
  21. Not shure if this is a bug. It used to wor in earlier releases. When de maverick type F is uncaged, the FOV doesn't change anymore. Not with the FOV-switch on the HOTAS, not with the button on the MFD. AG65F FOV.trk
  22. I was talking about flak-sites, and AAA (on a Schnellboot for instance). But I should clarify, I have a terrible target-fixation. I know that, but can't help it.
  23. Well that's fixed now. In th previous release, wingbombs could only be dropped if they were fitted in the mission editor. Not after re-arming. The current Mosquito (Jan-2022) can drop all bombs, also after re-arming, and can fire rockets. Just the bomb's rear fuses don't work. They set of on inpact so you can forget about low-level bombing. However; very nice and fun plane, and I'm taking it for a spin more and more. If only I could hit anything with the bombs ! Also I dread the navigator-skills needed, But that is for a later time. A bit dissapointed about the "fastest plane in the world" though. In cruise conditions it will go about 280 mph. That's slower than the Mustang ! And I just can't seem the kill anything that shoots back ! I'm dead before I get the pipper on the target. Need guidance
×
×
  • Create New...