ChuckIV

OK, this is a really weird one... Check out my pics. I see the ocean water receding WAY out there! As I move along the ocean the "super duty low tide" follows me! The ocean does not render at all at about a radius of 15 miles. Anyone else have this weird bug? Any simple fixes? I use a Reverb G2. ChuckIV

OK, after playing around with my settings, nothing seemed to work with my Reverb G2 in mt. My starting position at the splash screen was BACKWARDS, INVERTED, and REVERSED! Totally messed up! Here's what worked for me... 1. First, start DCS in mt mode (no suffixed added --enforce_VR, etc). I currently have XRToolkit turned off. I'll update this info. once that's working. 2. This will automaticallystart/turn on your WMR and VR set as long as you have "enable VR" selected in DCS. 3. Now, start your XRNS program and VoiceAttack if you're using these. 4. My last step was to map camera movement to my keyboard because once in the aircraft, I still have to make some adjustments to my "centered" position. 5. When you're done, and ready to shut down, do everything in REVERSE order. Shut down XRNS, then VoiceAttack, then SRS, then DCS. Works for me right now. After the next update, all bets are off. Happy flying! ChuckIV

I found a OpenComposite folder and deleted it since DCS no longer needs OpenComposite. This seems to have helped with the crashing and helps with the framerates also. I'll let you know if I keep crashing. ChuckIV

Anyone?

Quick question... I noticed in the crash logs that there are MANY DX11 errors. My computer is using DX12. Am I supposed to be using DX11 with DCS??

Edit: 03-28-23 Still crashing. Does DCS require DX11 ?? My computer is using DX12.

This is the Hawkinge AB I'm referring to.

Planes coming out of the revetments 39, 40, and 41... Here's the problem. When set to a group of 3 aircraft (Spitfires - maybe others don't know), and the player starts from revetment 39, SOMETIMES the other AI aircraft get STUCK at the entry point for runway 180. They take like 5 to 10 minutes to start moving again. This makes doing timely sorties difficult for sure. It's frustrating, because it's not ever time - this seems to be intermittent. Any thoughts?? ChuckIV

Called SERVICE and they claim this replacement is ONLY FOR AMD systems Called SERVICE and they claim the larger replacement cable is ONLY FOR AMD systems Called SERVICE and they claim this replacement is ONLY FOR AMD systems

I saw the VRNeckSafer thread as a possible solution, but I was wondering if anyone has been able to get a regular rear-view snap view working? (like in TrackIR setups where you use RAlt+Num0 to set any view you want) ** I have the HP Reverb G2 ** ChuckIV

Just like the title says, can someone give me the link to Steggle's newest VR optimization video?? Thanks! ChuckIV

Thanks FroZone - That helped. It is working again thank you

Installed 2.7 update today, and now my 3-screen setup is messed up. The opening screen shows up on my 3rd (farthest to the right) screen, and it's all scrunched up (can't see text because it's compressed). Is there a 3camera.lua file fix for this? ...or is there something you figured out to fix this? PLEASE POST HERE any helpful info. thanks!! ChuckIV

I agree, the 109 is impervious to both 20 mm cannon and 303‘s. Over the past two days I have emptied every single bullet and cannon shell I have into a single 109, and it keeps on flying. This is pretty frustrating. In addition, they hit you with one bullet, and you usually black out explode burn up etc.

Check the manual on the red versus green state. I always get these two mixed up.

In the initial settings on the main splash screen in the MISC. menu, you can select synchronize cockpit controls with HOTAS controls at mission start - this will not help if you’re using keyboard for trims. If you have actual trim wheels for example then yes, it will set to whatever you left it at when you exited the aircraft.

I used to have it where when the sortie started I was seated perfectly in my cockpit! I had to make some small changes to the SnapViews.lua file to do this. Now the SnapViews.lua file does NOT include the Spitfire any longer. I found a similar file called Views.lua in the Spitfire folders, but have been unable to make the changes! Anyone know how to change your default sitting position now (in the Spit) so I don't have to keep moving up and forward each time??? By the way I use TrackIR5. ChuckIV

I used to have it where when the sortie started I was seated perfectly in my cockpit! I had to make some small changes to the SnapViews.lua file to do this. Now the SnapViews.lua file does NOT include the Spitfire any longer. I found a similar file called Views.lua in the Spitfire folders, but have been unable to make the changes. Anyone know how to change your default sitting position now (in the Spit) so I don't have to keep moving up and forward each time??? By the way I use TrackIR5. I'll post this in the Spit section as well... ChuckIV

Fri13 is on to something. He is a genius. Ground units are virtually impossible to see if well camouflaged. We need tracks. I am assuming if the mission designer turns off labels altogether that the black dots still exist correct? If this is true, I can see why a change needs to be made especially for ground units. Now let’s talk about the WWII airplanes... I cannot speak for those that fly modern aircraft, as I do not have any of those modules. Most of the World War II pilots have been on Phil styles SOW server. He has many videos out there in regards to spotting from distance. And it is way, way out there! like around 26 miles or something like that. So I am in favor of the current black dots as they are pretty accurate for long range spotting. It’s a level playing field and no one has an advantage due to computer equipment. Let’s just get onto the dog fighting! ED Please, please, please, please, do not change a thing about your black dots as they currently are. You have it just right.

Couple of ideas... 1. Try the trigger Unit NOT in Zone (create a large zone first) to end the mission 2. Try using cockpit gauges to trigger the end of mission - like mph, or fuel pressure, or rpm, etc. to end the mission 3. Maybe Unit Life less than 1% would also work.

Do you have "historic" mode set in the editor? It's the "clock" at the bottom of your ME screen. If so, then only aircraft of your date/era will show up.

Dynamic weather is the only option through the ME I believe. Try to set the dynamic weather up with like 5 different systems crisscrossing your map. ChuckIV ** Keep in mind, however, that this could mess up the direction that your aircraft take off from the bases.

Put TWO waypoints just before the runway, and TWO after. This seemed to work a while back. ChuckIV

OK, what folder do I need to put in my C:\Users\Chuck\Saved Games\DCS.openbeta.... so that custom... 1. Bf-109 skins show up in my ME? 2. Spitfire skins show up in my ME? 3. P-51D skins show up in my ME? 4. Ju-88 skins show up in my ME? 5. A-20 skins show up in my ME? 6. P-47 skins show up in my ME? 7. B-17G skins show up in my ME? 8. Fw190A8... 9. Fw190D9... I've tried C:\Users\Chuck\Saved Games\DCS.openbeta\liveries... that does not work. Any help would be GREATLY, GREATLY appreciated!!! ChuckIV

No worries Mr_sukebe, Once the Mosquito is up and running, the Axis don't have ANYTHING that will out climb it!! The Fw190's and Bf109's are absolutely DOOMED!!! Let them keep their MW50. It won't help.