toutenglisse

Here a mission file with 1 Ai Su27 with task to attack a warhouse. AI-attack-static.miz

Delete options.lua located here : C:\Users"your name user"\Saved Games\DCS.openbeta(or DCS)\Config\ It does reset all option settings (incl. VR).

Resolved. I just rebuilt the mission to exact same (quick considering there are only few things in M.E.) and the issue disappeared. Sorry to ones who lost time watching this...

It must be the same than SA Page showing all anti-AC units. The only workaround I know is to teleport these units at start - then they will never show up on these pages.

Building mission with MIST script - without script the wingman Ka50 has no issue taxiing, but with my mission when I start taxiing the wingman bugs : F2 view shows wingman speed is near 30km/h but he barely moves (0.3 km/h ?). Help ? 2Ka50-PLAY-AI-taxi-OK.trk 2Ka50-PLAY-AI-taxi-stuck.trk

Much thanks Zarma - I was trying to use setimmortal/invisible unsuccessfully - your exemple shows all commands needed for it to work :thumbup:

I'm noticing an impact on performances due to Lua functions that regularly check groups (like dead or alive). On a Ka50 random escort task I'm building, 2 groups (about 5 to 10 units by group) at a time are checked for being dead or alive. If the functions are ran every 5 seconds, performances are impacted (zero critical usage but fps go to sawteeth instead of flat). If the functions are ran every 30 seconds all is OK.

Near all ground units now pass through buildings, but some don't : here a M1A2 and a T72B stuck. EDIT : no it doesn't seem to be related to unitType but building type. Here an APC stuck in the same building type than the tanks :

Much thanks, these ones works well in 2D, but are wrong in VR or with any 6dof. On Ka50 they also seem "bugged" (sliced).

I confirm I had 10°c loss when opened case and put filter in front of cpu cooling radiator.

Just to report but I think it's minor issue. I just had trouble with DCS freezing while testing 1 mission building. I nevertheless tried all the usual "crash" suspects, but it was a command synthax that worked with previous DCS version. I used : mist.groupToPoint('Groupname', 'Zonename', 'on road', nil, 60, true) and mission systematically crashed (DCS freeze - to the point only reboot can work) after couple of minutes when spawning / auto-destroying groups that trigger this fonction. Now I use : mist.groupToPoint('Groupname', 'Zonename', 'On Road', 60) zero problem. Just in case someone encounter this DCS freeze in an other case (so no log, no lua error msg) - because I spent lot of time to find the issue, it can be a synthax obsolete or that became unstable now ? (Mist 4.3.74)

This road is blocked by a railroad bridge - coordinates in picture.

Thanks it's much more easy now that ground units can pass through scenary buildings as workaround.

Here very short track about the TGP/Mav perf issue over Caucasus in VR. I noticed something about this : here I just turn on TGP-Flir + Mav on displays, and fly turning around banking so both pointers are just below or on horizon. (in A10c) On the first 360° around the perf are totally bad (less than 20 fps, issue accompanied by 4 cpu cores at 100% usage) every time pointers are upon mountains with forest area. During time pointers look to georgia west/sea direction, fps are good. At the exact moment I finish the first 360° the perf are totally OK. The next 360° is perfect no issue. If I restart this it happens again the same. A10tgp-mav-bug.trk

Here 2 tracks to show impact of "turbulences wake" in F/A-18c instant action 8v8 BVR, in 2.5.6 (at least on my side and in VR, in 2.5.5 this mission was OK with turbulences). Test3.trk is this mission without "turbulences wake" enabled, Test3turb.trk has the option enabled with halved fps. Tracks I post are direct copies of original tracks before I replay them (I've not watched these copies, if issued I can post originals but I watched them/corrupted them?), I noticed that : 1) tracks seem ok at beginning but quickly they are desync, I chase ghost planes and fire missile toward nothing, might not be an issue to see perf impact. 2) "turbulences wakes" option is hard coded in track, you have it or not enabled in options doesn't matter, a good thing to see perf impact. Also MSI afterburner monitoring of both flights. test3.trk test3turb.trk

Is it possible that you used to have "wake turbulences" enabled, and that after total new installation you have actually this option disabled ? If so try to enable it again to compare FPS. In several missions with enough air units, running absolutely normally in 2.5.5 with "wake turbulences" enabled, FPS are now strongly impacted on my side, due to "wake turbulences". I now have it disabled in 2.5.6 and these missions run like before. If no relation to this just disregard, it's just something that came to mind. Glad you sorted out.

Yes you said it better (and I remember I had lost gun on Ka50 once or twice). Question is will damage model be applied to external storage ?

Question / suggestion. When warbirds are hit for exemple on a wing near a gun, this gun is damaged. But with modern aircraft there is no damage on weapons (except if you loose the part weapons are attached to, for exemple a half wing of a Ka50). Here in this exemple wing is damaged, but Mavs being hit are still operational.

Just to report that this performance issue seems to have much more impact then prior 2.5.6 Here in exemple in VR I just hover in Ka50 around 4 taxiing FW190A8 or P51D. With P51D all is normal, with FW190A8 performances are somewhat halved.

The F-18 8v8 instant action runs near flawlessly in VR (except some occasional stutters due to heavy static clouds), unitl I activate "wake turbulences". With it activated it roughly cut in half GPU usage and performances. (see picture) The same low usage/perf phenom. also appear if several FW190A8 are rendered in field of view (engines running).

Very good set of textures, crisp and realistic at low altitude. Much thanks for sharing.

Here a track. It takes 1 catapult attachement-T/Off before bug appears. Simple case : 1 stennis and 1 F18c. F18catbug.trk

Here in this picture.

When I select an AC with Wpts and add 1 WP, and then select another different AC, this new one is labelled as the previous AC (ex : F/A18c Lot20 instead of M2000 in my exemple with 3 pictures). If just selecting an AC but no modify made, then selecting another AC is ok.

Maybe you did roll back to stable ? Try this command : DCS_updater.exe update 2.5.6.43503@openbeta