toutenglisse

I had repeatable results : same approach line, speed stable with ATC at 370kn, alt 6000 feet, mk82 auto mode against static BTR80 locking it using TGP point track. Without lasing consistently a bit too long, with lasing consistently spot on. Thanks.

Thanks for sharing this. With F16c I clearly see dumb bomb precision is better in both CCIP and CCRP modes when lasing. I'll try with hornet. Interesting to know that it's increasing precision IRL. Also I didn't know that it could benefit to precision with A10c (the flight manual do not say anything about that, contrary to F16c manual). And yes my question is regarding both auto and CCIP dumb bomb precision with Hornet.

Sorry Bignewy, bad move from me that I didn't save the track even if too long. I'll do if it happens again. It's a custom scripted mission I'm working on, with a script containing specific tasks for each airframe. I also had an other bug testing this mission : water drops effect everywhere on sea that seem to happen when missiles (120c) don't reach target and fall to sea. I'll try to replicate and make separate bug (but I know others also had this one before).

Just reporting, I know there is nothing usable here (happened after using Ka50 for some tasks, then I spawned in F18 with wingman on Stennis slot in singleplayer same mission file and this happened - I didn't saved track that would have been too long maybe 1 hour). I was taxiing to Cat 1, AI wingman was taxiing to Cat 2, wings folded, when he suddenly accelerated like an "UFO" and, after me saying "Oh merde !" while seeing him, I hit F2 two times and win+alt+R to record this : (the video speed is not accelerated)

I have this question since TGP has zero entrance in F/A-18c early acess guide. In F16c it's clearly written that lasing with TGP helps for bombing precision in CCIP / CCRP etc... (page 154 - laser ranging). But with Hornet does lasing help the same way or not ? Maybe laser ranging fonction is separate from TGP in hornet ? Thanks.

Yes it feels like built in positive curve - which I understand if it matches the real feel when using a force sensing flight stick like realsimulator.

Just a personnal finding in case it helps (because it works for me) : set negative curves for roll and pitch (I use -15 for roll and -13 for pitch, I know several other users also use negative but different values) - it will make the airraft more responsive (my first expectation for doing this) but also make the trim LESS responsive, so easier to fine tune assymetric trimming. (using Warthog flight stick)

Yes you can do what you need using random flag in action. Sorry picture is in french but you'll find the correspondant English term for sure (if I use wrong ones while explaining). Base trigger : Once - time more than 120/player in zone - "random flag" : flag 1, min value 1, max value 3. Then you set 2 other triggers, in condition you put for each : trigger 1 : "flag equal" : flag 1 value 1 - action = activate Sukoi trigger 2 : "flag equal" : flag 1 value 2 - action = activate Tor If the random value is set to 3 nothing will happen cause no trigger use this value.

It may be this : https://forums.eagle.ru/showpost.php?p=4051361&postcount=5

Normandy map has been updated on DCS Stable release, on December 2019 : https://www.digitalcombatsimulator.com/en/news/changelog/stable/2.5.5.41371/

I had this issue some time ago spawning on Stennis - like Breaklight said choosing another slot then trying again did solved because : - the first time the spawn occures on the place choosed for the slot in mission editor (unavailable / delay because a static was interferring) - the second time the spawn occures on an automatically defined place - in my case not interferring with a static plane. Remove or relocate the static plane did solve everything (no delay for first slot choice). If you have no luck trying several times to spawn the slot, it is I think because static planes are blocking all possibility to spawn (or interferring at least).

This ? : https://forums.eagle.ru/showthread.php?t=269900

By chance the guy didn't had to pull the handle on a Sa342.

that's what I thought.

Your FPS are the same than mine. You have 46 fps average with old cpu, and 49 fps average with new cpu. That means 45 fps in vr with just some spike, like me.

It is. Mine is a flat line 45fps with sometimes a spike up sometimes a spike down.

This mission (F16 interdiction caucasus) "has a bug". In VR, with ASW off (no fps capping) I can't get more than 45fps ("bug" is capping perfs), when in other missions I get normally variating FPS between 45 and 90. A good exemple of "perf bugged" mission (there are probably several) but in my opinion not a good exemple to see if a new cpu gives better perf with DCS.

Use this, unless your DCS is on steam : https://forums.eagle.ru/showthread.php?t=160053

This function works using M.I.S.T. Here a .miz working exemple (unit near bridge for you to observe, explosion occures on bridge at 3 seconds and destroys it, then the M.I.S.T. function detects the bridge destroyed in zone and triggers a text and green smoke) "Object.isExist" function with inbuilt DCS Scripting should also work but I don't know how. MIST-SceneryObject-destroyed.miz

Yes it works the way Sedlo said, but in addition to "unit speed less than" you have to create a "unit speed more than", or the trigger will shot while taxiing before take off if inside the moving zone. Here a picture of an exemple in mission editor - units are metric, also the CVN is moving at 20km/h.

The Apache A and D have a duplicated weapon for slot 2 and 3 (the HE rockets).

I had similar issue at first, Trim command too sensitive for 1 "click", but for other reasons I modified the curves (negative ones) for roll and pitch axis (I think I use -15 for "X" and -13 for "Y") and that also had an effect on Trim sensivity. Result is : axis with negative curves is way better to control the aircraft a similar way than others like F18 (with no curve the Viper lacks too much sensivity in axis - maybe because original axis settings have to match a pressure input controller like real ?) AND the trim Hat became less sensitive (I was expecting the opposite ?) and I can trim way more precisely.

From DCS Manual (folder DCS World Openbeta/Doc) page 206-207 : "Additionally, black, grey and red font colors are used to denote: grey – automatically generated action; white – valid action; red – invalid action. " Disclaimer : seems to be a bit of confusion with colors in text and in exemple pictures (just above : black, grey and red instead of white, grey and red. Same in the exemple picture label for white action described as grey…)

the little script. test-road.miz

the little script. test-road.miz