Jump to content

Nereid

Members
  • Posts

    333
  • Joined

  • Last visited

Everything posted by Nereid

  1. This very annoying bug (it stops my from using my Virpil controls as I intended to use them) is still present in 2.8.3.38090.
  2. This bug is still present in 2.8.34437.
  3. Seems we have to wait for an after early access manual...
  4. Thanks. So the P8 is just a backup. That explains a lot - and it's a pain in the *ss to read it. So what is correct? Is the compass just a backup ore the main source for a heading? I'm confused now...
  5. Yes. But it is currently broken, because the covers do close automatically after the button is pressed. If you want to support cockpit builders remove this "feature" (it is a bug IMHO) and yes, an option to "simplify" it with a shortcut to open the cover AND press the button would be nice. Not all virtual pilots do have the equipment to assign extra buttons for operating covers...
  6. They have done extra coding to close the covers automatically (but not to open them automatically which makes no sense). So extra coding is no excuse. This is another valid point. I have bound the flap lever lock to a two state switch. So the button to unlock is ALWAYS pressed, i.e. the lock is held OPEN by the pilot. But the lock closes without input automatically so my switch is out of sync with the cockpit. In my opinion: If there is a control to open a lock, it should stay open - at least as long the control is pressed. And if they want realism, by forcing to open the lock, they should not give up realism by automatically closing covers that would not close automatically in the real plane. You can't have a cake and eat it too. Best option would be extra controls to allow people with less input options to operate switches levers by automatically open locks and covers but provide single controls to operate all separately too. And they should add controls for the states for all levers/swiches and not just up/down binds as it is done for the flaps currently. They should think about a standard for all modules to do it this way.
  7. Then they should stop this. This is not helpful but a nuisance. And because the covers won't close automatically in the real plane I would call it a bug - until they add an option to disable this. And if they like it, they should make the buttons clickable even if the cover is DOWN (or open it automatically if the button is pressed). To emphasize it: I would NOT have bought the module if this behaviour was in place as I tested it or I was just not aware of it. It is a mess at this point. Exactly. I in my opinion they should remove it ASAP or fix it by adding new control options.
  8. What should the R.I. Compass Repeater display? Magnetic heading? So it is linked to the compass or it has its own? Or should it display true heading? Then how it is adjusted? And currently it displays neither. Not true heading nor magnetic heading but it is always a bit off. A bug? Or is it working as it should?
  9. The flap lever lock is automatically locking after flap lever is pulled up (from the lower position). Is this intended? This happens even if the unlock button is constantly pressed. This behavior makes it diffucult/impossible to bind (two state) switches to this lock.
  10. Can we please have three state shortcuts (up/middle/down) for the flaps lever? The up/down controls does make it impossible to use an axis/button lever on some control hardware (virpil throttle in this case).
  11. If you open the cover for a start or booster coil the cover closes automatically when the button is released (for no apparent reason - I don't think it does this in the real aircraft). This is very annoying, because for a second try you have to reopen the cover. For people using virpil control panels the buttons stops working for no reason, after the button is released (we have four switches with covers that do not work anymore since this behaviour was introduced). This happens if the button is pressed by a key/button shortcut or with the mouse. Version: 2.8.0.33006
  12. So the windscreen wiper is now at last animated and is working if the wiper control switch is clicked with the mouse. But the key/button bindings do not work - at least not for me. Version: 2.8.0.32235.1
  13. No problem. I was just asking if they binds are working. Currently they are not and that was the answere to my question.
  14. Neither. The switches are animated but not by bindings. I didn't say anything about their function. Let me repeat what I have said: It is pretty clear, isn't it? And that is exactly my point. Such missing bindings get overlooked very easiliy later on.
  15. It shouldn't. It is a switch. And you can bind them to a key or button. But it's not working. But feel free to explain how changing a sight should affect a switch.
  16. I was referreing to the "Laser Tracker Mode (LT)" and the "Image Autotracker (IAT) Prolarity" switch. It doesn't react on Keyboard bindings. You could change it by mouse but not by keyboard/button. No. Changing the sight should not affect a switch.
  17. Are the right hand grip laser tracker mode bindings not working in the current beta?
  18. OK, after deleting the AH-64D folders for the input configuration, they are working again. Something strange in the config was changed. And now I have to assign all buttons for 3 Virpil Panels, the throttle and the stick again. How lucky it is Sunday... EDIT: I have deleted those folders: C:\Users\[...]\Saved Games\DCS.openbeta\Config\Input\AH-64D_BLK_II_AI_Menu C:\Users\[...]\Saved Games\DCS.openbeta\Config\Input\AH-64D_BLK_II_CPG C:\Users\[...]\Saved Games\DCS.openbeta\Config\Input\AH-64D_BLK_II_PLT
  19. Even if I change "DENTENTS in lockout position" to "jump over" (I was using buttons to do this) in the settings they won't work. As soon as they go into IDLE position they just stay there. After pressing "KP+" for a short time, they are working fine. EDIT: Even if I assign BOTH levers to a different axis on a different device they will not work correctly.
  20. Strange. This doesn't work for me.
  21. For me the power levers do not work with my axis anymore. The will work after I inxrease the lever with a keyboard shortcut. If I move the lever down to IDLE, it stops working again and ignores the axis totally until I increase it with a keyboard shortcut. There is no other axis assigned to the lever. They did work in an older version. I do not know for sure if they stop working with the new update. Version 2.7.18.30348
  22. At some airports it works if you hold before the runway. Sometimes even before the holding line.
  23. Oh, and I think the red runway sign on Ramat David at the start of runway 33 is wrong. The runway goes to the right but the sign shows "33-15". Shouldn't it be "15-33"?
  24. Here are two tracks. One from Beirut Rafic Hariri airport, RWY 17 with several requests and one from Ramat David. For Rafic Hariri airport timestamps are as follows: 17:00:11 : Request for startup (answered) 17:01:14: Request for taxi (answered) 17:03:14: Request for T/O, before holding line (NOT answered); repeated one time, again with no answer After this I was aproaching the RWY step by step and repeating the request until I got an answer. Version: OpenBeta 2.7.16.28157 Syria - Beirut-Rafic Hariri - RWY-17-no-takeoff-permission.trk Syria - Ramat David - RWY-33-no-takeoff-permission.trk Unfortunately you have to enter the runway quite a bit.
  25. I will do this today as soon as time allows. In my scenario I was the only plane on the whole map in singleplayer.
×
×
  • Create New...