Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Those are for the backlight bulbs: https://hackaday.com/2018/07/24/milspec-teardown-c-1282-chaff-controller/
  2. Nice, finally we get a missile warning and even countermeasures so we're no longer a sitting duck! *Tires screeching* Wait, what? What's next, a paid RWR for the huey, even though that's had non-functional radar detectors on its nose all along?
  3. Saitek, like other hardware manufacturers, use drivers that provide mouse and keyboard devices that can be controlled using software. So if you press a button that's mapped to a keyboard key, it will function just as pressing a key on your physical keyboard would. If the mini stick is set up to control the mouse, that too will work just like your physical mouse would. For keyboard and mouse there is no concept of input "authority"; If it's a device connected to your computer, it can provide input (even if it's a virtual device, which you installed with the Saitek software). So, yes, this is perfectly normal.
  4. This question is also answered on the official VoiceAttack forum, with information on where to find the file. If you want to find the profile database quickly, you can enter %appdata%\VoiceAttack into the address bar of an explorer window, the search bar in the start menu/on the taskbar, or the run dialog. There is also a link to that folder on the "System / Advanced" tab of VoiceAttack's Options window.
  5. I believe the multiplier argument for numeric ranges(VoiceAttackHelp.pdf page 17) would come in useful here. Using a "When I say" phrase like "[1..49] [Nautical Miles;Kilometers];[10..60,5] [Nautical Miles;Kilometers];[4..15,100] [Nautical Miles;Kilometers]" would mean you can speak values from 1 to 50 in increments of 1, 50 to 300 in increments of 5, and 300 to 1500 in increments of 100. Optimizing the required accuracy like this will allow you to bring down the number of generated command phrases from hundreds of thousands to a few ten thousand, meaning the profile will load much, much quicker. Also, you can rename the timer command to "Give me 1 minute;Give me [2..300] minutes", to reduce the amount of generated phrases for this command by half. As you're using global variables, something you could add is a command that uses the calculated value to set a timer directly. That command could simply use your existing timer command by passing the value to it like this: Execute command, 'give me {DEC:eta} minutes' (by name)
  6. It could still be a corrupt driver, or a more general Windows issue(though it is strange that it occurs on two machines), but if you're upgrading anyway it's probably not worth chasing down, providing you don't have issues with the newer hardware. Good luck to you.
  7. Use the Windows search in the start menu(or your taskbar) to find "Device Manager", it should come up with one entry with the subheading "Control panel". Click it, and it should show you a list of the devices installed in/connected to your computer. It'll likely fold out the unknown device and mark it with a yellow triangle sign. Right-click it and choose "Uninstall device" in the context menu, that should remove the entry. Click "Scan for hardware changes"(the blue monitor with a magnifying glass over it, above the list), it should find the device and attempt to install it again. If this still fails, you can try right-clicking and choosing "Update driver" in the context menu, here you can choose to either have Windows try and find a driver(though it may just use the "bad" driver again), or manually select one by picking from a list(which should include all compatible drivers currently installed).
  8. I assume for the laptop you're not using a USB hub? If the device appears in Device Manager, I'd try uninstalling and/or manually selecting a generic driver for it.
  9. Did you manually install drivers on the laptop as well? Does the device show up in device manager at all?
  10. These pedals should work as a DirectInput joystick device, without any extra drivers(I.E. they come with Windows, and have since XP at least). Have you tried removing any third-party drivers you've installed manually?
  11. Pretty sure the first item is a normal screen, it's just that the front panel controls for power and the built-in onscreen menu are touch sensitive rather than traditional pushbuttons(I.E. they are used to control the screen itself, and don't send anything to the computer it's attached to). The second item is likely a resistive touchscreen, judging by the type of stylus. These types of screen do technically work without the stylus, as they register pressure on the screen from any object, but they're not as sensitive to touch as your phone would be, for example. Where a modern phone using a capacitive touchscreen will in some cases detect your finger even before it physically touches the screen, a resistive touch screen will often require a reasonable amount of pressure before it responds to your input, making for a less pleasant experience.
  12. If you're referring to the CRT monitor, that's pretty much unavoidable; Any type of picture-in-picture requires that view to be rendered separately. This is also the reason why mirrors are so performance intensive(notice how in most games, mirrors are either limited to small rooms, broken, or just plain don't exist).
  13. Are you aware Oculus Go isn't a PC-compatible headset? It's supposed to be used standalone, like a smartphone-based VR system.
  14. Huh. I've always had this behavior with the Gazelle, so I figured it was just the way the flight model/SAS system works; I shelved the module because of it. If it is a bug that can be fixed, I'd love to be able to give it a second chance. I'm using an MSFFB2 with FFB on(the trim was completely unusable last time I checked as well). Curves are untouched.
  • Create New...