Jump to content

MAXsenna

Members
  • Posts

    13401
  • Joined

  • Last visited

  • Days Won

    11

Everything posted by MAXsenna

  1. There are kits out there. Sent from my SM-A536B using Tapatalk
  2. Ah, I'm on my cell and couldn't zoom in far enough, so I went by the text, which said DLSS. [emoji58] Too bad it doesn't work for you. Have you read through the various DLSS/DLAA threads? Maybe those can help. Sent from my SM-A536B using Tapatalk
  3. MSAA (x4) has a lot of shimmering for me, while blurry instruments have never been an issue. I've opted for DLAA. Much less shimmering and no blurry instruments at all. Sent from my SM-A536B using Tapatalk
  4. Can't wait for 'Nam for Paradise Lost II and more...
  5. Awesome! [emoji1303] Sent from my SM-A536B using Tapatalk
  6. No worries. There's another thread about a user that can't get into a mission if OpenTrack is running with AI Track. I would follow @LucShep's advice and try an older version. Best of luck!
  7. Have you given DLAA a shot? I find it way better than MSAA and don't get too much smearing. Sent from my SM-A536B using Tapatalk
  8. Hi @Bernhard Strobel When you write "F10 card", I assume you mean the F10 map. If you bring up your kneeboard and lock it with RShft+K, and then browse the pages, where you have a fully functional map, and you can mark your position to see where you are. If you have an extra screen you can also use the free Moving Map application to display where you are in real time. For Android/iOS the app charges a small fee. Cheers!
  9. Ho Eagle! Not at my computer, so I can't provide any screenshots. But, open the Controls Settings, and the select the TM TPR column and click the axis tune button at the bottom. Then you check use as slider checkbox on the right, (and you may need to check invert as well in some modules). Do this for both toe brake axes, and you should be all set! Cheers! Sent from my SM-A536B using Tapatalk
  10. Have you set it up as a slider in the axis tuning? Never mind, I see what's happening now. And that's how it's supposed to be. I'm sorry, I don't intend to sound harsh. Why do you expect a different result? Your physical controllers controls the virtual controls in the sim. I'd be seriously frustrated if it didn't work like this. Check the "sync HOTAS at mission start" checkbox in the General Settings, and make hot start checklist for your physical peripherals. That's the answer to your last paragraph. To prevent it happening, make sure physical positions are set correctly. Cheers!
  11. Clearly a case of loat in translation as the Moza representative doesn't know what cockpit means while they probably are referring to the software. Guess this thread is done. Sent from my SM-A536B using Tapatalk
  12. Ah, never seen that error. But that's probably it. It feels nose heavy because the stick is still forward of the trimming point. Might want to ask in the VPForce Discord. DCS can't talk properly with the base is my guess. Sent from my SM-A536B using Tapatalk
  13. Quick question. Does the stick move in the correct direction when trimming? On my MS FFB2, I always need to swap the axis under FFB tune in the Controls Settings, and in some modules I had to invert the X and/or Y axis. Sent from my SM-A536B using Tapatalk
  14. OP states Vjoy isn't installed though. [emoji848] @Draken35 have you EVER had Vjoy installed and and added a virtual joystick? If yes, it has to be removed from the Windows device manager, as an uninstallation of Vjoy will not remove it. If no, do you have any other FFB devices connected? Like a racing wheel? DCS ain't fond of that. Cheers! Sent from my SM-A536B using Tapatalk
  15. Probably. Maybe the new weather effects did off with it. Sent from my SM-A536B using Tapatalk
  16. Ah, right. I didn't watch the video yet. Sent from my SM-A536B using Tapatalk
  17. Hmmm... [emoji848] Maybe I should try it, while I've never had any issues with my MS FFB2. Sent from my SM-A536B using Tapatalk
  18. I had to do that myself! So I knew from personal experience! [emoji1] Took quite some positioning to get it right. I did use the OpenTrack view to watch for overlaps. [emoji6] Sent from my SM-A536B using Tapatalk
  19. You must reposition the angle of the camera and the clip. This is especially true with large screens where the camera is high up. Sent from my SM-A536B using Tapatalk
  20. Slaw Rotors with a damper here. No curves and no deadzone.
  21. Did you have a look at this?
  22. Hi, didn't see this before now. What issues and what thread? Cheers!
  23. You say it crashes, or does it just hang on loading the mission? What happens if you you exit OpenTrack while it hangs? What happens if you disable AI Track? Can you paste your DCS.log here? Sent from my SM-A536B using Tapatalk
  24. What happens if you disable AI Track? And, OpenTrack crashes from time to time for me. And I can always restart it or start after I've started a mission in DCS. Are you saying DCS hangs if OpenTrack is running? What happens if you start a mission and then start OpenTrack after the mission is loaded? Sent from my SM-A536B using Tapatalk
  25. Yes, too bad it didn't work. What version of OpenTrack are you using? Sent from my SM-A536B using Tapatalk
×
×
  • Create New...