II.JG1_Vonrd

There is no option to delete the page pictures using F10 as there are in other training missions. I'm not a fan of these pages hindering my view, especially of my kneeboard.

I second this! Pretty much all that I want on my kneeboard is the Mission Briefing, my personal graphic of my HOTAS keybinds and perhaps 1 or 2 approach charts for my main and divert airport. I suppose that I could use a 3rd party like OpenKneeboard or KneeboardBuilder (I haven't tried either yet on the F-4E) but prefer to not use 3rd party stuff as much as possible.

Are you using the passthrough option? I get the same delayed crash when using it. When I disable passthrough, no crashing even in 3 hour sessions.

Ah... thanks! Yeah, I'm doing the Mi-8 Spring campaign and the messages keep telling me to go to "grid 25 70 section 6" or some such. I had to open the mission in the editor in order to see where the target is. Too bad it's not an option. I sort of like it.

I can't seem to get this coordinate system to show no matter which system I put in, MGRS or any of the various Lat / Long options. Where am I going wrong?

Actually I just noticed this mod by Ghost11556: https://www.digitalcombatsimulator.com/en/files/3336615/

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:

Does anyone have video of this? I'm disappointed that I never saw it. Maybe it should be re-introduced as a feature.

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?

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.

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.

Thank you!

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.

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?

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.

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?

Kinda like Covid...

@razo+r Do you mean my profile icon? I can't find anything named attachments. Would you mind posting a screenshot? NVM, Found it.

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/

Rgr, thanks for the reply!

Interesting... Does it still work? In VR? If so, can you give a bit more detail as to where to put the script, how to connect it to DCS and the peripheral (mouse or PointCtrl)? Can it possibly break the game or mouse / PointCtrl?

With respect but my opinion... How much did this decision to rely on just one livery maker "greatly streamline" the process? Eliminated a vote by the team? I have participated in two of the more recent skin competitions and found it more than impressive to see the quality of most of the submissions. There were certainly "personalities" in the different skins from each livery maker. Are you looking to have a more monolithic batch of skins by having them made by just one maker? If so, you would have been better off not mentioning any name, call the competition off and just hire your chosen artist. That's normal business practice and I don't think that anyone would object to that. By publicly announcing @lee1hyas the sole artist, I feel that you have done him a disservice and opened up some feelings of resentment (understandable) by other talented livery makers. His skins are very good through all of the modules that he has worked on. They may not be absolutely perfect but whose are? Mine are certainly not. I have no dog in this race since I haven't (yet) made any F-16 skins. I refrain from making any comments about any F-16 skins. Perhaps a lesson for the future? I do hope that the future you will still hold skin competitions. I think that it furthers our sense of community as skin makers and I certainly have a sense of pride seeing my creations in the official game.

This livery depicts a Douglas A-20B-DL, SerNo. 41-3665, Code: #72 of the 86th BS, 47th BG, 12th AF based at Youks-les-Bains airfield, Algeria, 6 January 1943. (In the attached photograph, 41-3157 is the aircraft with only the tail showing. A generic version with Bort numbers enabled is included. Place in \Saved Games\DCS.openbeta\Liveries\A-20G. (Create an A-20G folder if you don't have one). The 47th Bomb Group moved to Algeria beginning mid-December 1942 and completed the move in early January 1943. The unit began operations by flying low-level missions against the enemy in North Africa. When Axis forces broke through at Kasserine Pass in Feb 1943, the 47th Group, though undermanned and undersupplied, flew eleven missions on 22 Feb to attack the advancing armored columns and thus to help stop the enemy's offensive - an action for which the group was awarded a Distinguished Unit Citation (DUC). The group remained in action in the Mediterranean theatre in Malta and Italy until V-E Day. From late 1944, the Group was flying several configurations of the A-20 and the A-20's big brother, the Douglas A-26.

This livery depicts a Douglas A-20B-DL, SerNo. 41-3157, Code No. 17 of the 84th BS, 47th BG, 12th AF based at Youks-les-Bains airfield, Algeria, 6 January 1943. (In the attached photograph, 41-3157 is the leading aircraft. A generic version with Bort numbers enabled is included. Place in \Saved Games\DCS.openbeta\Liveries\A-20G. (Create an A-20G folder if you don't have one). The 47th Bomb Group moved to Algeria beginning mid-December 1942 and completed the move in early January 1943. The unit began operations by flying low-level missions against the enemy in North Africa. When Axis forces broke through at Kasserine Pass in Feb 1943, the 47th Group, though undermanned and undersupplied, flew eleven missions on 22 Feb to attack the advancing armored columns and thus to help stop the enemy's offensive - an action for which the group was awarded a Distinguished Unit Citation (DUC). The group remained in action in the Mediterranean theatre in Malta and Italy until V-E Day. From late 1944, the Group was flying several configurations of the A-20 and the A-20's big brother, the Douglas A-26.