Jump to content

old_red_eyes

Members
  • Posts

    18
  • Joined

  • Last visited

Everything posted by old_red_eyes

  1. How do they get there then? :confused:
  2. The Controls indicator is always displayed in bottom left of the virtual view, and this can not be changed in current release. You can align the second monitor with the bottom edge in Windows monitor settings, just drag the screen so it's in the right place. Or put the secondary on the right side of the desktop and run Phantom Monitor Fix to align the cockpit view with the primary monitor, then Controls Indicator will appear on the cockpit view.
  3. hannibal, seeing as no-one has chipped in... I have a th2g, but not hooked up right now, so here is my best guess. I think the TH2g gives you a horizontal spanned image, dimensions 3360x1050 in this case. So in Options.lua, define the screen size according to these dimensions. In your monitor setup file, create a "Left" and "Right" viewport, and use the viewDx/viewDy values to set the view direction. You need to match Left/Right viewports to physical top and bottom monitors. Both views will pan simultaneously. I am not sure if the mouse cursor will be usable in this configuration. Maybe someone knows a better way to do it? BTW check out the Multimonitor wiki http://www.vaaf.net/wiki2/index.php5?title=Black_Shark_MultiMonitors
  4. You don't have to physically move the monitors, just tell Windows they are in different places. Works fine for me. EDIT: Should say, with Phantom Monitor Fix... without PMF I have come to the conclusion it's impossible to get all the features displayed.
  5. Does it make any difference if you select Fullscreen on/off?
  6. Hi dsobbe I found my comms menu on the # key. Your approach seems like a good one. I think the problem arises because DirectInput provides keyboard scan codes to the game, so the developer needs to take care to map these to actual characters to cater for different keyboard layouts. This is tricky due to all the keyboards variants, so I guess some keys are not translated. I have done some experimentation, and found a few keys that are differently translated between US/UK layout: UK US ¬ ~ " @ £ # @ " # \ ~ | AltGr Ctrl+Alt (maybe?)I am not sure about AltGr, this key does not exist on US keyboards. There are probably other differences too. I don't know if there is a more scientific way to find out the key codes, I set my Windows setting to "US keyboard" and then pressed all the keys. If I have some time I will try to read the DirectInput codes and display them. I want to use an X-Keys keyboard with BS, so I will have to remap some keys anyway because X-Keys doesn't seem to support distingush Left/Right Shift/Ctrl etc.
  7. Fakum, thanks for getting the screenshot. I think it confirms what I suspected, because BS automatically places indicators in the "virtual screen", it can end up placing indicators where there is no physical screen. Unless the indicators have their own parameters, or maybe BS is made aware of different sized monitors, then this will be a problem. To get round this, you could place the primary screen on the left and the secondary on the right of the virtual screen, and also swap the monitors in Windows. Obviously this is now inconvenient because the Windows desktop is also swapped over, so not really a satisfactory solution in general, but would work for BS. By coincidence, this is how I have set up my monitors. I have a spare monitor which was placed on the left of the main (centre really, because there is a monitor on the right for a 2nd PC). So I extended the Windows desktop to the right which is physically the left monitor! It's pretty confusing moving windows around, but I only use these montitors for playing games. Offsetting the secondary monitor would give you the bottom or the top indicator but not both, so I don't think would help you. I nearly have my MonitorWizard going, but I think you are probably no longer in need of its modest capability.
  8. I'm not sure about that. I know what you mean - sometimes a little jiggle is added to simulate "realism". But that is usually because the model is too crude, and leads to a very linear response - which is unrealistic. Frankly, adding randomness is a cop out for the developer who has an inadequate model. If you model down to 2nd and 3rd order effects, then it should not be necessary to add randomness, because the model should contain sufficient characteristics of the real world to achieve realism without a hack. I would be a little disappointed if BS had randomness built in order to achieve it's remarkable realism, and I suspect the devs would be a little miffed if people think the result of their hard work is down to a RNG. It seems that you have never flown real (i.e full size) helis, I wonder if you have any experience writing simulation software?
  9. Yeah, I wondered about that. I finally found my comms menu at the top right corner of the second display. I think that means with the multi-monitor trick then something has to go, since the trim display is at bottom left. I call it a trick, because we are using a "virtual display" some of which is not physically there, but BS has no way of knowing that.
  10. Oh dear, you are unlucky :( That setup in the Wiki doesn't make sense to me either. It looks like a cross between a widescreen setup and a dual 1024x800 setup, either way it doesn't seem to match the description. Your numbers look good to me, at least on paper. As my prof used to say, if you can find errors in the example, you must have cracked the theory :thumbup: I've been working on a Monitor Wizard, but I've discovered that BS is sensitive to the exact order of parameters in the lua files, which seems weird. So if you are editing lua files don't be tempted to reorder lines in a more logical order! Upshot is I will have to write my own lua parser which will take a little longer.
  11. Well, the fact is you presented this reference as justification for your view, so I think you put it on the table for discussion. And definitely, the difference in size is crucial, so it is not irrelevant to state this. Have you considered that all the sims you have flown so far may actually not be very good simulations? It may be that when you simulate to sufficiently finer detail the flight characteristics become qualitatively different, and this is why BS is different? You should not assume that your experience with other sims is a good reference. My point of reference is that I work on high speed control systems (e.g for 60,000 RPM turbo pump). The behaviour of the control system becomes completely different depending on the resolution, I can tell you the control system for our 11kW pumps will not work on turbopumps :smilewink: Certainly, if you selling flight sim software you don't necessarily want to make it as hard to fly as the real thing, these are sold for entertainment purposes. If most users end up paying in "game" mode, then a lot of development effort is wasted. Frankly, I would only seriously consider the opinion of real helicopter pilots, preferably with military experience. But, without wanting to have a go at you, have you many hours flying full-size helicopters?
  12. I have a suspicion that if you don't have Fullscreen set, BS will use the desktop resolution. I can't check this right now. I am thinking of writing a "Monitor Wizard" which will help with Monitor setups, I guess there is nothing like that already? No point reinventing the wheel.
  13. I use memtest86+ for memory testing. The "Ultimate Boot CD" has this and also hard disk tools depending on the make. Alternatively you might be able to get a disk tool direct from the manufacturer. Maybe the problem is related to 2nd monitor?
  14. Are you editing the right profile? I.e. Game vs real? I also have a problem with comms menu, but can't investigate until the weekend.
  15. I think there is definitely a sweet spot where the rig is balanced just right to get the best out of games. But I think it's important to also know what screen res you play at? I have an OK frame rate with high settings even at 2560x1600, problem is with 4870X2 under XP I run out of address space and get frequent crashes. I chose a dual core CPU with 3.2Ghz core because I mainly play games without good MP support. This weekend I will reinstall under Vista64 and see if that helps with address space problems.
  16. Hi guys, I am also trying 2560x1600 plus 1280x1024. I have played with some of the examples and I had those working, not displayed right of course because my monitor sizes are different, but the relative sizes/positions were as expected. When I go to a 2560x1600 for camera view, the secondary screen displays an extension of the cockpit view instead of the Shkval. I wonder if the 2560x1600 has bust some limits somewhere? Also possible is that my video adapter is doing some autoscaling and messing up. 2560x1600 works ok on a single camera view, which is at least an improvement on what I had. I'll try to get some sample shots, though I am not sure how/where to upload them. Edit: Typical! Trying to recreate the problem has made it go away. I now have camera+shkval+abris on two monitors. Any typos throw it off, so double check everything. I did change the res on my second display to 1024x768, maybe that helped. Only snag is the low res... but at least the config is very flexible, if not very user friendly.
  17. Oops :doh: I was editing the wrong profile! i.e. changing the "real" profile then playing the "game" mode. Once I realised that, everything works as expected.
  18. DudleyAz, I have very similar problem. I have Microsoft Sidewinder 2 and CH Pro Pedals. The Pedals get mapped to pitch/raw/collective regardless of whatever settings I have in the options page. Even if they are all blank, they still get mapped. I use axis tune to verify I have the right axes. I read something about some updated DLLs, is there an official patch available? I'd like to know where the problem is before buying another set of pedals... :(
×
×
  • Create New...