Jump to content

electricaltill

Members
  • Posts

    267
  • Joined

  • Last visited

Everything posted by electricaltill

  1. My guess someone wrote those patch notes who isn't familiar with the aircraft - i.e it's the PVI-800. I haven't flown since the patch but I'm sure it's this: https://forums.eagle.ru/showthread.php?t=268831
  2. Put a semicolon at the end of line 14.
  3. I have had this too - the menu doesn't respond to clicks when it's happening, only the function keys.
  4. This problem still exists. Any fix incoming?
  5. Yes it makes sense for 'INU' to be above the switch somewhere, but the switch positions are not labelled correctly. Here's the shot from the manual, original graphics: https://imgur.com/hKSMRrC For INU updates/nav targets to be done by the Shkval is the 'up' position. This is labelled 'INU' in the new graphics, which is wrong. If you look at the Russian graphics for the new cockpit, the labels for the switch match the original graphics in the manual. The English version is wrong.
  6. I seed the update torrent files, so you can see how much is present for each module. The last update contained 400Mb for the Ka-50.
  7. There was just over 400MB for the Ka-50 in the latest update, but nothing declared in the release notes. Anyone know what changed?
  8. The switch next to the PVI-800 mode selector rotary switch is mislabelled. It has changed with the new cockpit update. The top position should be 'Shkval,' and the bottom position 'INU'. Currently the top position says 'INU,' incorrectly, and the bottom position says 'Update,' which doesn't really mean anything. I have verified this because by trying to use the Shkval to designate a target in the PVI-800, I have to set it to the 'INU' (up) position for it to work properly. If I set it to the 'Update' position it saves my own co-ordinates as the target point. The switch behaviour has not changed, the switch labels are just wrong.
  9. Clicking 'fly again' after watching a track should make me the pilot again in the same mission. Instead it plays the same track again. The only way I can fly again in the same mission is by using the 'take control' option after starting the track, or by quitting to the main menu and starting again.
  10. There's something weird going on with the lighting on these buttons. If there's sunlight on them, turning the cockpit illuminations on actually makes the buttons darker.
  11. The switch is not clickable. That is generally the case for buttons/switches on moving parts like the stick and throttle. You will find the weapon selector bindings in the "stick" category for the F-14.
  12. Yes, it's powered.
  13. That's funny, I just got a Virpil CM2 and was initially using the castle switch for the trimmer. I had to change it for the exact same reason.
  14. You don't mention the trimmer at all. Are you using it? There's endless debate about whether you should hold down the trimmer during manoeuvres or just tap it when you're done (I do the former), but if you're not doing it at all you're fighting the autopilot the entire time. Flying as fast as you say, you need all the control authority you can get, and the autopilot will be fighting you with 20% of it if you don't use the trimmer.
  15. I tried adding a name to a beacon for the Caucasus and the whole panel went blank. Can you describe how you did it?
  16. Mine are the same. I wondered if that was the reason but clearly not. It must be something in my sketches that is causing it.
  17. Yes sometimes I've had it freeze (when it was otherwise working) and it's just been a case of just restarting the app. Do you connect the boards direct to your PC or are they connected to a USB hub?
  18. That's interesting! How did you determine the correct format if the files are blank?
  19. Anyone have any ideas on this? I just saw a post in the announcements threat theorising about doing away with rs485 because windows supports so many COM ports. Has no-one else had this issue with connecting many devices at once? If a single board is connected it works fine. Any combination of 2 or 3 boards work fine. 4 is no, regardless of what the first 3 were. What could be causing this?
  20. Longstanding issue. I reported it in the past but no-one seemed interested.
  21. Just send ED support a ticket, and they can edit the licence for you.
  22. Thanks for replying, but I'm not using rs485. The Arduinos each have their own COM port.
  23. It's the address/argument/mask that governs which control is affected, not the arbitrary name given to the function.
  24. Both of these declarations are called "gearhandle". Change the name of one of them.
×
×
  • Create New...