Jump to content

nephilimborn

Members
 View Profile  See their activity

  • Posts

    75

  • Joined

  • Last visited

 Content Type 

Everything posted by nephilimborn

  1. nephilimborn
    For a separate reason (BSOD) i recently have tried 120hz locked to 60 (no smoothing); it definitely removed the stuttering esp from 20degress+ left/right in ah-64d on the syria map, however it appears a bit blurry for some reason that i cannot technically explain. Normally i can achieve a fairly smooth experience with other airframes on the syria map, however not with the ah-64.
  2. nephilimborn
    This week I began also experiencing pretty much the same issue as described in this thread ('the dreaded "DX device removed" error') along with windows BSOD bugchecks as analyzed by windebug below • 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred. • FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function • MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys Followed the advise here as well as updating to the latest Nvidia drivers (NVCleanstall). Sofar so good, however i also noticed much less crazy spikes (the resulted in BSOD-bugcheck) on mission load by also following your advice PP 120/half-frame-rate (although it seems as if moving terrain is now a bit blurry - might be me imagining that)
  3. nephilimborn
    Also went in manual...was so nerve racked just trying to keep myself in the correct horizon while flying the mission in the black that i actually & idiotically lined up my carrier landing at the wrong end of the carrier! Did not notice until i activated the NVGs, re marshalled and almost became a 'Seacat' (BTW love that term); misjudged the glide-scope and wiped out during the landing. I definitely DO NOT have the right stuff!
  4. nephilimborn
    Apologies, i am an idiot - i neglected to turn on the internal lights during case III launch so the deck crew could see my salute, and also neglected to flash the external lights...mission works just fine now
  5. nephilimborn
    Automated startup to quickly (skip INS alignment) taxi out of the way before the S-3 taxies in front worked for me. Waited for S-3 to launch, then taxied to cat 4, however unfortunately i cannot launch even when 'saluting'...this is after successful responses from the checklist and a 'ready to go' confirmation from the pilot. Tried both radios on channel 6 but no joy.
  6. nephilimborn
    Apologies, focus was a poor choice of word...meant blurry movement. I think i have a small defect in the lens but that is separate topic. I followed your advice and adjusted DCS and PPlay settings for a stable 72hz - this turned out in the end, for my use case, to be the best experience. Thank you!
  7. nephilimborn
    I seem to recall instant action missions (e.g. silkworm Persian Gulf) and user files missions defaulting GBU laser code to 1688, it seems now this default is some random 6digit number (documented in Kneeboard). LANTIRN TV display cycles between valid codes, however cannot sync. Is this a side-effect of the new fusing in DCS?
  8. nephilimborn
    Good day all; received the PCL a few days, previous DCS VR experience with Q3. Struggling to find settings that mitigate the focus issues i seem to be having with PCL. OpenXR settings via the new PPClient (QV quality, Max render res, 72hz) DCS settings are generally as advised on the DCS forums with max FPS set to 77 (10% headroom). I have noticed others mentioning that 120hz locked to 60fps via the PP client is a better experience and will try that out tonight, however curious what the community here has experienced.
  9. nephilimborn
    A retrospective to close out this thread...and a big thanks to both @kksnowbear & @LucShep for your experienced help & insight in resolving an issue that was plaguing me for months! It has now been 1.5months and no black screen, 100% fans events. The resolution included the following actions Root cause: Rerouting PCIE 12VHPWR cable, eliminating the 15mm 180degree bend with the introduction of the thermal grizzly wireview Mitigating factor: High power draw exacerbated the above cable issue, undervolting advice & guidance mitigated the occurrence however has long term value for me in terms of TDP & PSU capacity (at load i am near 80% with a 1000w PSU). This is esp useful for me now as i have recently upgraded from a Q3 to PCL and the GPU demand is significantly higher for significantly longer Other: Eliminating GPU slot sag with additional supports This forum thread helped me see the forest thru the trees; i was too deep into the issue and clouded by frustration and pc hardware inexperience.
  10. nephilimborn
    Hi all, just received PCL yesterday...my previous experience is the Q3 in DCS. Have the following set in PPlay (attached)...my ignorant question is with both QV and FFR selected in PP, what is the effect? I am assuming the PXRuntime is requesting QV from DCS ... BTW, love the high res and color clarity of the PCL, however do not care for the lens-apparent? barrel effect nor the inconsistent focus, blurriness outside of the small sweetspot - as much as i hate meta, the edge2edge clarity of the pancake lenses seems superior or maybe i just need to get use to Pimax VR. Anyone else with a similar experience?null
  11. nephilimborn
    i used guns on the mobile launchers and that worked for me.
  12. nephilimborn
    Okay, ran the mission again 4 times last night. After review of the scripted lantirn targeting and weapon view at drop i am convinced the wrong bunker is getting lazed, have also ensured no masking is occurring during bomb drop. To progress the mission trigger i instead manually (CCIP) dropped bombs on the north and south bunkers (this took 2 bombs each to shack the scuds), then used the guns on mobile scuds. This worked and allowed me to progress the mission. On the helos, i found that i could take them out reliably with sidewinders if i lead above and ahead (ahead of flare countermeasure dispense) and at no more than 1.2mile distance. I took both out quickly however had to fly 180degress for ~5mi for the mission trigger to direct me back at the remaining helo (which i had already taken out); this was weird as a single helo showed up on radar however was not painted...once i flew to the ghost radar contact, another mission trigger fired allowing me to RTB or tank. After all that i could never get the airfield carrier break to trigger so the mission failed (i was low on fuel and am hopeless at night AAR)
  13. nephilimborn
    I did get a campaign voice indicating a hit however no DCS BDA notification txt pops up...will run the mission again and pay better attention this time (apologies); i am using the miz file that you posted earlier however I seem to be experiencing the same behaviour - I must be doing something wrong as others seem to have recent success with the updated miz.
  14. nephilimborn
    I was unable to get Jester to designate the next target after hitting the bunker for some reason; i noticed another post seemed to get around this by re-entering the laser code...will try that next.
  15. nephilimborn
    This solution works for me (same MT-VR conditions); thanks!!!!
  16. nephilimborn
    same experience; tried a few different approaches with this mission however was unable to influence a different result
  17. nephilimborn
    From what i have observed, albeit anecdotally from these forums and tech-tubers that have a history of trustworthiness, IMHO the Crystal Light is exactly what i have been looking for. I am currently sim'ing with Quest 3 and do not care for nor will ever use MR or any of the other stand-alone features. For my use case, the CLight looks to be a good value proposition, as such just ordered the headset (Australia via Player1 Sim Gear)
  18. nephilimborn
    Three 4 hour DCS sessions over the last 3 days and no black screen events came across this vid re horizontal mount PCB stress; no idea how much of an issue this is over time ... i know a year ago people were having weird stability issues with PCIE riser solutions ;
  19. nephilimborn
    Received the thermal grizzly last night & installed it while also rerouting the pcie5 cable (relieving torsional tension, etc.). @kksnowbear I also am hoping that my previous obliviousness did not permanently damage the PCIE cable. @LucShep I rewatched the first video you recommended and realised that i was an idiot when i first attempted the undervolt with GPU Tweak III. I have since invested the time this deserved and was able to successfully tune the VF curve to .970volts @ 2700mhz (+150). This keep the max (timespy extreme benchmark) TDP to ~415watts (a BIG reduction in both power and heat). Last night i ran 15 different benchmarks with two tools without a black screen event. I may eat my words later, but sofar so good!!!! Going to put in some heavy gaming session tonight in DCS and the UEVR injected and see what happens. Thank you BOTH!!!!
  20. nephilimborn
    Thank kksnowbear, very good point wrt the cable routing as a possible root cause. It does have bend, that while not extreme (20mm), it does not meet the recommended (35mm) length b4 the bend - this is a result of the MSI cable length not being ideal with my build. Maybe ignorantly i trusted that ScorpTec pc builders know what they doing when they built the system. I ordered the thermal grizzly wireview to hopefully mitigate this, i trust der8auer more than i do cablemod - hopefully it arrives by tomorrow. i am so deep in the trees that i cannot see the forest; thank you for the analysis and a great idea to try the 8pin PCIE adapters, i should have thought of that! Now i just need to find where the hell i put the adapter! Also agree re the connector which is PCI-SIG specification; it was adopted by Nvidia & PSU vendors, not invented by them. I bear responsibility for just blindly trusting how the pc builder installed & routed the PCIE5 cable. Attached are two photos of the cable & GPU - will get the side panel off later and capture that as well. Thanks Again!
  21. nephilimborn
    Thanks LucShep, ordered the wireview. Also check 4 different power supply calculators, the majority of which seem to indicate that i am at the edge or above 80% power draw for the MSI 1000G PSU. I might just also pull the trigger on a new PSU; considering the XPG CORE REACTOR II 1200W which, according to Hardware Busters has very good 12Volt rail properties https://hwbusters.com/psus/xpg-core-reactor-ii-1200w-psu-review/ and is assessed as top tier on the cultist psu list https://cultists.network/140/psu-tier-list/ I tried undervolting with GPU Tweak III and got mixed black screen behaviour when running the Unigine Superposition stability test - i ended up just ignorantly setting the power target to 90% for now. Will put more effort into tuning the VF curve when the thermal grizzly wireview arrives. This sh*tshow is driving me into mental instability - replacing the PSU is driven more by desperation rather than any evidence that the MSI PSU is the root cause.
  22. nephilimborn
    in the interim i have been able trigger the black screen consistently, not with DCS, but with praydogs UEVR mod + Robocop: Rogue City. This hammers the CPU and GPU in a manner that seems to trigger the behaviour within 2min of gameplay (where stress testing with tools such as 3DMark do not) I collected data in HWINFO every 500miliseconds...others have suggested that NVidia firmware might respond with minimal voltage tolerance to mitigate the burn-the-house-down risk with the stupid 12VHPWR connector - the voltages near the event seem normal (16pin HVPWR voltage at 12.157 which is similar to other loads that did not result in black screen + fans 100% requiring hard reset). Other relevant sensor data near the event (all seem within operational boundaries - note i had a 97% GPU power limit set, locked all cores to 5.3, vid request limit to 1.4) GPU Power: 415.173W; 16pin HVPWR Power: 406.472W; Clock: 2700; Load: 96%; Hotspot: 70deg C GPU Core Voltage: 1.04v; PCIe Input Voltage: 12.171; 16-pin HVPWR voltage: 12.157 Performance limited ONLY by Voltage Reliability (this is normal and expected at this power level) CPU VID: 1.323v; Vcore: 1.344v; VR VROUT (SVID OUT): 1.351v; VR VCC Current: 82amps; CPU Package temp: 52deg C I found that if i power limited the GPU to 90% (GPU Tweak Utility) i was able to avoid the black screen, well at least for the 30min that i tested in game. Question: I know to avoid the recalled cablemod 16pin adapters; however the CableMod M-Series Pro ModMesh Sleeved 12VHPWR StealthSense Direct Cable Kit for MSI PCIE5 (16-pin to 16-pin) looked like something to try? Any thoughts? Thanks again for everyone's help on this; really do appreciate the advice.
  23. nephilimborn
    Thank you all, very good advise - i need to invest the effort to troubleshoot and test as recommended, i cannot keep holding onto the false hope this will be fixed or necessarily mitigated by a collection of BIOS, OS, Driver settings. First method i think is to swap the 4090 (problematic system) with a known operable system (my old 3080 rig) in order to narrow down if this is hardware or not.
  24. nephilimborn
    I was also wondering about this...i have since watched many of buildzoid's videos and adjusted the VRM and CPU settings as generally advised - however that of course is not going to fix an degradation damage already done. Similarly i was wondering if i should test with incrementally lowering & locking the P-Cores - thank you for the advice, you have motivated me to try this as well! Also, thank you for confirming my fears wrt messing with C-State!
  25. nephilimborn
    I am also wondering about this; i am running the following BIOS (gigabyte specific) settings to avoid the higher voltages the seem to be systemic to degredation (most of this is advised from buildzoid vidoes) IA VR Voltage limit: 1400 LL Calibration: High, AC LC: 55, DC LL 55 (50% of 1.1milliohm renaesas controller) VCore voltage mode: Adaptive, NF Offset mode: Legacy Internal CPU VCore offset: -.07 PL1/PL2/IccMax as per intel specs Good point, I do need to do more re testing with at least a different GPU.
×
×
  • Create New...