Jump to content

majapahit

Members
  • Posts

    1712
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by majapahit

  1. My DCS NOTE: all is OFF (but PD 1.1 to trigger HP resolution) , this is for Dogfighting / BVR ! (All this not my finds, all from the forum)
  2. 1- between the eye the shiny little square 2 -find download NVidia Profile Inspector (or the DW version, same) attached
  3. 1. black sticker the sensor 2. NVidia negative LOD - 'clamp' ON 2a. - Transparancy Supersampling xxxxxREPLAY_MODE ALL (to enable NEG LOD BIAS) - Texture filtering LOD Bias DX '-1.375 No more DCS wave shimmer around Stennis, YMMV
  4. FYI need Always had problems installing Kneeboard Builder having custom directories for both DCS and the Saved Games had 4 blank pages that were the auto-mission briefings supposedly did some thinking copied from the KneeboardBuilder program install directory e.g. ".. <files>\KneeboardBuilder" the directory " .. <files>\KneeboardBuilder\Kneeboard Groups\General DCS World Kneeboard\Dynamic Mission Briefing\LuaPreviewImages" has the 4 lua files for generating the mission data pages and copy/add this to "xx:\Saved Games\DCS xxxx\Kneeboard\ thus creating "xx:\Saved Games\DCS xxxx\Kneeboard\LuaPreviewImages et voila 4 mission data pages show again
  5. I noticed, uninstalled, reinstalled, no joy, if you can fix it, please, great mod
  6. HP Reverb might be the sales hit HP did not expect (they didn't, they expected all VR manufacturers would be offering 4K by the time they did) and they're coping with up-scaling production perhaps.
  7. I often at startup lose Forward_Backward-axis with HP Reverb especially when held still for a while. I used to restart Reverb accompanied with a lot of harsh words, but I found I need to rotate/left right MORE than 180° and Forward_Backward-axis kicks back in. This can even happen when one entered the cockpit, don't just look left/right, look left back / right back and it will reset back in - in my case -. At night it helps if I have 1 bureau lamp on full on my right, for contrast and orientation I presume.
  8. in WMR say 'flashlight on' and a horrible B/W pic-in-pic appears from one of your tracking camera(s) .. supposedly
  9. Is what I do with the HUD
  10. If there was / is no stated SATAL 2019 rule as conceded here by Moltar himself, thus there can be no ban, for that seems rather illegitimate, for such are the common rules of society. No punishment without a rule. You can or might want to disqualify results and rematch I'd opine, after consulting the parties involved who have standing, after which jointly there shall be agreement on to be established new rules.
  11. I'm reading this thread in utter amazement. YOU guys behave like bloodthirsty morons. It's a computer GAME. If you don't like a result because of whatever, and if the allegations concerning this are in any way disputable, simply annul the result and replay the match on corrected settings. What does that cost you .. couple of extra hours & couple of dollars in connection time .. and the opportunity to a new challenge. Grow up.
  12. With VR you can move one's head 'outside' of the glass, and that looks way better.
  13. you sure? I think I saw a difference, because I had to tone it back down also.
  14. the tool fpsVR (4 USD Steam) you can bump up RGB, fixes Reverb bland colors
  15. I looked at the module icons on the bottom of the DCS start and moved the slider of all settings, does improve - somewhat - does give you a headache, so go slow, then figure out what happens. You're looking to find the 'comfortable sweet spot' which is a lot easier to find on a static page than in a cockpit flying, it's rather obvious. 2cts
  16. Switch LTWS OFF and see what's really there. Otherwise you can only lock for which you have track. In particular a problem if AWACS is shot down (good teams do that). Online pilots know this so on PVP servers, thus on a bad (or perhaps good) night, a majority of pilots might be hiding. If you're a team fly staggered and make the front pilot bait.
  17. I have this hunch Devs considered AACQ as a 'default milestone - good enough for now -' and went on to develop the F16. If only AACQ worked as it prob does in real life, as in actually working as a tool and not modelled halfway to theoretical spec, so not switching to tracks 30 of 60 miles away that would have been actually a good consideration, but now it’s not. Wags said about Mini-updates devs will develop SPOT mode starting december, let's see if that works, a - wider - locking beam to look around without the faulted ‘automatic’ AACQ and beyond LACQ (10nm), and if they can adjust all these 'radar is thinking for a second on the wrong bloody track, tough luck' nuisances, which are quite the disadvantage to fly merged, who knows we can actually be on par and defend 27’s IR locks (with 9X and we be in an advantage then).
  18. Use the helmet (is prob what the devs are thinking how urgent this is)
  19. Radar "SPOT" mode yeeeeeesss, finally
  20. Look F2 Position with lowered launchbar, connect Check if this raises the trust barrier ok Back inside with F1 Look around outside and find a line or spot to remember where exactly you are Remember how you find this spot Or, do Ctrl-F1 'HUD only' position yourself with F2 in F1 'HUD only' look down and see where you are.
  21. Lately on a PVP server, about 10 flights staggered 35-100nm, switch LTWS off, they all disappear. This is exceptional of course, but does proves a point what sometimes can happen. And yes I climb to 16k alt to not miss anyone. The problem becomes a nuisance when one cannot LSS if no track shows, no lock until track, you have to wait, you lose a second, that's one precious second. Worse in ACM. You cant lock, for, I suspect, the code is busy calculating if a track can be generated, which it cannot a lot of times for one is too close and moving about too fast, and you lose very precious seconds or one depends on luck and chance to either eyeball the bandit and create a helmet lock, but that's too little too late in rather random circumstances, I'd say. Which is sad.
  22. Actually, switch LTWS off and see what the DCS F18 own radar is actually seeing, which is abysmally little. And I also have a dark suspicion the DCS F/A-18C radar is modelled by the devs, trying 'as how a real F/A-18C' radar would operate according to theoretical (!) 'modelling', the DCS F18 somehow probably performs worse than the real life F/A-18C, or at least considering that in theatre, will have continuous feed from actual live human AWACS always in their headset. And on top, puts the DCS F18 in a disadvantage to other DCS modules with simpler radar modelling, that will have 'a lock is a lock' logic. But perhaps I'm just pissed off when I lose a lock on aircraft(s) heading full afterburner my way at 15k or worse 32k altitude, or one cannot lock at all whilst - some - red flights seem not to have that problem, not in the same way at least. F18 High fidelity modelling being a disadvantage because of practical under-performance consequences making for a disadvantage in a PVP theatre vis-à-vis other modules, that would be sad, wouldn't that be.
  23. Actual F-18 pilots don't seem to complain about the throttle control in DCS F-18.
  24. I always use manual (Override). In RL I think I read somewhere auto is switched on only in ferrying when enjoying the scenery and in case of an ambush. Entering an active theater on Auto would be wasting c.measures.
×
×
  • Create New...