Jump to content

bengo

Members
  • Posts

    595
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by bengo

  1. szadok, please confirm if you have the latest TIR-software installed. BS only works with version 4.1.036. Then make sure you have the right filter set in the profiles window. Make sure it says 'All titles' or 'Flight'
  2. I sometimes experience similar behaviour. I traced it down to the following causes : -sometimes the status in the lower leftcorner of the track-ir program window says 'tracking', as it should be. If I move my head in certain positions the status starts flickering between 'tracking' and 'no data' eventhough the three dots are clearly visible in the tracking-window, resulting in strange movements and jumps in the cockpit. I find it sometimes is started by when I access the 'Profiles'-tab in the TIR-software. Solution here is to shutdown the TIR software, unplug end replug the TIR-unit and the tracking should be fine. -if I use the DOT-overclock function in the Dualcorecentre-software for my MSI-motherboard, I see visualy distorted panels when I flick my head around using TIR. I also have very unstable zooming in the cockpit then. Turning DOT of fixes it, so it must have something to do with overclocking in this case. Hope it helps.
  3. Thanks for checking that Lange. It proves I'm not seeing ghosts. BTW, I'm not a Cougar user, I went the CH-way. I'll find a way around it, if it should bother me : haven't quite made it to the point where I can employ weapons....yet.:smilewink:
  4. Hey guys, ran into a bit of problems while setting up my HOTAS. Apparently there is a difference in how indows handles the AltGr-button versus the right-Alt-button. A number of European keyboards have an AltGr-key instead of a right-Alt-key to the right of the spacebar. Windows translates a press of AltGr not as RALT but as LCTL followed by RALT. Weird stuff. Think I'll have to drop making a profile on the stick, and map directly in BS.
  5. And it takes up 1 character less in a cramped space.....
  6. Something I thew together : http://users.telenet.be/bengo//blackshark_keyboard.pdf
  7. Yeah, I'd like that. Kinda like the keyboard layouts for Falcon, right ? I've been looking for a template to make one, but haven't found one yet. It's not gonna be easy, with all them multipliers though...
  8. Problem solved. Dunno what did it (I vote for #2 !) but here's what I did : 1) Update TIR to 4.1.36 2) Activated Vector Expansion in the 'Flight'-profile. So, all I have to do is learn to fly this thing.:doh:
  9. Uh-oh; Just read the BS FAQ. I'm still at 4.1.30 with TIR.:music_whistling:
  10. Too bad No difference with UAC on.
  11. I switched UAC off, in order to get the FMC in LDL767 in FSX to work. Vista is becoming a real PITA for me. Everything is installed on C:
  12. Thanks for your quick respose. Gamelist of TIR was already up-to-date. BS was in there. Alt-tabbing out of BS showed the TIR-window with BS listed as the current game. Tried running both TIR and BS as administrator, but no joy either, so is it still necessary to enable UAC for a test ? I'm just thinking : the less checks by the OS, the easier it must be for game and hardware to 'see' eachother. TIR works fine in these settings for all my other flightsims.
  13. I can't get TIR to work with BS. TIR-software sees BS is active allright, as Black Shark is listed as the active program in the TIR-ptrogram window. Blue led on TIR is on. What puzzles me most is that in set-up/controls I can only see TIR-settings in the axis for camera settings. Shouldn't this be in the views-section ? I'm sure I must've missed something somewhere, so any push in the right direction would be greatly appreciated. Using Vista32 (with UAC disabled).
  14. Yes, I'd like to see higher and longer-lasting smoke-columns, please. It would add to the immersion.
  15. ...and I was one of them. Thanks for putting it up.:thumbup:
  16. Took her up for a spin and managd to get her back on the ground in one piece. Great and smooth graphics. Looks quite amazing actually.
  17. Hi Urze, you wouldn't by any chance know if BS wil be on display at LLTM, would you ? I figured ED might see it as an opportunity to show it to the community like they did in Brussels a few months ago. Greetz
  18. Might be best to have a look at the Saitek site. They have a forum where you can get help for your problem.
  19. Have you tried programming a single keystroke to those buttons/switches, and then load the profile and check in notepad to see if the keystrokes get generated that way ? That's always a good check to see if the Saitek side of things are working or not. I'd try that before uninstalling LockOn. Here's a thread with good info : http://forums.eagle.ru/showthread.php?t=28251
  20. I know from previous experience that the drivers can cause these problems, especially if you've tried to uninstall or mess with them. I recommend going to the Saitek site, lookup the proper uninstall procedure, execute, dl-latest drivers, install according to Saitek. Doesn't hurt to try. Hope it works out for ya.
  21. Well, they've changed for the SU-25T : (numerical keys are not the ones on the numpad !) ALT-1 = Attitude hold mode ALT-2 = altitude (baro) and roll hold ALT-3 = transisition to level flight - aka panic button ALT-4 = baro altitude hold ALT-5 = radio altitude hold ALT-6 = route following ALT-9 = disengage autopilot ALT-² (above TAB) = AP momentarily override AP (press and hold) Check the manual, pages 47, 48 and 49.
  22. You lucky b*st*rd !!!:pilotfly::smilewink:
  23. Hey, wrote the e-mail yesterday and already got an e-mail back. In order to make a 'shift' command work, you need to split up the command completely : First create an "on release"-section for that button/switch, by clicking the specific button clicking the specific button on MacroworksII-screen and clicking 'On release' on the 'Insert'-pulldown. Set the cursor in the top window, press and release the shift-key, click 'Key down' in the 'Insert'-pulldown, now press and release the lettre (A to Z), followed by another 'Key down' from the 'Insert'-pulldown. In the bottom window, do the opposite : keypress (A-Z), 'Key up', shift, 'key up'. Et voila...ça marche. A lot of work for a simple thing, but at least it works. And I'm not a good electrician either, but hooking up the matrix board isn't that hard.
  24. Hey Razor, thanks for your reply. Something is definately wrong with MacroworksII then. I've set them a message through the PI-Engineering site about this, some two weeks ago, but not got reply. I'll sent my findings to them again, but this time through e-mail. Would you please do that also, so they know for sure something is wrong. I'm running an X-keys matrix board by the way. Give my regards to the orange kangaroo :thumbup: Cheers PS : I'm from Beringen
×
×
  • Create New...