Issues with compiles.sqf

Discussion in 'Mission Editing' started by Matt L, Jul 11, 2013.

  1. Matt L

    Matt L OpenDayZ Rockstar!

    Joined:
    May 10, 2013
    Messages:
    841
    Likes Received:
    136
    I know this probably isn't the right place to post this but seeing as there is no troubleshooting forum (yet), I would like to take the time to ask for some help. I have been using tons of edited fn_selfActions called from the compiles.sqf for a long time, and today it just started giving me some weird random errors, saying theres a filepath error of something like \z\addons\dayz_mission\Fixes\fn_selfActions.sqf when that's not what's in the compiles, it looks like this :
    Code:
        fnc_usec_damageActions = compile preprocessFileLineNumbers "\z\addons\dayz_code\compile\fn_damageActions.sqf";        //Checks which actions for nearby casualty
        fnc_inAngleSector = compile preprocessFileLineNumbers "\z\addons\dayz_code\compile\fn_inAngleSector.sqf";        //Checks which actions for nearby casualty
        fnc_usec_selfActions = compile preprocessFileLineNumbers "Fixes\fn_selfActions.sqf";        //Checks which actions for self
        fnc_usec_unconscious = compile preprocessFileLineNumbers "\z\addons\dayz_code\compile\fn_unconscious.sqf";
        player_temp_calculation = compile preprocessFileLineNumbers "\z\addons\dayz_code\compile\fn_temperatur.sqf";        //Temperatur System //TeeChange
        player_weaponFiredNear = compile preprocessFileLineNumbers "\z\addons\dayz_code\compile\player_weaponFiredNear.sqf";
    I've tried everything I can think of, from changing the filepath to Scripts/fn_selfActions and placing it in a Scripts folder, to redoing my selfActions with a blank one, to grabbing a new compiles, to using a new pbo and placing all my scripts in one at a time...everything. Same error everytime. It's annoying beyond comprehension. I was wondering if anyone has ever experienced this and would know a fix?
     
  2. guccimane

    guccimane New Member

    Joined:
    Apr 24, 2013
    Messages:
    14
    Likes Received:
    1
    I got that message before and after researching for awhile finally found out it was because my pbo wasn't packed correctly. It might not work for you but I fixed it by downloading a stock PBO, unpacking it and then copying everything from my custom mission pack into the stock one, and repacking it.
     
  3. Matt L

    Matt L OpenDayZ Rockstar!

    Joined:
    May 10, 2013
    Messages:
    841
    Likes Received:
    136
    Tried it, worked thanks much.
     

Share This Page