Jump to content

Luse

Members
  • Posts

    474
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Luse

  1. Scotch,

     

    I've looked at both lines and have previously removed "scriptmod" from the paths file. That's not the issue.

     

    The error isn't within the paths file - the error is within either of the following two files,

    UTIL_Functions.lua - Doesnt have a specific line specified

     

    but

     

     

    BAT_FirstMission.lua:43 is the following line:

    dofile("../../../ScriptsMod."..versionPackageICM.."/UTIL_Functions.lua")

     

    I've tried replacing /ScriptsMod." with the 20.xx.xx.xx as my current package is, but that doesn't seem to fix the problem either.

     

    Messed around and found a few things out of place within UTIL_Functions and the BAT first mission file.

     

    Successfully generated and ran through first missions, however, I get the following error when ending a mission:

     

     

    DCEError.thumb.png.6de14aa755290a1cbd639bee3d87c7dc.png

     

     

    Hey folks,

     

    This is an easy fix to make this work correctly. Navigate to, then open path.bat (the one where you set your installation paths) using Notepad++ or advanced text editor.

     

    Now, Line 8 looks like this:

     

    set "versionPackageICM=ScriptsMod.20.38.01"

     

    You need to delete: ScriptsMod.

     

    So, Line 8 should now look exactly like:

     

    set "versionPackageICM=20.38.01"

     

    The author mistakenly left those characters in, so the batch file was effectively looking for:

     

    ScriptMods.ScriptMods.20.38.01

     

    which does not exist, hence the error.

     

    So, remember to correctly set your installation paths in this file while you are there, then run the FirstMission.bat to reinitialise the campaign.

     

    Let me know if it works for you.

     

    Cheers!

     

     

    Sent from my SM-G950F using Tapatalk

     

     

  2. I've done two reinstalls of the P-51 Normandy campaign -

     

    I receive the following error upon running firtmission.bat

     

    H:\Eagle Dynamics\DCS World\bin\luae.exe: cannot open ../../../ScriptsMod."20.38.01/UTIL_Functions.lua: Invalid argument

    stack traceback:

    [C]: in function 'dofile'

    ..\..\..\ScriptsMod.20.38.01\BAT_FirstMission.lua:43: in main chunk

    [C]: ?

     

     

     

     

  3. Zooker,

     

     

    Multiply that by the length of the cycle in hours, then divide by two.

     

     

    A 1+15 cycle gives you 37 minutes into the wind for 22,727 meters.

    A 1+30 cycle gives you 45 minutes into the wind for 27,272 meters.

    A 1+45 cycle gives you 52 minutes into the wind for 31,818 meters.

    A 2+00 cycle gives you an hour into the wind for 36,363 meters.

     

     

    For experimentation purposes, I've been flying strikes with a 1+30 cycle where the carrier turns into the wind a few seconds after mission start ....

     

     

    Thank you for this, Yoda!

     

    Can I ask where you are putting the distance parameters? I'd really like longer carrier legs for my missions.

  4. After flying an aerobatic flight with a group of friends tonight and wanting to grab some screenshots I decided to max out my setting in DCS and found out something peculiar.

     

    The track will play totally fine ( No jets breaking off randomly, etc ) as long as I don't mess with AA / AF. Changing either of these settings will make break the track %100 of the time. When taxiing I will run into the jet in front of me, graphics settings back to what they were when flying and it doesn't happen and the track even takes fast forwarding at 30X no problem.

     

    Is this a known issue or bug?

  5. 23ish if I recall. The map was expanded quite a bit adding several new airfields. That expansion wasn't cheap for disk space. 33.4ish is an accurate number to its current size.

     

     

    Quick mission loads the first 1/3rd of the way and then hangs. I'm not sure entirely how to read in the logs exactly where I'm killing the process at, it's around the 4+ minute mark.

     

    To recap,

     

    Updated, Repaired.

    New Saved Games, Repaired.

     

    Still having the same issue.

  6. Removed, no difference. Still won't load.

     

    As a side note, both times I've had to repair TWICE before getting the game to launch. Each time the first install doesn't do runtimes. The second repair does and both games will boot. BUT - 2.0.5 is still having the mission editor issue.

     

    EDIT: Not sure if it's related or even close to related.. But looking through WinDirStat I see that just Nevada is pushing 33.4 Gigs. IIRC It was previously around 20 correct?

  7. Hello!

     

    After updating to 2.0.5 I found out I was unable to load into the mission editor, Not a problem. Ran the repair using SKZillas repair function and rebooted.

     

    Same issue, I've waited 11 minutes and finally called it quits.

     

    System Specs are as follows; i5-4670k @ 3.4, 16Gb DDR3-1866, PNY GTX 1060 6GB ( W/ Most recent drivers ) Samsung 850 Evo 256 - DCS 1.5 and 2.0 are installed here. 600 Watt platinum plus rosewill PSU.

     

    Also,I noticed there was an "failed.ofsh" file inside my 2.0 Saved Games folder,

     

    Logs are attached.

    Logs.zip

  8. Quick question,

     

    For some reason having them installed makes the edges of any terrain look like I have no AA or AF. AF is set to 16 and AA is set to 8xQ.

     

    Any ideas?

  9. Not sure if this helps, but after take-off, when not in any autopilot mode, the Flanker needs to be heavily trimmed nose down.

     

     

     

    Absolutely! However it doesn't matter how much trim- nose down I encourage. The sim isn't detecting any. From default keyboard settings OR stick. I also just saw the thread below this one :doh: mods if you want, feel free to merge this into that thread.

    EDIT: Alright, Something very goofy - Been reading up on this, I've disabled FFB and still unable to trim on ED A/C ONLY.

     

    EDIT 2 I've been using my G27 pedals as rudder ( clutch , brake and gas ). I've unplugged them once, still had the issue.

     

    Replugged them, same issue.

     

    Unplugged them. Issue fixed - The issue is only present on ED Aircraft and Modules ( FC3, L-39 Etc )

     

    Any 3rd party module is fine with the G27 plugged in. Tested and verified with Mirage, MiG-21, F-86

     

    I hope this has helped, it's really irritating as I dislike having a twist rudder. - Any ideas?

×
×
  • Create New...