Jump to content

NoFear1979

Members
  • Posts

    110
  • Joined

  • Last visited

Everything posted by NoFear1979

  1. 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.
  2. Sure. I am at work atm but will sort you out once I am home.
  3. 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
  4. 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.
  5. 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:
  6. 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!
  7. 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.
  8. Doubtful even when a possible scenario. Some weeks back prior recent patch no such issues. Hence my question.
  9. 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.
  10. 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/
  11. Full repair fixed the problem. However I haven't been able to pinpoint the reason behind the problem unfortunately.
  12. Paratrooper RPG and Paratrooper AKS = same issue.
  13. 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
  14. 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
  15. Noted today that my replay files as described in topic are not loading aircrafts used by players.
  16. Seabased heli pads seem to not work properly. The helicopters spawn inside the object instead of on top of it. I've tried to move them off heli pads and then on it again without success. On carrier it works fine though, as well as landing on a seabased landing pad. Spawning: https://i.imgur.com/MRVj54j.png Landing: https://i.imgur.com/RB1bX3m.png
  17. I did a random test today and if "hold" command added under the tab "triggered actions" the ground units hold their position. However if adding "hold" command under the tab "route" they do not hold their position.
  18. Will we see a fix soon on the matter? Im simply asking since most mission built will be a mess and not really playable from a enjoyable point of view (look a cluster**** of units piled up in a unrecognisable blob). Thanks :)
  19. Some pro flying at nap of the earth and a spot on landing:
  20. Have done some mod work with the M261 rocket pods liverie. Basically whats needed is to add a dds file into the aeroweapons.zip located in the core installation of DCS. 1. Make a backup of the zip file and then extract the content to a non DCS installation folder - named exactly as the zip file. 2. Add dds files into the aeroweapons folder extracted from the zip. 3. Zip all files inside the actual folder and name the zipfile exactly as the origin zip file. 4. Move the new zip file into the DCS core folder location for the origin zip file and replace it with your custom zip file. 5. Add the following into the description.lua of your custom UH-1H liverie. Add the name of the DDS where red text is located below. {"M261", DIFFUSE , "INPUT DDS NAME HERE", true}; {"M261", NORMAL_MAP , "m261_nrm", true}; {"M261", SPECULAR , "m261_spec", true}; ----- And there you have it. I've added my PSD template that can be used to play around with the various color layers (or create your own). Save as JPG, then replace the JPG with DDS file extension. Showcase: https://imgur.com/a/mOijIBM It would be cool to see a selection of rocket pod liveries availible from the DCS core installation by default but that would require ED to adapt the rearming window to be able to select rocket pod liverie - which I doubt will be added or if it's even appliable. But nonetheless, for your custom liveries it can be done like this. Do note however that your custom zip file will likely be erased when DCS recieves a patch update. m261_black.dds m261_desert.dds m261_winter.dds m261_ws.dds m261 template.psd
  21. Hello Flappie! After some research I did notice by pure random luck that the hold command is the problem. If hold present = the units move to the 1st unit in the group and cluster up. If hold not present = the units stay in their preset position from the editor.
  22. Update: I noticed that the same issue arose with newly placed units - after I had added hold command to them. I removed the hold command and then they stayed in place. Seem to be some mishap with inverted command to the function "hold".
  23. Related to DCS 2.5.6.57264 Open Beta - 04.11.2020 patch. Just wanted to give ED a heads up on an issue that has arisen with the current patch. Great job on all those fixes, but still wanted to flag around the current topic. The current issue more or less means that mission builders need to replace current placed groups with new groups which will be a tedious task. What happens is that pre patch placed vehicles break their position to link up with the lead unit, even when tasked to hold. Would be great to see a solution! Keep up the good work you do.
×
×
  • Create New...