Jump to content

adriansito123

Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by adriansito123

  1. hace 1 hora, rob10 dijo:

    Check out this thread:

    Thanks man, seems like they are working on it from what I can read. I searched specifically for bugs regarding the 87's and couldn't find this thread.

     

    • Like 1
  2. So i discovered this when doing some pop up attacks training with the cbu-87's against SAM sites (the first mission of FIWOS campaign) and noticed that the bombs always landed long of the target. After some investigation I saw that i ignored the AD and BA settings of the bomb, which at that time where set at AD 1.000 secs and BA 4921 ft. When i tried to change those settings so they would fit my engagement parameters, the values I entered where ignored, meaning that when i leave the CTRL page and go back to the SMS page the values for AD and BA would still be the same as before (1.000 secs and 4921 ft respectively). I report this as a bug because I've just seen older videos of this exact same procedure working correctly.

    I've also tried the same in a simple mission I created to see if it was a mission bug or setting special to that mission but i gathered the same results.

  3. hace 26 minutos, Miguel21 dijo:

    ha ok, I understand better ^^

    in fact, you have 2 possibilities:

    1/ or you just modify the MissionScripting.lua file that was already in the open_Beta folder

    /2 or you install the MissionScripting.lua file with OvGME

    But you don't do both

    And I think your installation of OvGME is wrong.

    If you want to use OvGME, I advise you to watch some tutorial videos

    I see.

    The thing here is that I did not modify the file before the first time the warning message popped up, the file that i posted before is as how it was the first time I installed the mod with OvGME

  4. hace 6 horas, Miguel21 dijo:

    the modification seems well

    now we're going to check if the location of this file is correct:

    which DCS are you using? (Open Beta?)

    Can you post a printScreen of your installation (windows explorer) with developed tree on the left?

    Yes I play in Open Beta, here is the screenshot.

    Captura.PNG

     

     

  5. hace 5 horas, Miguel21 dijo:

    Hi
    Yes, as long as the file is not modified "correctly", the message will appear.

    and you have to do it again at each DCS update
    It is also necessary not to make a mistake with the file, especially if you have 2 installations of DCS (open Beta)

    But you have the possibility to do it "automatically" via the OvGME software

    Look at the PDF, which is in each campaign zip

     

    edit: be careful, if you modify MissionScripting.lua yourself, check if the file encoding is respected (ANSI or UTF8, but not UTF8-BOM for example)

     

    Hi again.

    I don't mind editing the file myself every time dcs updates, could you tell me which modifications do i need to make?. I will add the full content of the file so you can mark which line I should edit and how.

    Thanks for the reply anyways :).

    Edit: I checked and the files are in UTF-8

     

    --Initialization script for the Mission lua Environment (SSE)

    dofile('Scripts/ScriptingSystem.lua')

    --Sanitize Mission Scripting environment
    --This makes unavailable some unsecure functions.
    --Mission downloaded from server to client may contain potentialy harmful lua code that may use these functions.
    --You can remove the code below and make availble these functions at your own risk.

    local function sanitizeModule(name)
        _G[name] = nil
        package.loaded[name] = nil
    end

    do
    --    sanitizeModule('os')
    --    sanitizeModule('io')
        sanitizeModule('lfs')
        require = nil
        loadlib = nil
    end

  6. Hi Miguel, this is the first time I play one of your dynamic campaigns. When starting the first mission a message appears on the up-right corner of the screen saying the following:

     

    WARNING: sanitizeModule('os') in MissionScripting.lua has not been disabled. Mission results will not be accounted nd campaign will not progress.

    I have tried editing said file but with no results, the warning keeps popping up every time. Any advice?

    Thanks

  7. So first of all, exuse my english.

     

    During a long period of time i've been trying to finish the "Bee Swarm Bay" instant action mission that is available for the F16 in the Persian Gulf map.

     

    The mission says that you have to defend an airfield against a swarm of attacking helicopters, but after a random period of time the pop up message appears saying: "Mission failed, the helicopters have taken the airfield", when in reality and after checking the tacview files, there are no troops or helos in the area close enough for the airfield, and of course not landed.

     

    This is the first post i think i made in any forum because i haven't found any other post talking about this and i'm desperated to know if i'm doing something wrong or what, if there is a trigger that im missing or something.

    • Like 1
×
×
  • Create New...