NoFear1979

The Nato Forces and SovietIran Forces LUA files contains what follows: GT_t.CH_t.HUMAN = { life = 0.08, mass = 90, length = 1, width = 1, max_road_velocity = 4, max_slope = 0.87, canSwim = true, canWade = true, waterline_level = 1.4, engine_power = 0.5, fordingDepth = 1.0, max_vert_obstacle = 1, max_acceleration = 3.0, min_turn_radius = 0.1, X_gear_1 = 0.3, Y_gear_1 = 0, Z_gear_1 = 0.0, X_gear_2 = 0.0, Y_gear_2 = 0, Z_gear_2 = 0.0, gear_type = GT_t.GEAR_TYPES.HUMAN, r_max = 0.53, armour_thickness = 0, human_figure = true, } The value you want to change is life = 0.08. This value should be > 1 as stated previously. I changed it to 1.1 just to be sure. This should fix the problem with the units not firing on opposing forces or not moving to wp's etc. There is another mod called Insurgent SF 4x4 (Technical with 50 cal) that has the same problem. This solution works for it as well.

Sure. I am at work atm but will sort you out once I am home.

With DCS 2.7 I've noticed that the ground units won't move or shoot. I read somewhere (forgot where) that it would resolve the problem by setting the health to value > 1. So for instance 1.1. I tried this with the Nato GF mod and it worked. So I think this mod deserves an update

When country US is selected the nato and us soldier as well as the russian iran and russian 1 and 2 soldier does not move to waypoints or interact with oppossing AI factions in combat. All units mentioned are marked with a star in their name as well, if that has any relevance to the issue. It's a shame, those models would look great instead of the vanilla US AI infantry units.

I found a post which shed some light on the issue, luckily it was not the editor but a invalid ogg file that was the problem. Deleting those ogg files solved the problem Reference:

Been doing some further investigation on the issue and it seems that it is my client which is having issues since a friend could use the open command without problem. I've tried to run a full repair but to no avail. Would appriciate some support here ED Thanks!

For instance using the action "radio transmission" has the option to open a ogg file to add to the mission. Problem is that this and other actions which has the option to open a ogg file does not work, simply nothing happens when clicking. I tried the same through a ground unit but same issue there as well.

Doubtful even when a possible scenario. Some weeks back prior recent patch no such issues. Hence my question.

I edited one of my mission files because I found some conditions that were off. This is not the issue but what follows from my mission editing: I saved the mission file per "save as" as I usually do. After this I wanted to close the editor. It then prompts again that I haven't saved recent changes (which is not true), and ask if I want to save changes. I press no since I have already done it. However this results in all content of the mission file being wiped out and the mission file at 0 kb and not recognizable by the editor to open. Note that this was for saving on the same mission file. I then tried to save as a new mission file, which didn't prompt when closing the editor if I wanted to save recent changes. However when I try to load this mission file under the mission section of the main menu, it states loading and nothing happens. So there is something off with the mission editor it seems.

Anytime BigNewy! I have done some research FYI. Prior to DCS 2.7 I have used specific objects from third party mods which in DCS 2.7 is not compatible at all due to the no longer supported OS windows 7. How it worked before as a work around was to add additional files with a specific name due to a missing file using specific mod and object in it. It is those files that caused a problem in relation with DCS 2.7. So in conclusion, DCS 2.7 software was not the problem. It was using a mod object and specific files for it based on windows 7 support that caused it. Since those files however replaced original (backed up of course), is what caused DCS 2.7 to crash. Hence why the repair fixed the problem. Why telling this? Simply to clarify that DCS 2.7 was not the root of the problem (On second notice I was able to go into the mission file and remove the objects manually be removing some of the code using Notepad++) -> Removed Civ Spot Lights White since they are no longer compliant with DCS 2.7. Source: https://www.digitalcombatsimulator.com/en/files/3315880/

Full repair fixed the problem. However I haven't been able to pinpoint the reason behind the problem unfortunately.

Paratrooper RPG and Paratrooper AKS = same issue.

When trying to place Infantry M249, Infantry M4 or Infantry Soldier JTAC in editor DCS crashes, or when trying to load a mission containing those units. Note that I haven't tested vanilla infantry units for Russia e.t.c. For whatever reason this message comes up when loading a mission as described above. Shader "bazar/shaders/model/fake_omni_lights2.fx" failed to compile. Reason: warning x4717: Effects deprecated for D3DCompiler_47 D:\DCS World\bazar\shaders\model\fake_omni_lights2.fx(66, 13-91): error x3017: 'calculate_position': cannot convert output parameter from 'float' to 'float3

With DCS 2.7 a new roadbump has arisen with the fake_omni_lights2.fx: Shader "bazar/shaders/model/fake_omni_lights2.fx" failed to compile. Reason: warning x4717: Effects deprecated for D3DCompiler_47 D:\DCS World\bazar\shaders\model\fake_omni_lights2.fx(66, 13-91): error x3017: 'calculate_position': cannot convert output parameter from 'float' to 'float3' I am trying to figure this one out but if anyone else comes up with a fix please post it

Noted today that my replay files as described in topic are not loading aircrafts used by players.