Falconeer

Whenever i start DCS. it loads to the screen saying "15 years of DCS" and than crashes back to Windows. Last time i flew, all was fine and computer was shut down normally and no issues during flying. This morning when i tried to start, i was using my Quest 2 and rembered the post about the new update for the headset, which causes DCS not to start, however even if i start from Steam, same thing happens. Loads till the screen saying "15 years of DCS" and bang, i'm back in Windows. I have not installed anything, changed settings, downloaded stuff, except for updating SRS, but i don't think this is causing it So far i tried to: * reinstall Visual C++ Redistributable Packages * renamed DCS folder in "Saved Games" * run repair *completely whiped DCS and reinstalled But whatever i tried, nothing seems to work and DCS simply won't launch. Other games run just fine. I don't know what else i could try Sytem: * Windows 11 Home 23H2 * Amd Ryzen7 5800X3D * Amd RX7900XT * 64Gb DDR 4 * DCS runs on it's own M.2 SSD Edit: i just went to Steam and it appears there are more players reporting the same issue dcs.log dcs.log.old DxDiag.txt

You are making assumptions based of a random internet page

No, the GBU24 is also set on the ground. GPS can be changed midflight. PRF not

No, they get the info from the HOB sensors (Height Of Burst)

When our pilots (F-16's) do night ops, they switch jhmcs for standard helmets, because our jhmcs don't have room for the bracket which holds the nvg's. Iirc the Belgiums switched from jhmcs to Skorpion and the latter supports the nvg's bracket, so i'd say depends on which helmet you use, but not both at the same time

Indeed, thx for adding the photo, couldn't do that from my phone

Well, you just proved yourself wrong. The middle picture shows the location to set PRF codes. It's with the 4 circles (1 grey, 3 black) just in front of the fins. They are not always behind a door. The bottom picture shows the bomb from the wrong side, as they are on the opposite side

No, the laser code still needs to be manually set on the bomb. The data connection is for GPS and fuse settings only

GPS antenna's The smaller "windows" before that are Height Of Burst sensors

well, to be honest, i don't see anything special. Just a helo pilot doing it's job?

sorry, i don't have this behaviour on my Quest 2

You can press Nm pad 5 to recenter your view. I do this everytime when i enter a cockpit. Get myself comfy in my seat and press Nm pad 5. Never had problems since then with misaligned views etc, especially in VR

Dont forget to turn on power to the chin station

No Wing tanks are Cat III Yes That's what the stores config switch does, depending on the load

This is correct. I'm used to different abbreviations Potato potáto

MRM is opposite of the dogfight switch and is it's own master mode. Some call it MSL, others called it Missile override, i like to call it how it's referred to on the throttle as MSL is mostly use for "Mean Sea Level" There are 7 master modes in total. Thats why it's a master mode. It overrides every mode you are in

There is also a MRM master mode. Regarding the SMS page setup: you can set up different pages as you like. Mostly used are the bottom OSB's. For example, i like to switch to dogfight and MRM mode and set one of the pages on the right MFD to HSD to maintain SA. Then i set other page to TGP, so i can visually identify whatever target the radar has found. I leave the first page at SMS to change gun modes or have a quick overview of the weapons selected and its parameters. Same can be done in AG mode. So with this setup, you can quickly cycle between these pages with the DMS switch, without the need of fidling with the buttons and menus

The aircraft does not "know" what is mounted to the chin stations. All other stations are programmed manually by the SMS page or via the DTC

Correct and that's also an issue that a lot of this stuff is not described in the public documents If you are going to slap big heavy stuff onto the plane, things are changing to the flight caracteristics and need to be within certain boundries. That why the switch is there to prevent certain movements of the aircraft, so the FCLS doesn't lose control. Remember that the F-16 cannot fly without computers, because it has a very unstable design (hence it's maneuverability) The CAT I / III switch doesn't limit how much G's you can pull directly, but it limits AoA and roll, which in terms affects how many G's you can pull at a certain speed. In Cat III, you can still hit 9 G's, but you need a higher speed to do so. You can test it by loading the jet up with bombs and wing tanks and start a steep climb. Put the switch in Cat I and start a roll and pull on the stick to command max AoA and you'll most likely loose control of the aircraft. Now try the same again with the switch in Cat III and the system will project you from loosing control (departing controlled flight is the correct term)

pm sent

Nothing needs to be corrected, you simply cannot shoot missiles from down low and expect them to behave the same as if they are fired from 30k altitude. It doesnt't work that way

Correct and make sure the name in the monitor.lua file and the name in the RWR.lua file are identical. Also make sure that the RWR.lua file is modified, so that it can be exported

Our Apache can't fit missile launchers, because of the Missile Warning System mounted on the outer wing surfaces. But Hellfires are a good substitude

Well, shooting from there puts you already in a very big disadvantage. The problem is not the missile

You can just flip the Cat I/III switch and the error should clear. Technically speaking, it's not a fault, but an advisory