-
Posts
499 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LOW_Hitman
-
Which textures do you mean? Ground, Cockpit? Because having the cockpit textures lower than high makes them unreadable in VR
-
i tried avc264 for a while, what i saw is that after a longer flight (for example return to airbase (syria)) the textures are getting blurry. When i switch to the external views the plane is blurry. Running HEVC 265 since yesterday, not have seen any blurry textures so far, i'll keep testing.
-
ich glaube die meisten heutigen Rechner stehen hoffentlich nicht mehr unter dem Schreibtisch dank RGB Beleuchtung Der Verbrauch ist zum Teil wirklich krank da stimme ich voll und ganz zu. Ich muss aber ehrlich sagen das ich dennoch positivst überrascht bin vom Wechsel von 3070 auf 4070. Ich hatte wirklich schwere Bedenken wg. Lautstärke und Verbrauch. Der Leistungsgewinn ist jedenfalls gewaltig und jetzt läuft DCS in VR besser und flüssiger als eine aktuelle "Weltraumsimulation" non-VR
-
Meine RTX 4070ti super liegt zwischen 285 bis 320 Watt (Asus TUF OC). Wobei ich sagen muss im Vergleich zu meiner Zotac 3070ti ist die Karte um mind. 50% leiser bei einem gewaltigen Leistungszuwachs.
-
F14 VR - VDI screen not usable in MT Version
LOW_Hitman replied to westr's topic in Bugs and Problems
Maybe only an MT version issue as far as i know AND thnx for your help!! -
hab mal vor langer Zeit ein YT-Video gesehen - dort wird empfohlen den Treiber runterzuladen - die Karte zu tauschen und den PC dann ohne Netzwerkkabel zu starten - dann sollte Windows da nicht dreinpfuschen. Hat bei mir jedenfalls immer tadellos geklappt
-
F14 VR - VDI screen not usable in MT Version
LOW_Hitman replied to westr's topic in Bugs and Problems
Thnx Flappie, restart the mission is working - but thats not a fix. -
F14 VR - VDI screen not usable in MT Version
LOW_Hitman replied to westr's topic in Bugs and Problems
After all the last patches the VDI within the F14 module isn't working correctly. I always need to restart the mission to make the vdi working. First start = black screen and no camera picture. Please ED fix this! This issue is known for a year or something! -
Ist es möglich mit dem HMD z.B. in der F16 od. F18 ein Bodenziel mit dem HMD zu erfassen? Spich für den Beschuß mit einer Maverick z.B.? Danke Euch!
-
By default it's ctrl + F2 (also other F-keys to toggle and so on) Please check if "disable Toolkit" isn't crossed out Mention that you have to be inside of DCS to make the menu work - for example within the game menu or in a plane
-
I've seen no issues whilest using pico connect. After a few days of testing i think AVC H.264 is working best for my system. I didn't see any optical differeces when using H.265 Also the picture seems to be sharper when using AVC H.264
-
iam using pico connect, steam vr, pico connected via usb 3.0 cable - is it the same behaviour or only when using VD?
-
Hi all! using a Pico 4 and iam not sure about the Codec-Setting within the Pico Connect software. There are 2 options: AVC264 or HEV265 What is the difference, and what is the better solution for DCS? I read that AVC is an older codec - but no details whats correct and whats incorrect. Whats your preferred setting and why? Best regards
-
Nvidia Einstellung - Cuda Sysmem Fallback - Eure Erfahrung damit?
LOW_Hitman replied to LOW_Hitman's topic in Deutsch
Ich werde es mal on/off testen - bin aber überzeugt dass das sicher von der Anwendung her unterstützt oder "optimiert" sein muss/sollte wie Du sagst. Wäre halt gerade in VR in DCS ein gamechanger. -
Missed FPS Target on Batumi when facing one direction
LOW_Hitman replied to Glide's topic in VR Bugs
how can you increase the gpu load? higher settings only? Is this "moving" workload from the cpu to the gpu? - have you ever tried cuda sysmem fallback on/off in this situation? -
It was a software issue within Pico link, after updating to pico connect the issues was solved.
-
no - i9 9900k so its very strange - changed to only 5 cores instead of 8(16) and now its way better. No chance to play via wifi - no second router and i prefer the cable solution
-
Iam using my pico with cable so VD is not an option. Yesterday i tried the "affinity solution" i'll test it further if it solved the issue. F16 is runnin smooth since i have changed this setting.
-
Some absolute strange thing... i tried a setting after watching a jabbers video. So i've set affinity to only use 5 cores. With this setting i was able to fly a f16 mission with nearly 70fps instead of stutters.. i will try it in a few other mission.
-
Iam using pico connect and since i updated from pico streaming assistant to connect its unplayable. Iam afraid its a pico software issue. Played syria with nearly no stutters before - same settings and now its a stuttering show. I can share my nvidia settings - the game settings are set good iam sure - other modules and maps are runnin clean and at a range between 60 - 80 fps
-
tried, it's not working. Syria is unplayable with my pico 4. 10-15 fps - also strange the F14 and the F16 modules are both not playable on all maps. it's so weird... With a SU33 for example i get 70-80 fps at caucasus for example.
-
sorry for that maybe dumb question but can i use VD whilest using the cable? It's a tool for a wireless connection isn't it?
-
Iam not using VD - only SteamVR and Pico Connect via USB3.0 cable. So i can only set the resolution from high to ultra within the pico software. Ill give it a try