Jump to content

SYN_Mugue

Founders [premium]
  • Content Count

    53
  • Joined

  • Last visited

Community Reputation

17 Good

About SYN_Mugue

  • Rank
    Founder

Recent Profile Visitors

294 profile views
  1. Not trying to poke you in the eye here, SharpXB. But actually I believe most of the camo at the time, had more to do with hiding the planes on the ground from being destroyed, than blending in with forests while in flight. But your point is taken. And I do hope someday we get actual HDR rendering. Cheers
  2. I find it interesting that some of you guys are claiming that spotting with 4k is easier. This is not my experience at all. And low contacts are the worst. For me, on my 32" 4k monitor which is about 12" from my nose, the contacts are rendered so small it makes them nearly impossible to see. The difference in size of rendered planes and objects between running 3840x2160 or 1920x1080 seems dramatic to me. There is no question that 4k wins the eye candy test. And a lot of the times I fly around in 4k just because it looks SO good that I don't mind being slaughtered by unseen foes. But if I want any kind of passable SA in multiplayer I need to run 1920x1080. Otherwise, my squad mates are calling out contacts all day long that I just can't see. It will be fun to see what changes the new view system will make.
  3. " Please test if the text doesn't seem to fit in the window. " That works perfectly for me now. Thanks Vander. M.
  4. " I can remove the fixed height and width values in the next version so you can extend the window by dragging. " I was wondering if you could do this somehow, but not wanting to burden you, I never asked...Because on my 4K monitor with up scaled fonts in Windows, this tools is unusable without resetting my font size(= not optimal). Labels don't fit on the buttons and only half of the page shows in the window etc... So, it would be great if this solves the problem I have. Good luck and Thanks. M.
  5. That P-38 looks fabulous! Can't wait.
  6. Thanks for the quick reply Jason, That was the answer I was hoping for. Have a good day.
  7. I notice that in the Launcher, the check box for, peer to peer or web download is gone. Can I ask which system we are left with? As I always picked "web distribution" because of my personal dislike of torrents in general, and the soaking up of my bandwidth. Thanks.
  8. The mouse scroll wheel does that for me...Don't know if that helps?
  9. I also support the idea of adding separate L and R key binds for feathering props. Currently it's very clunky to do, during the usually stressful conditions that require it, imho. Hope we can get it one day.
  10. Well Luke, my friend, maybe it isn't that simple... --------------------- Here's my setup System: ASUS Sabertooth x79 MB, i7-3820 @ 4.32GHz, 32 GB RAM, GTX 1080, Window 7 64bit pro Peripherals: Logitech 810 keyboard, Razor Naga mouse, G940 ffb stick, MFG Crosswind V2 rudder pedals, TM Warthog throttle, DSD Race King & P-series button boxes, Saitek throttle quadrant With the above setup, everything works fine in BoS, no problems. -------------------- Now on to my issue... To that setup I'm trying to add a second Saitek/logitech throttle quadrant(just arrived) and another DSD P-series button box I'm going to morph/hack into a trim control box.(still to come and likely a whole other problem) Here's the rub...When I plug in the new throttle quadrant, Windows recognizes it (and everything else too) and all functions correctly. In Windows, (and in DCS too) so I know it all works. But when it comes to BoS I've got a strange set of issues. First: Mapping the axis' and buttons in the game as per usual.(to my existing profile) Appeared to map normally. Ran a quick mission to test my new engine controls, and I got nothing from the new axis' yet the buttons on it did work. Then I looked at the axis tuner function in game and sure enough no axis movement. So, the axis IS mapped in the games control menu, but not working/recognized when the game is running. Strange I thought! Second: Then I tried, backing up, then deleting the 'input' folder. Thereby resetting things and carefully remapped every control... This time around, everything mapped and functioned in the control setup menu. And all buttons and axis worked in game too. Great! Or so I thought...When I started a mission and took off, I discovered that I had lost all Force Feedback from the pitch axis on my G940. (no forces or shake) Roll axis was unaffected and worked like normal. At first I didn't panic cause I've had, and know others that have had, ffb glitch in BoS and RoF before. Usually adjusting, applying, then readjusting and re applying the force levels in game will sort it out. And/or a game restart or system reboot too if needed. Tried all that obviously, but no joy.(stick force, ha ha) So then I made a virtual controller out of both of the saitek quadrants using vjoy and joystick gremlin. (Thinking that perhaps I had exceeded the maximum number of controllers allowed in BoS.) Once I got that working, I mapped everything again in a freshly reset input folder. Again everything works but the ffb on the pitch axis. :/ What in the name of Gods Gray Earth could be causing this strange behavior? Anyone else run into this problem before? Any thoughts how to solve this short of me throwing my new quadrant out the window? Any help or black humor would be appreciated at this point. Thanks.
  11. Is there a hard limit to the number of controllers the game will recognize? Or am I limited only by my OS and hardware? The reason I ask, of course, is...I seem to collect controllers like a dog collects ticks. And I wondered if I can have the new toys I've ordered plugged in and working too. Or do I have to make a choice about which ones I keep? In the end I guess I'll find out, just hoping someone knows so I can plan ahead. Thanks, M.
  12. WOW! That IS a significant improvement! Nicely done.
  13. Thanks for extending the draw distance of the trees. This really made a huge difference in how our virtual world looks. Keep up the good work! S! PS: the Spitfire is pretty nice too.
  14. No problem HarryM, I wasn't offended, it was just a very small joke. Cheers!
×
×
  • Create New...