Jump to content

derelor

Members
  • Posts

    4062
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by derelor

  1. You are not blind. It's not implemented in the current public version, but already fixed internally (ticket #27767).
  2. Unfortunately I cannot watch it. YouTube won't let me: "This video is not available. Sorry about that." Could you also upload it somewhere else?
  3. This is now fixed internally. Thanks for reporting, guys!
  4. Thanks, reported as ticket #27768.
  5. I think there is no bug. There are two different input assignments that result in opening the comms menu in the F-86F: 1. Communication Menu: "\" ("#" on DE keyboard) In easy comms mode (Options → Gameplay → Difficulties → Easy Communication Checkbox) this always brings up the communication menu (both on the ground and in the air) In realistic comms mode this key acts as voice call (when the canopy is open) or intercom (when the canopy is closed). The communication menu is only opened when the aircraft is on the ground so that the pilot is able to shout out to the ground crew from inside the cockpit. 2. Microphone Button: RALT+"\" opens comms menu both on the ground and airborne, but radio needs to be powered for PTT button to work
  6. derelor

    Rest in peace

    RIP
  7. I was told that BST is aware of the issue and actively working on it. Let's all stop the whining now, please. All we can do is wait. If you want to do something constructive in the meantime, please help me assemble a list with all missing items in the UH-1H Flight Manual: http://forums.eagle.ru/showthread.php?t=128898 Thank you!
  8. Old, but still great:
  9. Wow, I love it! Reputation added.
  10. The Sabre is a fantastic aircraft - I love it.
  11. "USAF F-84F Thunderstreak fighters were painted with Communist Bloc paint schemes and insignia to portray enemy MiG-15s." from http://en.wikipedia.org/wiki/The_Hunters_%281958_film%29
  12. I fully agree with you that mouse input should be standardized across all DCS modules. ED should establish a standard that all 3rd party devs have to follow. Mouse input is not consistent inside A-10 or P-51 modules. Look for example at CMS NWS, JMR, RWR, DISP switches (A-10C) and Homing Adapter Mode Switch (P-51D).
  13. BST certainly knows about this, but I will try to bring it to their attention. What else besides p. 68 (http://forums.eagle.ru/showpost.php?p=2151528&postcount=78) is missing in the current "unfinished" UH-1H Flight Manual? Can someone help me assemble a list with missing items?
  14. General issue, not limited to F-86F. See for example http://forums.eagle.ru/showpost.php?p=2151625&postcount=1. Reported as ticket #26899 and already fixed internally. Reported as ticket #27287 and already fixed internally.
  15. Update: In current internal version there are no more mouse input inconsistencies in UH-1H (ticket #27594) and F-86F (ticket #27386) modules. See attachment for rules.
  16. This is already reported (ticket #26899) and already fixed in some internal versions.
  17. Update: Missing notch and "100 FEET" label fixed internally...
  18. That was fast. Thanks again! :thumbup:
  19. Thanks. Could you provide a track file?
  20. Reported as ticket #27453. However, I cannot replicate these morse code audio issues in my current internal version (based on DCSW 2.0.0). Could you please provide tracks created using version 1.2.10?
  21. Are you sure Picunda is SW of Sochi? :D I also receive Primorsko-Achtarsk NDB (Morse Code --. .--) on 920.00 kHz. This is strange because it is of status "BEACON_INACTIVE" in file Beacons.lua (at least in my installation): Can you provide another example?
  22. I know. All the errors pointed out here are in the ticket, however. :P Regarding the tooltip: I suggest changing it from "Baro pressure QFE knob" to "Altimeter barometric scale adjustment knob". What do you think?
  23. Good work!
×
×
  • Create New...