Taz1004

I'm trying to figure out why I'm keep getting score of 85 on this mission. I was around 15 seconds early when I reached the carrier. How are you supposed to set this up by the way? I set TGT to wp4 as in other videos but wp4 is ahead of the carrier and I seem to arrive early. I told Clam to detach when the message appeared short of the carrier. I was at 300 kts and 850ft. I also couldn't tell my wingman to kiss off because the menu option never appeared during Case I. Is this DCS bug or does it only appear under certain conditions? I just told him to RTB instead. Edit: I don't know how but ended up getting 100.

That's what was fixed in v20

ST or MT?

Just typo.

UPDATED TO V20 for DCS 2.8 3/15/2023 Smaller smoke markers Fixed minor compatibility issues between ST and MT version of DCS Smaller Smoke Marker.

DOWNLOAD For DCS 2.8 OB Multi Thread: IC Fail version for Multi-Thread: Better Smoke V19SP MT IC Safe version seems to work fine for me so no change needed there.

I originally wasn't going to do winter trees because default looked okay. I did the snow covered trees at the request of some and to have an option. You can simply delete files that says "winter" from my mod.

Due to the bugs. But I remember you said there's only one bug for BS3 and rest of us just don't know how to fly so I'm sure you'll have no problem.

Not that I can think of. These tree mods are straight texture swap. Most of the times reduced in size.

I didn't think the "possible" bug fix and Igla was worth $20. But maybe $10. You can say I fell for ED's marketing but I was trying to salvage my prior purchase. Just stating my reason for buying the buggy upgrade since you asked in prior post. And A10C-II wasn't this bad upon initial release. You could still complete missions.

IDK, it sounds to me like your argument is the flawed one. Just because it happened to A10C-II, it doesn't justify happening to BS3. I bought it in the hopes that ED will finally work on the Shark and fix the bugs because BS2 was pretty much abandonware. But it got worse. You can't possibly play any campaign in current state. I am still hoping that it all gets fixed eventually. And I might take your advice and don't buy anything else from ED because waiting for reviews is also pointless. There's old post of mine where I asked if BS2 was as complete as A10C and everyone said YES except just one. You'll also find plenty YouTube reviews of BS3 raving about it.

Yes I have mods but it's all texture mod, shadow mod, and label mod. Nothing I could think of that may affect the AI or comm. Maybe Vaicom? I'll try again with no mod but it's the fact that I keep having to play 60 minutes of it to reach that point. Is it possible for you to send unencrypted version of this mission so I can chop it down to that section? Or is there way to skip it and not get 60 points?

Yea it is my startup routine to turn down RWR and WPN volume. Then some voices in training are way too low. I raise it for training, forget to lower it back down, and then my ear drums get blasted by my wingman when flying another mission. Wish sound level of all audio are normalized. Sound editing softwares lets you do this all together in batch process. And not directly related but would like to mention this as it's also about having standards between modules. Key binding names needs to be universal. Radar/RDR, Speed Brake/SPD BRK, Open/Extend/Aft, Closed/Retract/Forward, HDG/Heading... I know it's due to different developers working on different modules but wish there was some guidelines developers need to follow for consistency.

I tested on my private server and it even passed the pure script so I can't say what you're doing wrong unless I know what you're doing. Again, what does the log say?

I'm sorry, the way you wrote that is a bit confusing. You say it fails on "other" online servers but "Others" seems to be fine with IC? You referring to other "people" on the second other? What does the log say?

Regardless of the reason or whether it's realistic or not, these inaccuracies in DL makes wingman commands "Engage Datalink Target" useless because the AI doesn't know which target I'm talking about.

I unbound that long time ago and nothing's assigned in General. But still have this behavior unless I set something to "recenter VR Headset" in UI Layer.

I don't see "Reset view" under General tab and none of my controller has any assignments in General.

I did find a workaround however. Go into UI Layer and assign keyboard strokes you don't use to "recenter VR Headset". I assigned LCtrl+Num5. Leaving it empty causes it to revert to Num5.

Yes, I'm getting this too. I unbound Num5 from all controls section but still being used as VR recenter.

This is still happening to me. I tried it again yesterday after the patch and still happened. I tried again today following RedKite's video exactly and still happened. In his video, when he pressed Spacebar at 37:05, the tanker started to turn immediately. For me, even after I pressed the Spacebar and he acknowledged to "bring it South", tanker kept coming towards me and started to turn only after he passes me. Only thing different from his video is that I was at angels 12. RedKite looks like he's at 26. Does that matter? I tried to get behind the tanker and he just does all kinds of maneuver to shake me. And if I fly straight, it settles 0.3 miles behind to my right.

There are two things that affects sense of scale. 1. If you look at your car through binoculars, it would look huge. If you measure your car while looking through binoculars, you'll find that the measurement is correct. But it still looks huge. This is focal length. 2. In-game IPD adjusts the separation of left and right camera within the game. By lowering it, you're basically making your in-game head small. Which in turn makes the world bigger. SteamVR calls this World Scale which is more appropriate. Ideally, we'd want a way to adjust #1, the focal length of in-game left/right camera because it's headset/user dependent. G2 I believe have 2.5m focal length and Quest I heard has 1.5m. It also depends on custom lens, glasses/contacts etc. But since DCS doesn't give you focal length adjustment, only option we have to offset that scale is with #2. So use whatever value you feel happy with. But again, it's "SENSE" of scale. Measuring while your measurement tool in VR is also affected by #1 and 2 would be pointless. Actual scale of the in-game 3D models were all accurate when measured them with passthrough camera of my HMD.

For my Vive Pro, SteamVR detected the latest DCS as new game. I had to reset all the settings like resolution, motion smoothing etc. Good thing is OpenXR toolkit now works for SteamVR. I personally am getting much better performance with sharper image.

Tape measure inside VR would be pointless as it itself would be off scale. You need to compare it to RL. Place your controllers in VR at points you want to measure from and to. Corner of left and right MFD for example. Then measure the distance between your controllers in RL. You will most likely find that the scale of the models are correct. It is the distortion of the lens and in-game VR camera focal length that throws off the scale.

I thought that was for Hornet. For Viper is MAN RNG