Hunter Joker
-
Posts
981 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Hunter Joker
-
-
10 hours ago, =475FG= Dawger said:
So you want the AI to run the MMS instead of hold a perfect hover while you run the MMS and shoot off weapons and the like?
Exactly, so I can choose...Once I can choose to be only the pilot (I prefer piloting than shooting) and sometimes could I go Copilot...
I didn't see anything bad if You can choose...nobody oblige You to use it... didn't it? -
Never used, I fly with two stick (one for pilot and one for copilot) and a collective. Doing all the stuff alone and, I must admit, a bit tired of it. I prefer piloting so no chance for the AI pilot but having an AI copilot that can take care of a bit workload from the pilot could be a pleasure when You didn't have a second player. No necessity that he speak or other fancy behavior, could be simple like Petrovich or George.Please no.
I am happy to have a competent and non-annoying AI pilot grab the controls in the Kiowa. No need for anything resembling the “clown”.
Inviato dal mio RMO-NX1 utilizzando Tapatalk
-
Could we hope to have a Jester like copilot one day?
Inviato dal mio RMO-NX1 utilizzando Tapatalk
-
2
-
-
6 minutes ago, GrEaSeLiTeNiN said:
Mine is a Warthog, but I'm pretty happy with the mapping so far. Hope it's of some help. I go with what works and is functional. When I am undecided on the functions for a particular button or switch that involves a modifier, I normally go with what is less likely to conflict in the heat of battle. Sometimes neither option is better but a matter of getting used to one.
Thx, I will check it.
-
I'm a bit in trouble in find a good mapping for my HOTAS for the Kiowa.
I mapped something, then fly and found that I need other controls, remap, fly again and found that probably the first set is more useful...confusion...a lot of confusion
There's some one that have a decent setup that could be shared here? Even if You have different devices, eventually I can adapt it.
Thank You.
-
Found this, a more complex review will follow.
Inviato dal mio RMO-NX1 utilizzando Tapatalk
-
2
-
-
Non serve più ormai. Ciao.Ringrazio veramente tutti per il supporto ma a questo punti vi faccio un'altra domanda: Nel tutoria si dice che bisogna inserire sulle delle proprietà la stringa "force_enable_VR-force_OpenXR". Ora, scusandomi già da adesso per la mia incompetenza, con il nuovo launcher dove trovo le proprietà dove inserire la stringa?
Inviato dal mio RMO-NX1 utilizzando Tapatalk
-
Il problema era nell'errata implementazione dello standard OpenXR da parte di ED ed a carico del Quad View. Hanno seguito finalmente le linee guida ufficiali e hanno messo a posto. Prima o poi qualcuno prenderà in carico lo sviluppo dei tools di MBucchia (Pimax in primis) visto che attualmente sono l'unico modo per far girare su visori di fascia alta titoli come DCS con prestazioni più che accettabili.Occhio solo che il supporto su OpenXR Toolkit è terminato, e in realtà recentemente a qualcuno ha dato problemi.
Quindi detto che non ti conviene usare steam vr, userei nativamente il supporto openxr andandoti a installare pimax xr. fine.
Altra cosa, se il problema ti è arrivato solo con quella build, ci sono due "test" che puoi fare:- Portare il polling rate del mouse a 500Hz qualora fosse ora impostato a valori più alti (di default mouse da gaming tendono a impostarlo a 1000hz)
- Disabilitare il modulo supercarrier (se lo hai ovviamente)
Inviato dal mio RMO-NX1 utilizzando Tapatalk
-
58 minutes ago, Otto pallen said:
rispolvero questa discussione chiedendo a chi è più studiato di me un aiuto o un consiglio su come risolvere il mio problema, ho giocato con dcs in modalità vr da ormai diversi anni. Da questa estate però purtroppo, più o meno da quando è stato rilasciato il CH47 e relativo update, non riesco più a giocare, o il frame rate è ridicolo, o si blocca tutto, col fatto che le temperature erano molto alte e indossare il visore per parecchio tempo era non molto salutare ho lasciato stare ma adesso che ho provato di nuovo... nulla, tutto come prima, anzi peggio.
Utilizzo il visore per giocare anche ad altri programmi tipo Assetto Corsa o IL2 Great Battle ma li non ho nessun problema e viaggio con frame rate oltre i 40/50fps, comincio a pensare che il signor DCS ce l'abbia con me
. Io ho sempre utilizzato nel launcher del Pimax SteamVr, potrebbe essere quello che mi incasina tutto? Ho provato anche a far partire il gioco con settaggi molto basi ma i risultati erano simili.
questo è il mio sistema:
CPU: I5 10600K, RAM: 64GB, GPU: RTX3070, VR: Pimax 5KSuper.
Lascia stare Steam VR,
Con il Pimax vai di OpenXR Toolkit, Pimax XR, Quad View.
Qui c'è una guida, un pò datata ma ancora valida, segui questa passo passo.
Ciao.
-
1
-
-
54 minutes ago, some1 said:
12nm is when you move the stick diagonally, so power of two motors combined. But even 9nm is plenty for a stick without extension, that translates to around 3kg max force on the grip.
Do You think that with a 200mm extension will be enough anyway?
Cause for me flight without extension is impossible...Thx.
-
1
-
-
14 hours ago, BIGNEWY said:
correct FOV submission, the team have tested and it is looking good.
thank you
Hi, can You consider to release it as soon as possible as a hotfix, so detached from the rest of the others fix, cause from last patch VR is pretty unusable and I didn't even was able to see the new map from Friday...
Thx. -
Hi, can You explain me apart copy over the new dll what must to be do to switch to new DLSS version? I now that there's an executable, a DLSS Tweak/Switcher of some sort...thx.
-
So OpenXR Toolkit is not needed to run DCS with a Crystal? Only PimaxXR e Quad View?Regarding the breaking of quad-view. I downloaded the file provided by Sandboxcode and swapped it out. I'm on a 13900k and 4090 and previously, with a superb image, I none the less got the micro stuttering/jerking of objects on the ground as I looked out the cockpit left/right at low level. It would be apparent to a diminishing degree as I climbed higher.
With the file-fix in place I went into my game, no jerky foveate box (but visibly working), fired up Mig21 Free Flight and...WTF! Not one iota of jerkiness. Smooth as silk, flawless. I don't get it...did ED fix something else while also breaking the other bit?
I run the Pimax client, Pimax-OpenXR, Quad View and QV Companion, no XR Toolkit (don't see any need for it).
Serendipity in action. Though now I'm scared the fix on its way from ED might bring back the jerkiness. Right now it's pure 100% perfection.
FWIW.
Inviato dal mio RMO-NX1 utilizzando Tapatalk
-
Just to be clear, probably You misunderstanding the meaning of my words (helped by the fact that my English is bad and sometimes I write English thinking as I speak in Italian so sorry for this...).Edit: I shouldn't be ranting so I'll edit my post. Bottom line: please start holding the right people accountable instead of this false impression that you have.
ED literally has a blatant BUG in their code.
THAT is the problem, existing since Day 1 of DCS OpenXR support. Reported to them on many occasions in the last year and a half.
The meaning of my post was that, having the only one people who make high end headset working with acceptable performance under DCS creating a series of toolkit that nor ED or headset manufacturer show to be able (or want) to do, leaving the development and support of these tools is a big problem for us, the players, who spent and invest thousands of dollars in software and hardware. Not absolutely a Your problem nor that this problem was caused to us by Your quitting. I hope these time I make clearer my statement.
Inviato dal mio RMO-NX1 utilizzando Tapatalk
-
I hope in a fix at least on Monday...at the moment I can't even test the new patch and the new map that I bought cause of it..
Inviato dal mio RMO-NX1 utilizzando Tapatalk -
Can You write here how to substitute the dll? I know that apart overvrite it You must execute sono batch/executable...With mine, I just:- Disabled 'Allow use of the eye tracker' in PimaxXR Runtime
- Lowered the DCS resolution down to 1440p from 4K
- Updated the DLAA/DLSS nvngx.dll with the latest version (https://www.techpowerup.com/download/nvidia-dlss-dll/), and switched from MSAA 4X to DLSS Balanced.
- In QuadViews raised the Focus Size from Horizontal and Vertical up from 25 to 30, and is quite playable now at 65-80 fps.
Inviato dal mio RMO-NX1 utilizzando Tapatalk
-
For me with a Crystal disabling DFR is a dead sentence, so I will wait for ED fix...I have the same issue.
I had to revert to the more stable openxr Toolkit and disabling the DFR
Inviato dal mio RMO-NX1 utilizzando Tapatalk
-
Quad View simply is mandatory.
Inviato dal mio RMO-NX1 utilizzando Tapatalk-
1
-
1
-
-
So is completely bugged, not a refresh/fps problem.
Inviato dal mio RMO-NX1 utilizzando Tapatalk -
Quad View, a lot of users are reporting that.
Inviato dal mio RMO-NX1 utilizzando Tapatalk -
Didn't try at 90, actually I'm a 72Hz 72fps locked. If it work at 90hz /90fps for me is still a big problem cause with all maxed out I could achieve solid fps only up to 75/78fps...
Inviato dal mio RMO-NX1 utilizzando Tapatalk-
1
-
-
The problem is that MBucchia didn't develop/support it anymore... A big problem...
Inviato dal mio RMO-NX1 utilizzando Tapatalk -
Same for me, my Pimax Crystal make exactly the same. Now that MBucchia didn't develop it how could be solved?Quad views through PimaxXR just broke for me after the new DCS update that dropped a couple of hours ago. It looks like its tracking my eyes and where I'm looking but is shaking violently in the box where the Higher res part is supposed to be.
Inviato dal mio RMO-NX1 utilizzando Tapatalk
-
1
-
-
It seems also Pimax Crystal affected.
Inviato dal mio RMO-NX1 utilizzando Tapatalk-
2
-
1
-
Wishlist: "Jester like" copilot
in DCS: OH-58 Kiowa
Posted
Inviato dal mio RMO-NX1 utilizzando Tapatalk