Jump to content

II.JG1_Vonrd

Members
  • Posts

    365
  • Joined

  • Last visited

3 Followers

About II.JG1_Vonrd

  • Birthday 11/01/1954

Personal Information

  • Flight Simulators
    Battle of Stalingrad, Cliffs of Dover, Rise of Flight, DCS
  • Location
    Oakland CA
  • Interests
    Flying, Flight Sims, Moto Guzzis, Glassblowing & art, History
  • Occupation
    Aircraft Mechanic / Inspector

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Actually I just noticed this mod by Ghost11556: https://www.digitalcombatsimulator.com/en/files/3336615/
  2. As the title says. Or, allow us to access and modify ourselves. There was a mod by Dalva24 for a "Cute" Rita... too cute for me but I did mod some of the files and it seems to work but I'm worried about integrity check. Here's another thread:
  3. Really interesting that there is a "magic number" that causes this affect. @303_Kermit nice detective work and well presented. The question in my mind is how often do mission builders place more than 100 entities in one group? I would assume not often. What if there are two groups of 55 entities each in close proximity? If that close proximity causes the same affect it would make sense. Many missions have areas that have large totals of entities in one area, i.e. a well defended airfield. I wonder if there's an area diameter 100 unit limit. I might give that a try for a test and encourage others to do so.
  4. Does anyone have video of this? I'm disappointed that I never saw it. Maybe it should be re-introduced as a feature.
  5. Thank you for clarifying! My worry meter has gone down. @BIGNEWY Can you confirm that the merge of Beta and Stable does not necessarily mean that hotfixes are out of the question for any future issues?
  6. I've been following this since the issue began, mostly because it affects my squad mates / friends who use the Quest (one had just purchased his first VR, a Quest 3 and within a week or so was grounded by the Meta fiasco). Thankfully, it doesn't affect me and my new Pimax Crystal. It does give me pause and concern though. In the future there are bound to be issues and some may break the game for some. With DCS no longer split between Beta and Stable it seems that there will no longer be Hotfixes. At least that's the way I read @BIGNEWY's posts regarding a fix. ALL fixes will have to wait until the next scheduled update (and as we have just seen, that schedule might be postponed when issues arise). I hope that I'm wrong in my interpretation of the events in this thread. I'm hoping that there will still be possibilities for hotfixes. After all, as we know "Stercus accidit" (I know, not a great Latin translation) and waiting possibly more than a month for a resolution to a problem is a bitter pill. If it's true that consolidating DCS to just one entity eliminates quick hotfixes, I would much prefer to be in "Beta" for perpetuity.
  7. Thank you all again for your input. The crash has not occurred again and everything seems to be stable. The PC (and all peripherals) are plugged into a surge suppressor strip. I'm beginning to think it was a momentary power loss and I didn't notice it since I was in the headset. We have had storms running through the SF Bay area and PG&E does have occasional issues... . I'm considering this as a closed issue but I'm not going to click "Mark as Solution" since it remains a mystery.
  8. I totally understand and thanks for your help! I just ran some high stress missions and had no issues at all. Temps were fine... GPU 58c, CPU 68c. Going to try Enigma for multiplayer stress. Maybe it was a fluke last night. I can't find any program that shows temps and usage in the VR headset other than fpsVR which works only through SteamVR. I am using OpenXR and don't want to use Steam. Anyway, just hoping that it was some sort of fluke. If it does happen again I will try all of your suggestions (I probably should regardless and will do so in future, but for now, I just want to enjoy my new toy. I thank you all very much for your help and suggestions.
  9. Yes. About a year ago and no problems. I agree that the voice recognition is unlikely. It was where the DCS log file was pointing though. It is probably due to system stress. I'm going to run some high usage missions and I have temps and cpu / gpu usage shown through MSI Afterburner / HWinFO64. I do have settings pretty high. I suspect the CPU. What's the best stuff to turn down in settings to reduce CPU load?
  10. Power off, no reset. CPU - AMD Ryzen 5 7600X MOBO - Gigabyte B650 Aorus Elite AX Memory - G.Skill DDR5-6000 (2 ea 32Gb) Graphics card - PNY GeForce RTX 4080 Storage - 2 each 2TB P3 NVMe PCIe 3.0 M.2 Internal SSD VR - Pimax Crystal using OpenXR latest build OS - Mindows 11 Pro 64 bit PSU - FOCUS-GX-1000 Gold No overclocking or any other modifications. Is there a program that will make a log of system temps in order to still be able to see them post crash? I have Core Temp but don't see how to keep a log.
  11. I just recently installed a Pimax Crystal. Everything was working fine for a couple days but last night I had a complete PC crash (powered off). Looking at @Flappie's DCS log troubleshooting it was due to Windows and only MSCTF.dll was present in the log. I use both VoiceAttack and SRS currently and have used Viacom in the past (Viacom was difficult to completely remove, it seemed to leave crumbs all over the place). I need both VoiceAttack and SRS and am reluctant to remove the one voice recognition profile that I've found. Any suggestions besides removing VA and SRS?
  12. @razo+r Do you mean my profile icon? I can't find anything named attachments. Would you mind posting a screenshot? NVM, Found it.
  13. Depicting Fw190A-3 Wk. Nr. 313 of Stab III./JG2, flown by Adjutant, Oblt. Arnim Faber who after shooting down a Spitfire flown by by Sergeant Trejtnar of 310 Squadron (Czech) RAF mistakenly landed at RAF Pembrey in South Wales on 23 June 1942. Includes three versions, two in Luftwaffe markings pre-capture (Luftwaffe markings has one with and one without swastika) and one post capture after being repainted in RAF colors / markings and given the RAF serial number MP499 and a 'P' for prototype. Interesting that they retained the "Fighting Gamecock" emblem of III./JG2. Link: https://www.digitalcombatsimulator.com/en/files/3336379/
×
×
  • Create New...