pachuco70

The weathered cockpit labels and text looks great in 2D but is almost unreadable in VR. I don't have this issue with other planes. I am using Quest 2.

Reflected, Any tricks to keeping up with them? I can keep up in the climb but the circling formation is tough. I have tried all kinds of engine settings...and blew a few engines as others have...but even flying WFO ( Wide F'ing Open ) and cutting the corners, I can't stay in the formation. I was afraid the speed was set by the AI and not by you ( as you mentioned elsewhere ). It would be nice if their speed was decreased by 10% to 20%. I have flown this campaign a dozen times and I must say, aside from the speed they fly, the new formations and the circling pattern is a lot more fun to fly and the mission doesn't feel like it takes as long. You look out and see a lot of action going on and it makes more sense to fly it like this because you have eyes pointing in all directions! If you didn't increase the fuel loaded...I don't think you could complete the mission with the old fuel load out. Flying WFO burns a lot of gas!

Reflected, I flew mission 5 last night and had issues with the AI. The 4 German fighters we are supposed to engage with fly full throttle towards the channel in front of the bombers. They outrun the bombers almost to England before turning home. My flight and I could never catch them...it was very strange. Is there an effective way to get ED's attention on these kinds of things? I know you have identified these issues to them numerous times but the issues after the last update make it almost impossible to play it. Since the last update my computer crashes every time I play The Big Show and Bodney...I am unable to finish a mission. The crashes happen about half way through the missions. This happens with both ST and MT. The Normandy map is awesome, and MT shows a lot of promise, but I might have to check out IL2 to get my fix...it's a damn shame.

This was in ST. I just ran it in MT and it worked! Ugh...welcome to software debugging hell...LOL. EDIT: I spoke to soon...it happened to me in MT also.

Screenshot where you can see him off center. This is happening in both the versions - Normandy and Channel Map versions of the campaign.

In Mission 2 on the new Normandy map...The wingman, #2, is not centered in the hanger. When I take off and he follows, he hits the hanger door opening every time and ejects. I attached a track file. bigshow_error_mis2.trk

I think Reflected mentioned that in the eleventh hour, ED changed the Normandy map frequencies. Not sure why they would do that...but now Reflected needs to update the freqs. I would imagine it's a PIA...LOL.

I use the term "landed" in the loosest possible way...LOL. It used to circle the airfield and then attempt a landing near your parking spot on the east side of the runway only to go long and explode on the other side of the fence/tree line...but the last couple of times it just explodes in mid-air just after spawning in. The last time I saw this I was able to F2 to see it as it spawned in, and saw it explode. I am assuming you have something triggered to cause damage to it? I could be wrong...but I definitely heard an explosion before the plane blew up.

Reflected, I think they might have updated the B-17 damage model. Whatever you trigger to cause damage to the B-17 is blowing the B-17 apart in mid air. Because of this it crashes and never attempts the emergency landing. This has happened the last 2 times I have played. The last time I was able to F2 view the B-17 as it happened and was able to witness it. I have played this mission many times and never saw this until recently. Having that B-17 come in for a crash landing has always been a highlight for me of this campaign. I see how frustrating it can be to spend hours on design and testing, only to have the mission wrecked by a little "harmless tweak" that ED does to AI, damage, or flight models!

I have found a cause for part of the problem. I use a modified Labels.lua file to help me in VR. I use the "aircraft_symbol_near" and "aircraft_symbol_far" variables to place a dot or symbol right over the enemy aircraft when they are near to help me identify friend/foe because the resolution isn't great in VR and plane ID is tough. I use the "CenterCenter" alignment variable to achieve this. To get the dot right over the aircraft I need to use a negative value in the "shift_in_pixels_y: variable. This used to work in ST before the MT update. If I change all the negative values to 0, it works again. But, of course, the dot is not centered. I am also getting issues where labels are not rendered in both eyes...something happened with the label system after the update. I only tested with "CenterCenter" and not any of the other values. I did not test if negative values work in the "shift_in_pixels_x" variable. I have attached my modified ( no longer working ) labels.lua file. Labels.lua

Reflected: I just played mission 4 and this happened: When we get the call to turn to 0-2-4 @ 7000m the whole flight turns but stays at around 1200m. We fly out on 024 but when we get the call that the 4 motors are close and we need to turn to 0-8-5...we are still at 1200m and start climbing at this point. No chance we can catch them at this point. I have not tried to recreate it yet to confirm...as it takes a while to get to that point. Just want to see if any others have experienced it.

dcs.log Log attached. Thanks. This problem exists for me in ST...I am not seeing this behavior in MT.

I can confirm. The option to assign in the individual plane profiles are now missing. The settings are available to be mapped in the "UI Layer" profile but that maps to all planes and is a problem if you don't map them the same for all planes.

Still having issues but it looks like labels are now rendering in both eyes and the effect isn't as bad...but it is still there. null

Saw the GR preview look at the Normandy 2 map...and WOW! I would purchase your campaigns again if you ever decided to port them over... I understand that it would be an almost impossible task to do...but we can dream!

Yea...LOL. In "real life" I would have scrubbed the mission because there weren't any holes to go down through. I will have to fly it again and see if the cloud cover varies. I know I probably dropped the bombs on some poor French family farm house! Having the navigator in this campaign has been fun...it allows you to concentrate on other tasks and adds to the immersion.

Not sure if it was intended...but the cloud cover on the last mission was almost 100%. I could not see the ground for most of the mission and navigation by sight was impossible. Over the target, cloud cover was 100% and there was no way to see the target. Thanks.

Sortie 2 can be a challenge...it's a tough one! I found a practice mission in the user files that helped a lot. You can fly both night and day missions without the stress of being shot at! Mosquito OBOE - Blind Bombing System

I think hit hard and run like hell is the strategy for this one. It took me a few tries on this one...getting the timing right and hitting when the train is on the bridge and exchanging the bombs on the wings for rockets is what worked for me. I think if you have to go back to strafe the train for any reason, your chances of getting out alive are slim.

I wasn't sure where I saw it so I did a search. It was in the PDF docs...looks like you removed it from the briefing screens. Yes...I'm one of those nerds that looks through all the documentation! Sortie 5 PDF docs Page 2, last bullet point. Sortie 8 PDF docs, page 4, second to last bullet point. Sortie 9 PDF docs, page 2, second to last bullet point. I get it with the AI...wish they would spend a little time there. The AI has been getting stuck on the ground and not taking off...it's very annoying. Luckily the action in your campaigns is usually trigger based and not time based so you can orbit the field for a few minutes and they eventually take off. I did notice that the AI flies really reckless when doing a form up over Manston...I had AI pilots fly directly into the circling flight, head on at high speed, and run into one of the "lads", so I had to fly a couple missions shorthanded! If you ever need someone to test for you let me know. I fly one or more missions from your campaigns ( I have them all ) just about every night. I started learning the F-14 recently because I am hoping to start the F-14 trilogy. Finding DCS with VR has been awesome...been waiting for this for decades. My first flight sim was in 1984...8 bit Flight Simulator from Sublogic! We've come a long way! It has been cool to see your skills as a campaign maker improve with each offering. I hope DCS knows how lucky they are to have you out here slaving away building these things...LOL. Is there a link where I can show my appreciation and buy you a beer?

Reflected...you outdid yourself! I think this campaign might be more immersive than Wolfpack. The variety of missions, flying at night, and flying low to the ground are a whole new experience. Who knew that southern England and France were so hilly? LOL. It's a whole 'nother world down at the waves and tree tops! Having the navigator adds so much to the experience...especially flying the Mossie with two engines and all the other controls to keep track of. For the most part it has been spot on except for Sortie 7. The first time I flew it I drifted too far south on the coast and did not get any navigation assistance. We crossed the coast right over the area with flak guns and half my flight, including me, were shot down. Second time I flew it I was able to hit the right spot on the coast but after that first waypoint Di didn't give me any assistance. I had to use the old "Attack Primary..." and follow my wingman to the target. I was able to get rounds on target and ran for home but had a FW190 follow me all the way to Manston! I don't know how he had the fuel to do it because I flew flat out and almost ran out of fuel myself. I know this could be an AI issue but is there a way to have them turn back at some point? Lack of navigation help and this issue with AI FW190s have been about the only issues I have had so far...and they were on the same mission. I am amazed at how I have been able to navigate the waypoints and hit exactly where I need to be ( with the help of Di, of course ). Flying at low level really makes it a challenge, but so far I haven't had any issues...it's amazing. In the briefing notes you mention that delayed fuses are not implemented...is that still true? I did some testing and it appears that you can set a delay and it looked like it was working. I fly almost exclusively WWII and your campaigns are the reason I fly DCS...thanks!

I am having this issue and a few others related to labels.

LOL...Yea I hear you with the issues. I was playing ST and there are a lot of issues there too. The UV light did work on the previous night mission though.

I also had my UV light go out on that same mission...is this a bug or is it scripted into the mission?

The other label settings have bugs too. The labels don't show in the left eye of my visor. I have attached a track and my logs. I also was not able to shut down the port engine on the Mosquito...it would just spin even when fuel and magnetos were turned off. I am using Oculus Quest 2. i9-12900KF w/64GB RAM NVIDIA GFORCE RTX 3080 Ti dcs.log labeltest_1.trk