Jump to content

Puma

Members
  • Posts

    482
  • Joined

  • Last visited

Everything posted by Puma

  1. Not a stupid question! I had no idea either. Learn something every day. Thanks guys.
  2. I get that warning but it works regardless. Flip a switch, do you see text that matches? Start dcs, do you see a spew of text? Mine works 100% despite it.
  3. Never underestimate the power of a video card. I upgraded from a similar ATI card to a GTX 970. Not only did I now get to max graphcis settings, but I could nearly do so at 4k, which was a bonus!
  4. I'm not familiar with adaptive vsync, so you've got me there! I read about it a bit. Cool idea. Only possible thought might be: do you have aero disabled? Small chance it needs to be on so NVidia considers the windows base to be 3D. Beyond then, you are close. Adaptive sync at 75 Hz should in theory be similar to 60 even if thats all you can render, so it won't be consistent I suppose, but gotta compromise somewhere I guess. Have fun!
  5. Visibility is all about resolution, so I would like to speak the merits of a 4k display. For accuracy and tactics, I'd rather have a 4k at min settings than fancy graphics at lower resolutions. I have the Seiki 39" 4k tv which I got for $360. It only does 30 Hz, but its not as bad as it sounds and you can't beat the price. Once others come down in price, us this as your bathroom TV :) I did have a to get a GTX 970 to render, but if you can afford it, the experience is unmatched imo. Shorter term, yes, trackir should be your first purchase, and get a good zoom system in place. Last thought... labels aren't so bad. I know they seem like cheating, but real pilots don't have resolution impeeding them, so its just offsetting a handicap of the virtual pilot. I like the mods which make the label like 2 or 4 pixels.
  6. Ah ha. Now that you explained WHY you think you need full screen, we can work with you. You can use softh to do bezel correction in windowed mode. Setup will be a little painful, but for these many requirements its the only solution I can think of.
  7. you can use Helios as a mapper of inputs to outputs. So for example add your joystick as an input interface. Add dcs as an output interface. Then just drag and drop rules like "when switch 27 goes on, set eac to on and batt per off". Very flexible. You can do three way switches easily. That will be all you'll use unless you get more monitors or an led board. Just to be clear, I hope you are wanting to program non-native stuff into your warthog? Otherwise it should work out of the box where every control performs its real-life function without any programming.
  8. if Helios will ever be part of your future, start now. You can use any hid as an input and drag/drop dcs actions into it. Plus all the other stuff Helios can do like gauges. I used target ONLY to setup a key combo for teamspeam PTT. Everything else is Helios or dcs internal config.
  9. or google refreshlock?
  10. it would be helpful to know why you don't want that solution, but okay, ill play your game :) What about editing your supported modes via nvidia? Somewhere in there you can add and remove custom resolutions and refresh rates. If you could convince your video card that it doesn't support 75hz, then dcs would likely take the fastest supported mode.
  11. did you try full screen off, vsync on and windows refrsh rate set to 60?
  12. I have a set of speakers with sub and bass shaker on a sound card, and a USB headset with mic. Headset for teamspeak, sc for dcs. It would be great if I could have dcs send environment to the sc, but headset (radio, rwr, tcn, etc) to the headset.
  13. search for max fps. Its a lua setting somewhere. I am NOT sure if that translates to vsync rate in full screen mode, but its all I can think to try. failing that, disable full screen mode. I was surprised I didn't notice a performance penalty when doing so. Vsync still worked.
  14. my interested shouldn't be given much weight. I've read the manual like six times, but am stil building my pit so despite hours of test flights, I haven't flown a single mission. From years Falcon AF experience, I anticipated that a system to locate threats would be pretty valuable.
  15. I think he's trying to make it clear that the key to the solution lies in the trianglular portion of the picture. My original question was meant to be only about the syntax and the principal behind, so that's very valid. I agree that in this particular application, a-10c specific 5 points are involved and the pilots could come up with some applied name like Sam quint-markpoint-ulation, but the mathematicians would still call this triangulation.
  16. Touche! Harzach for the win.
  17. watched a video on this. Amazing application of simple tools. Love it. My random thoughts on the issue: A) why wouldn't a computer do this automatically for any threat detected on the rwr? B) I believe this should be called biangulation since you are only using two lines to locate an object in 2d space rather than triangulation which would be three lines to locate an object in three dimensions.
  18. Sounds like one is correcting for magnetic variance and the other isn't. I think I recall something about the in the manual but am at work and can't check.
  19. Live the dream. Go get em.
  20. I would be interested for the right price. Maybe a subset if that helps the cost?
  21. Invert single pin & debounce Loving DCS-BIOS so far. 2 questions: 1) Can I add a switch debouncer on an input pin? Seeing a little bounce on one of mine. 2) On my NSMP PTR switch, I have it "ON" in the "STOW" position, but this seems to be the opposite of the way you programmed it in single-pin mode. Can I invert the logic for it? I suspect I can use the 2 pin mode, but I tried with 0 as the second pin and that didn't work at all and I'd hate to waste a pin just for this. Great work, great documentation. Thanks!
  22. sorry I don't have the details, but I believe this has to do with the "render purpose" you set in the init lua during export config. Hopefully that's a lead for you.
  23. Finally getting close to a final monitor configuration. I have moved my thrustmast MFCDs onto my primary monitor because its 4k /39" so I can spare the realestate, and the performance gained by running on 1 monitor justified it. However when I set the size so the buttons align, they don't quite fill the square. Also I ahve expored my RWR and it has no background at all. I read an old post about creating a black square by using negative width/heights, but when I tried that it looked like a reverse image of some opposite part of the cockpit, especially when I panned around. Challenge, if you choose to accept it: How can I black out a rectangular part of the screen, above the "world" drawing, but below the MFCD/RWR. I would prefer to remain in fullscreen mode for VSYNC reasons.
  24. might need to run Helios as admin? Right click.
  25. oh, and yes "sync to pit" does nearly nothing. There is a good reply from gadroc why, but basically it is dangerous in case of air starts, and technically challenging for multiposition switches.
×
×
  • Create New...