dlder
Members-
Posts
259 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by dlder
-
Unfortunately, I have to replace 1 mountpoint to add that 1 mountpoint + whatever I want to add. By that I mean: to get the outer pylons, I have to add these shapes & textures to an existing mountpoint. That means, I would need to create 2 extra shapes (one for each side) and add these to the default shapes (the LAU-115). That's quite a lot of work for... less missiles^^ "Should" be possible if I can get the default shape, but unfeasible, sorry. edit: for better understanding, the marked missiles / mounts are 1 mountpoint!
-
You have to look inside the ZIP files... Yes, v2.84.1 But, I didn't try it ingame. Too much of a hassle to make the same screenshots from mid and low altitude and from the ground. I just go after the size/date for each picture (inside the ZIP) So yeah, maybe GTC actually does look better, subjectively at least. The biggest issue I have with both is: terrain.cfg is now encrypted. So... what does that mean for such mods? Thanks! Could you please add which picture is what?^^
-
Just a quick question: just for this reason, I've joined the DCS discord, dropped the log into the "dcs-log-analyzer" chat and... nothing happened. How does this work, so that I can help myself next time?
-
Thanks, I'll try to get some more info if/why the GPU Ram is really filling up. Seems weird. But I did fear that I should only set 1 pagefile, though it shouldn't matter in any way.
-
This is a bit strange imho... I have 64 GB RAM 32 GB Pagefile 24 GB GPU memory And after changing from one map to the other (I'm not sure which; from Nevada to Persian Gulf maybe?) the game crashed. The log is attached. (line 2.680) How is that possible? Could it be the pagefile layout? C = 256mb (minimum for the small Windows dump file, if an error accurs) D = 32 GB Any ideas, tips welcome! I only have 26GB of free SSD space on C, so I can't use the main drive for the page file.... dcs.log
-
Here's the full DCS.log dcs.log Will try! 1st: Mbucchia OpenXR-Pimax + OpenQuadViews 2nd: PimaxXR + OpenQuadViews (NOT PimaxQuadViews) Today I tried PimaxXR + PimaxQV and haven't had any (XR runtime) crashes so far. I'm now using the second option in the Pimax-Client. Not "Pimax OpenXR Quadviews", but "Pimax Central Priority Rendering". They really need to start providing tooltips and/or better option names, but I'm guessing this is Fixed-Foveated-Rendering? -> because PimaxQV has two 3 problems Settings cannot be adjusted and the quality is too low for my taste the 2D mirror from DCS is ultra-low-resolution which is unacceptable, as I'm recording from that XrNeckSafer is incompatible
-
Just checked the other logs: Mbucchia Pimax OpenXR Mbucchia QuadViews Log (this is the "newest", where I played with the official PimaxXR, thus no log file from the runtime like the one above): Maybe I should add, that I'm currently playing No Man's Sky in VR with the Crystal. No crashes whatsoever. None. And that's a 150+ hours... and this game REALLY stresses the 4090 because if DLSS is not enabled, you run out of video memory.
-
Hey, so, I haven't played DCS since the summer (stability issues and Su-25 TV bug). I've tried it again today and... there are a few things different now: Pimax finally has their own OpenXR it also includes QuadViews with DFR or VFR DCS too has QuadViews and EyeTracking options (for either DFR or VFR) Now, I have both options enabled in DCS, as this seems necessary for DFR to work with either Mbucchia or Pimax. But because the quality of Pimax's DFR-settings suck and - for now - cannot be changed, I am using Mbucchia's QuadViews (as well as Pimax-OpenXR). It works, though the performance seems "off". And, then this happened two times in different missions / maps / jets: As you can hear, the game itself doesn't crash, but continues. It's just the output that's borked. I guess the OpenXR runtime crashes and the HMD stops working and looses track. In "dcs.log" are quite a few of those errors: ERROR VISUALIZER (26880): xrEndFrame failed with error: XR_ERROR_RUNTIME_FAILURE There are no VR / OpenXR / nVidia specific errors in the Windows logs though! And now crashdumps of anything! If I remember correctly, Mbucchia himself said to stop using his OpenXR runtime, because it's out of date and he stopped working on it, so I switched to Pimax's own, official OpenXR. But the same thing happened again... Here's my DCS options: Here's my OpenXR setup: and with PimaxXR: And here are my Pimax settings: v1.33.01.01 Lighthouse, 120Hz, Eye Tracking enabled, Sound Standard RQ = 1.0, DFR via QuadViews and Pimax both disabled, Smart Smoothing disabled, Lock to Half Framerate enabled, Hidden Area Mask enabled
-
I just work in IT, which doesn't actually mean anything other then that it allows me to make educated guesses and allows me to do some modding if I like. BUT: I don't know nothing about textures and stuff! So, I can only manually check every file from mods vs. the games files, which I do on pretty much every update. The gist is this: CGTC has lower quality textures and also fewer textures then Barthek. That's why I prefer this texture pack. And again: I cannot recommend to mix both, but if you do, install CGTC first and then Bartheks. Caucassus Terrain hasn't been changed by ED in quite a few years, so this pack is still very relevant. Only the now encoded terrain.cfg remains a problem... That is true! But it shouldn't really affect you, if you have texture and visiblity set to max. ALTHOUGH: I have no idea how the LOD system works in this game... maybe it would be beneficial to mix both mods, but then you'd have the nasty job of manually unpacking all ZIPs of both mods and use the "best texture". And even then you have the problem, that maybe the darkness/shading isn't the same, so you have different kinds of textures between low- and high-quality. -> try both and stick with one
-
I'd really like to know: now that the "terrain.cfg.lua" is encrypted, what do we do? Can we just delete the encrypted one? Does somebody have a de-crypter, to merge the changes by ED into the mods file? Because as it stands, this file is no longer relevant.... Also: I at least wouldn't install the terrain.cfg.lua I mean, I wouldn't mix those 2 anyways, you'll never know which texture would be out of place. But to each their own. I've also been using all the tree-mods from Taz, but as it is currently, they are out of date and imho should no longer be used (just compare the files they use; ED updated some and are thus newer / don't exist with Taz's mods).
-
gotcha! Thanks again!
-
First off: thanks! Those settings get deleted, when you start DCS, but get added by the launcher (just open the launcher and don't start the game, and you'll these options in the LUA)
-
I've just flown a night mission in the Su-25T and I was not able to lock on to any ground targets. I also couldn't see any targets with LLTV (night time TV!), as the screen was completely dark. And I have "symbols" enabled, so I know where the target is located; meaning, I'm looking right at it in the TV. Only in lit areas (from flares/light bombs for instance) I'm: a) seeing the target on screen b) able to lock onto tanks But even that doesn't work all the time; I've made a quick test mission, where I also made sure the tanks a "warm" by moving them, and they aren't visible with or without lighting (fires and flare). Here's a video about that; track is also attached. The daytime TV is also way too dark and it's hard to find targets, but at least the Skval is able to lock onto targets... Could someone confirm or deny that? How are you guys doing the past 2 weeks or so? (I'm flying in VR, if that matters) su25.trk
-
Does anyone know of any updated comparison screenshots or videos? A lot of the Better-Smoke files were updated by ED in the recent patches. That doesn't mean that the official DCS looks as good or better then DCS with this mod, but it does bring up th question: is this mod still needed?
-
canopyReflections moved from VR to Graphics and is now float custom_IPD is now int instead of string The other stuff remains unexplained; like, why does the launcher add these settings (to options.lua): aircraftmode compasstape easyradar tacticalmap ... and when starting the game, they get removed again? Like those are still experimental and not yet used ingame.
-
Hm... I don't use the launcher, so could it be that some settings are only there and not ingame? I really have to cross-check the options again, but good tip!
-
So, I've just tried the mission and now it works! Kind of... Now there is another problem: the SEAD didn't kill all anti-air. And looking at tacview: the missiles hit (weren't shot down), but didn't seem to do any damage. After the 1st pass, both Su-24 were shot down by said AA. I then flew in and destroyed one SA-8 and suddenly, all AA went offline? Either there is some Tacview-Export bug, or...? Anyway, after that, the Su-25 attacked, I killed the jets and the Su-25 continued attacking (unlike before) and destroyed the last objective. The mission then continued, telling us to RTB. Second issue here: the comms text-box was in Russian; I didn't know what was said and requested, but when I had to answer via F10, I replied with something like "Roger, RTB", so I at least new the mission was over^^ <profanity>, I forgot to save the TRK.... but I'll upload a video later on and post it here, so you can see what I mean.
-
Didn't yet see any post about that... it seems the following options were removed? ["graphics"] = { ["canopyReflections"] = 1, ["difficulty"] = { ["heading_units"] = 1, ["miscellaneous"] = { ["Datum"] = 1, And I wanted to ask, what the following new options meant (they only get added via the launcher, not by launching DCS directly): ["difficulty"] = { ["aircraftMode"] = true, ["compassTape"] = true, ["easyRadar"] = true, ["tacticalMap"] = false, Cheers!
-
fixed Pimax Crystal Quadviews seems to broken after last patch.
dlder replied to tikijoetots37's topic in VR Bugs
quick update: might be that loading missions and into the plane with DCS MT is now faster? Need to do more testing... I'm still using Quadviews, but without Eyetracking, so only FVR, but it works pretty well and I didn't have to change a thing. I did have 1 crash when loading into a plane for the first time after the update (hang after "Terrain Loading Done" or what the exact message on the loading screen is), since then: stable. Maybe shaders had to be updated? dunno. Sent the crash log to ED via the prompt (does that actually help?). -
fixed Pimax Crystal Quadviews seems to broken after last patch.
dlder replied to tikijoetots37's topic in VR Bugs
Yep, same issue on my end; Crystal, OpenXr, QuadViews (why was OpenXR settings reset?)
