Jump to content

Recommended Posts

On 2/2/2021 at 4:34 PM, PB0_CEF said:

Same answer than for TempestRiser just above 😉 Looking at Iranian Tomcats loadouts you should be able to modify US Tomcats loadouts or I will try to do one for you ...

 

Hey CEF,

I have been trying it myself but I do not get it. I made a loadout in the editor. That saved loadout you can find in 'C:\Users\******\Saved Games\DCS.openbeta\MissionEditor\UnitPayloads'. I copied the pylon/weapon information to 'db_loadouts.lua' under the heading for 'escort'. Replacing the loadout already there. This didn't work because the weapon systemd where hanging on the wrong pylons as I posted earlier.

 

This is a entry in the loadout.lua:

[10] = {
                    ["CLSID"] = "{LAU-138 wtip - AIM-9M}",
                    ["num"] = 10,

 

I noticed that the Mission editor loadout formulates it differently:

[1] = {
                    ["CLSID"] = "{LAU-138 wtip - AIM-9M}",
                    ["num"] = 10,

 

So what I did was replace the [1] and changed it to [10] because I noticed that in the db_loadouts.lua the number in front is the same as in the weapon entry. That didn't work.

 

I don't mind you 'fixing' it but I would like to understand the proces so I can modify my own loadouts to my own preferences. Wouldn't want to bother you everytime I wan't to change something.

 

Any help appreciated.

Link to comment
Share on other sites

2 hours ago, RedeyeStorm said:

 

Hey CEF,

I have been trying it myself but I do not get it. I made a loadout in the editor. That saved loadout you can find in 'C:\Users\******\Saved Games\DCS.openbeta\MissionEditor\UnitPayloads'. I copied the pylon/weapon information to 'db_loadouts.lua' under the heading for 'escort'. Replacing the loadout already there. This didn't work because the weapon systemd where hanging on the wrong pylons as I posted earlier.

 

This is a entry in the loadout.lua:

[10] = {
                    ["CLSID"] = "{LAU-138 wtip - AIM-9M}",
                    ["num"] = 10,

 

I noticed that the Mission editor loadout formulates it differently:

[1] = {
                    ["CLSID"] = "{LAU-138 wtip - AIM-9M}",
                    ["num"] = 10,

 

So what I did was replace the [1] and changed it to [10] because I noticed that in the db_loadouts.lua the number in front is the same as in the weapon entry. That didn't work.

 

I don't mind you 'fixing' it but I would like to understand the proces so I can modify my own loadouts to my own preferences. Wouldn't want to bother you everytime I wan't to change something.

 

Any help appreciated.

I will try to look at you loadout : please cut/past ditor pylons loadout and your complete escort loadout...

Your method should work ?!?

 

[/url]All known Dynamic Campaign Engine Campaigns

Last DCE news : Crisis in PG - Blue version

Link to comment
Share on other sites

Hi CEF,

 

This is what I had:

 

["Escort"] = {
            ["AIM-54C-MK47*2, AIM-7MH*3, AIM-9M*2, XT*2"] = {
                attributes = {},
                weaponType = nil,
                expend = nil,
                day = true,
                night = true,
                adverseWeather = true,
                range = 500000,
                capability = 1,
                firepower = 5,
                vCruise = 255.83333333333,
                standoff = 80300,
                -- tStation = 7200,
                LDSD = true,
                -- --- self_escort = true,
                sortie_rate = 8,
                stores = {
            ["pylons"] = {
                [10] = {
                    ["CLSID"] = "{LAU-138 wtip - AIM-9M}",
                    ["num"] = 10,
                },
                [9] = {
                    ["CLSID"] = "{SHOULDER AIM-7MH}",
                    ["num"] = 9,
                },
                [8] = {
                    ["CLSID"] = "{F14-300gal}",
                    ["num"] = 8,
                },
                [7] = {
                    ["CLSID"] = "{AIM_54C_Mk47}",
                    ["num"] = 7,
                },
                [5] = {
                    ["CLSID"] = "{BELLY AIM-7MH}",
                    ["num"] = 5,
                },
                [4] = {
                    ["CLSID"] = "{AIM_54C_Mk47}",
                    ["num"] = 4,
                },
                [3] = {
                    ["CLSID"] = "{F14-300gal}",
                    ["num"] = 3,
                },
                [2] = {
                    ["CLSID"] = "{SHOULDER AIM-7MH}",
                    ["num"] = 2,
                },
                [1] = {
                    ["CLSID"] = "{LAU-138 wtip - AIM-9M}",
                    ["num"] = 1,
                },
            }, -- end of ["pylons"]
                    ["fuel"] = "7348",
                    ["flare"] = 60,
                    ["chaff"] = 140,
                    ["gun"] = 100,
                },
                AddPropAircraft =
    {
        ["LGB100"] = 6,
        ["M61BURST"] = 0,
        ["IlsChannel"] = 11,                -- preset ILS channel
        ["LGB1"] = 8,
        ["KY28Key"] = 1,
        ["TacanBand"] = 0,
        ["ALE39Loadout"] = 3,
        ["UseLAU138"] = true,
        ["LGB10"] = 8,
        ["INSAlignmentStored"] = true,        -- fast alignment, remember to modify also the value: "startup_time_player" in this file
        ["TacanChannel"] = 37,                -- preset TACAN channel
        ["LGB1000"] = 1,
    },
            },
        },        
        ["Fighter Sweep"] = {

 

I just flew a mission where Viggen's where supposed to attack shipping. They didn't spawn in at all. In Conf_Mod.lua I have PruneStatic=false and also Triggerstart=true. If I understand correctly then the Viggens should have spawned in. I have Prunescript=true and set to 1.5. I almost is like they got pruned (their base is far from the carrier). I also noticed that at spawning in Strike Eagles and F-117 where on the apron at first but got deleted when the mission progressed.

 

Thanks for the help.

 

Edit: I have continued to muck about with the Loadout.lua. I am now officially buggerd. I can change the pylon numbers anyway I want but the placement of the weapons remains unchanged! The above loadout misses one sidewinder, and one sparrow.

 

Edit 2: Something weird is going on. Even if I remove all weapons under escort it continues to spawn the same 2 phoenix, 1 sidewinders, 2 bags and 2 sparrows. Also something funny with prunescript. I redacted out all the lines for the prunescript. Still no Viggens and no enemy fighters on the tarmac.


Edited by RedeyeStorm
Additional info
Link to comment
Share on other sites

I'm trying Crisis in PG solo missions; I downloaded and installed the Viper and Harrier versions, and tried the Harrier first.  The problem I'm having is that I can't find the Tarawa tacan.  It gives an ICLS channel 13 in the briefing, but that doesn't 'click' when I try to use it in either the TCN or AWLS.  Is there a fix you can recommend?

 

Thanks for your help and work.

Link to comment
Share on other sites

I'm trying Crisis in PG solo missions; I downloaded and installed the Viper and Harrier versions, and tried the Harrier first.  The problem I'm having is that I can't find the Tarawa tacan.  It gives an ICLS channel 13 in the briefing, but that doesn't 'click' when I try to use it in either the TCN or AWLS.  Is there a fix you can recommend?
 
Thanks for your help and work.
Correct, the ship tacan channels are not in the brief, only ICLS. Could be an oversight in the export to next mission briefing. I know the Super carrier in the Hornet campaign is 37X. You may be able to find the others somewhere in the campaign script files, using Notepad++.

Cheers!


Sent from my SM-G950F using Tapatalk

W10 Home 64Bit, Intel Skylake I5 6600K 3.50GHz, ASUS ROG Stryx Z270F MoBo, 32GB G.Skill RipJaws V DDR4 3200 RAM, Samsung 960 Pro 512GB M.2 SSD (OS), Samsung 850 Pro 512GB SSD, 2TB Seagate SDHD, 2TB WD Green HDD, GALAX GTX GeForce 1070 EXOC Sniper White 8GB VRAM

Link to comment
Share on other sites

22 hours ago, supa325 said:

I'm trying Crisis in PG solo missions; I downloaded and installed the Viper and Harrier versions, and tried the Harrier first.  The problem I'm having is that I can't find the Tarawa tacan.  It gives an ICLS channel 13 in the briefing, but that doesn't 'click' when I try to use it in either the TCN or AWLS.  Is there a fix you can recommend?

 

Thanks for your help and work.

You can verify it in the mission editor : LHA_Tarawa Tacan channel is 39X and ICLS is 13 : maybe a DCS bug ?

 

On 2/6/2021 at 3:51 PM, RedeyeStorm said:

Hi CEF,

 

This is what I had:

 

["Escort"] = {
            ["AIM-54C-MK47*2, AIM-7MH*3, AIM-9M*2, XT*2"] = {
                attributes = {},
                weaponType = nil,
                expend = nil,
                day = true,
                night = true,
                adverseWeather = true,
                range = 500000,
                capability = 1,
                firepower = 5,
                vCruise = 255.83333333333,
                standoff = 80300,
                -- tStation = 7200,
                LDSD = true,
                -- --- self_escort = true,
                sortie_rate = 8,
                stores = {
            ["pylons"] = {
                [10] = {
                    ["CLSID"] = "{LAU-138 wtip - AIM-9M}",
                    ["num"] = 10,
                },
                [9] = {
                    ["CLSID"] = "{SHOULDER AIM-7MH}",
                    ["num"] = 9,
                },
                [8] = {
                    ["CLSID"] = "{F14-300gal}",
                    ["num"] = 8,
                },
                [7] = {
                    ["CLSID"] = "{AIM_54C_Mk47}",
                    ["num"] = 7,
                },
                [5] = {
                    ["CLSID"] = "{BELLY AIM-7MH}",
                    ["num"] = 5,
                },
                [4] = {
                    ["CLSID"] = "{AIM_54C_Mk47}",
                    ["num"] = 4,
                },
                [3] = {
                    ["CLSID"] = "{F14-300gal}",
                    ["num"] = 3,
                },
                [2] = {
                    ["CLSID"] = "{SHOULDER AIM-7MH}",
                    ["num"] = 2,
                },
                [1] = {
                    ["CLSID"] = "{LAU-138 wtip - AIM-9M}",
                    ["num"] = 1,
                },
            }, -- end of ["pylons"]
                    ["fuel"] = "7348",
                    ["flare"] = 60,
                    ["chaff"] = 140,
                    ["gun"] = 100,
                },
                AddPropAircraft =
    {
        ["LGB100"] = 6,
        ["M61BURST"] = 0,
        ["IlsChannel"] = 11,                -- preset ILS channel
        ["LGB1"] = 8,
        ["KY28Key"] = 1,
        ["TacanBand"] = 0,
        ["ALE39Loadout"] = 3,
        ["UseLAU138"] = true,
        ["LGB10"] = 8,
        ["INSAlignmentStored"] = true,        -- fast alignment, remember to modify also the value: "startup_time_player" in this file
        ["TacanChannel"] = 37,                -- preset TACAN channel
        ["LGB1000"] = 1,
    },
            },
        },        
        ["Fighter Sweep"] = {

 

I just flew a mission where Viggen's where supposed to attack shipping. They didn't spawn in at all. In Conf_Mod.lua I have PruneStatic=false and also Triggerstart=true. If I understand correctly then the Viggens should have spawned in. I have Prunescript=true and set to 1.5. I almost is like they got pruned (their base is far from the carrier). I also noticed that at spawning in Strike Eagles and F-117 where on the apron at first but got deleted when the mission progressed.

 

Thanks for the help.

 

Edit: I have continued to muck about with the Loadout.lua. I am now officially buggerd. I can change the pylon numbers anyway I want but the placement of the weapons remains unchanged! The above loadout misses one sidewinder, and one sparrow.

 

Edit 2: Something weird is going on. Even if I remove all weapons under escort it continues to spawn the same 2 phoenix, 1 sidewinders, 2 bags and 2 sparrows. Also something funny with prunescript. I redacted out all the lines for the prunescript. Still no Viggens and no enemy fighters on the tarmac.

 

Sorry loadout seems good for me ... I don't know exactly what is wrong with it. Did you download the knew Crisis campaign to look at iranien F-14A with such kind of loadout ?

[/url]All known Dynamic Campaign Engine Campaigns

Last DCE news : Crisis in PG - Blue version

Link to comment
Share on other sites

I have edited the bat file for my PC and the first mission bat still will not work. I have also checked that its point to the correct script version.

 

REM Core or Main DCS ou DCS.beta path, always end the line with \
set "pathDCS=C:\Program Files\Eagle Dynamics\DCS World OpenBeta\"

 

REM DCS or DCS.beta saved game path, always end the line with \
set "pathSavedGames=C:\Users\Herman\Saved Games\" 

 

REM DCE ScriptMod version not any / or \ and no space before and after =
set "versionPackageICM=20.43.60"

 

I do not understand the issue.
 

Link to comment
Share on other sites

7 hours ago, PB0_CEF said:

You can verify it in the mission editor : LHA_Tarawa Tacan channel is 39X and ICLS is 13 : maybe a DCS bug ?

 

I'll check it out, I just didn't see any Tacan channel attached to the Tarawa in the brief or any of the .lua files, but I probably wasn't looking hard enough in the .lua files.

Thanks for the reply

Link to comment
Share on other sites

8 hours ago, grant977 said:

REM DCS or DCS.beta saved game path, always end the line with \
set "pathSavedGames=C:\Users\Herman\Saved Games\" 

This line doesn't seem good for me. Here is mine :

REM DCS or DCS.beta saved game path, always end the line with \
set "pathSavedGames=f:\Saved Games\DCS.openbeta\"

 

It seems you forget : DCS.openbeta\


Edited by PB0_CEF

[/url]All known Dynamic Campaign Engine Campaigns

Last DCE news : Crisis in PG - Blue version

Link to comment
Share on other sites

8 hours ago, grant977 said:

I have edited the bat file for my PC and the first mission bat still will not work. I have also checked that its point to the correct script version.

 

REM Core or Main DCS ou DCS.beta path, always end the line with \
set "pathDCS=C:\Program Files\Eagle Dynamics\DCS World OpenBeta\"

 

REM DCS or DCS.beta saved game path, always end the line with \
set "pathSavedGames=C:\Users\Herman\Saved Games\" 

 

REM DCE ScriptMod version not any / or \ and no space before and after =
set "versionPackageICM=20.43.60"

 

I do not understand the issue.
 

maybe
set "pathSavedGames=C:\Users\Herman\Saved Games\DCS World OpenBeta\" 

FAQ DCE (Cef & Miguel'version)

In case of problem with a mission generated by CEF's DCEs, please post as many elements as possible:

  • - the mission + the tacview + a screenshot of the bug window + Give the name of the campaign + version of the scriptsMod

DCE_Manager


News : Crisis in Persian Gulf, one campaign, 13 modules (29/12/2023)

Link to comment
Share on other sites

Here is what I have now this is the exact path to my saved games folder and the location of the main DCS folder.

 

REM Core or Main DCS ou DCS.beta path, always end the line with \
set "pathDCS=C:\Program Files\Eagle Dynamics\DCS World OpenBeta\"

 

REM DCS or DCS.beta saved game path, always end the line with \
set "pathSavedGames=C:\Users\Herman\Saved Games\DCS.openbeta\"

 

REM DCE ScriptMod version not any / or \ and no space before and after =
set "versionPackageICM=20.43.60"

Link to comment
Share on other sites

Hey CEF,

 

22 hours ago, PB0_CEF said:

You can verify it in the mission editor : LHA_Tarawa Tacan channel is 39X and ICLS is 13 : maybe a DCS bug ?

 

Sorry loadout seems good for me ... I don't know exactly what is wrong with it. Did you download the knew Crisis campaign to look at iranien F-14A with such kind of loadout ?


I will check it out. Not much time at the moment. It really is weird. I even removed everything except two sidewinders. Saved the lua. Used first mission.bat but got the same weird loadout. Further more there are no Viggen in any mission not as statics and do not show when I got a mission to escort them. No errors where thrown up either. They where in the luas like other planes an where in the order of battle.

Link to comment
Share on other sites

3 hours ago, RedeyeStorm said:

Hey CEF,

 


I will check it out. Not much time at the moment. It really is weird. I even removed everything except two sidewinders. Saved the lua. Used first mission.bat but got the same weird loadout. Further more there are no Viggen in any mission not as statics and do not show when I got a mission to escort them. No errors where thrown up either. They where in the luas like other planes an where in the order of battle.

For the Viggen it's a now known bug : It needs to have at least one sweden ground objet in the base_mission to work so if you are able to edit the base_mission, add one sweden ground unit somewhere and then it will work but you will have to restart the whole campaign sorry 😞

 

[/url]All known Dynamic Campaign Engine Campaigns

Last DCE news : Crisis in PG - Blue version

Link to comment
Share on other sites

22 hours ago, grant977 said:

I have edited the bat file for my PC and the first mission bat still will not work. I have also checked that its point to the correct script version.

 

REM Core or Main DCS ou DCS.beta path, always end the line with \
set "pathDCS=C:\Program Files\Eagle Dynamics\DCS World OpenBeta\"

 

REM DCS or DCS.beta saved game path, always end the line with \
set "pathSavedGames=C:\Users\Herman\Saved Games\" 

 

REM DCE ScriptMod version not any / or \ and no space before and after =
set "versionPackageICM=20.43.60"

 

I do not understand the issue.
 

What exactly do you get as an error message?
Can you make a screen print?

(is it the firsMission.bat that bug?)

FAQ DCE (Cef & Miguel'version)

In case of problem with a mission generated by CEF's DCEs, please post as many elements as possible:

  • - the mission + the tacview + a screenshot of the bug window + Give the name of the campaign + version of the scriptsMod

DCE_Manager


News : Crisis in Persian Gulf, one campaign, 13 modules (29/12/2023)

Link to comment
Share on other sites

When Im down laod i then Copy and paste tech to Users/UserName/saved
games/ Dcs.openbeta /Mods/ » folder : and it looks nothing like the file tree shown in read me When I open the mods folder it looks completely different 

dcs.png

mods.png

Tech.png


Edited by RePhil
added tech file

[sIGPIC][/sIGPIC]

Window 10, i9-9900,2080TI, 32GB ram Puma Pro Flight Trainer, 2 x 1TB WB SSD NVMe HP Reverb

Link to comment
Share on other sites

7 hours ago, RePhil said:

When Im down laod i then Copy and paste tech to Users/UserName/saved
games/ Dcs.openbeta /Mods/ » folder : and it looks nothing like the file tree shown in read me When I open the mods folder it looks completely different 

dcs.png

mods.png

Tech.png

 

there is no bp
You only have 2 more directories than CEF in its PDF:
Mods/Services
Mods/Static Templates

And you can't compare your "tech" folder with that of CEF, since it hasn't published its composition.

In short, you have installed many, many Mods and it is normal that the content is different.

nothing abnormal...


Edited by Miguel21

FAQ DCE (Cef & Miguel'version)

In case of problem with a mission generated by CEF's DCEs, please post as many elements as possible:

  • - the mission + the tacview + a screenshot of the bug window + Give the name of the campaign + version of the scriptsMod

DCE_Manager


News : Crisis in Persian Gulf, one campaign, 13 modules (29/12/2023)

Link to comment
Share on other sites

On 1/12/2021 at 3:40 PM, MAXsenna said:

Salute?

Sent from my MAR-LX1A using Tapatalk
 

You have to use Lshift U or bind one of your hotas controls to the catapult shoot function. Those are the only 2 ways you get launcehed ina F-14

 


Edited by Orestd
Link to comment
Share on other sites

getting this error message.

Getting this scripting error>[string
c:\users\my name\appData\local\temp\DCS.OpenBeta (a nil value)
stack trace back
c:?
{
[string
c:\users\my name\appData\local\temp\DCS,OpenBeta V~mis00003559.lua]239: in function on event
[string scripts/world/eventHandlers.lua) 13: in
function<string "scripts/world/eventhandlers.lua"]:11>

i have rechecked and rechecked the path bat everything looks good. The thing with this message is when you hit enter it disappears and you get into the main menu where you can end the mission. The only thing is it does not record my kills. I shot down 2 aircraft and it had my air to air kills at 0.  Anyone have a clue how to fix this.

Link to comment
Share on other sites

7 hours ago, rollnloop said:

In the path file , check the directories names end with a \, as in DCS.OpenBeta\

Hi thanks for your reply. Yes all the directory names have \" at the end. Now I went into the log file to look for the error message and see if it could give me an indication of what is going on. I found the error message and for some reason it is looking for the saved games directory in f: I don't have an f: directory and I did changed the path.bat to c the funny thing is that the original path.bat pointed to f. I don't know if that is a coincidence or something else. 

Link to comment
Share on other sites

If the problem continues
Can you tell us which campaign it is?
And give us the log too?

FAQ DCE (Cef & Miguel'version)

In case of problem with a mission generated by CEF's DCEs, please post as many elements as possible:

  • - the mission + the tacview + a screenshot of the bug window + Give the name of the campaign + version of the scriptsMod

DCE_Manager


News : Crisis in Persian Gulf, one campaign, 13 modules (29/12/2023)

Link to comment
Share on other sites

2 hours ago, Miguel21 said:

If the problem continues
Can you tell us which campaign it is?
And give us the log too?

I have 3 dynamic campaigns and all three have the same problem. All three are crisis in the Persian Gulf for the F-14, F-16, and F-18. I have attached the log. I will supply the path.bat for one of the campaigns. I don't know maybe it is something I did incorrectly maybe you can see it. Thank you.

dcs.log

path.bat


Edited by Orestd
Link to comment
Share on other sites

I confirm, you have a problem  of path saved games
you gave this in the game: f:\Saved Games\DCS.openbeta\

3 errors:
-1-
This is not the right reader (I understand yours is c:)

-2-
And there is no user in your path:
set "pathSavedGames=c:\users\my name\DCS.openbeta\"

-3-
you didn't recreate the first mission , the one that writes all this in the campaign database.
to do for each campaign

 

PS: I will provide you with an intaller.exe that we are trying to develop, I will send it to you by mp, you will tell me if it works.


Edited by Miguel21

FAQ DCE (Cef & Miguel'version)

In case of problem with a mission generated by CEF's DCEs, please post as many elements as possible:

  • - the mission + the tacview + a screenshot of the bug window + Give the name of the campaign + version of the scriptsMod

DCE_Manager


News : Crisis in Persian Gulf, one campaign, 13 modules (29/12/2023)

Link to comment
Share on other sites

 

10 hours ago, Miguel21 said:

I confirm, you have a problem  of path saved games
you gave this in the game: f:\Saved Games\DCS.openbeta\

3 errors:
-1-
This is not the right reader (I understand yours is c:)

-2-
And there is no user in your path:
set "pathSavedGames=c:\users\my name\DCS.openbeta\"

-3-
you didn't recreate the first mission , the one that writes all this in the campaign database.
to do for each campaign

 

PS: I will provide you with an intaller.exe that we are trying to develop, I will send it to you by mp, you will tell me if it works.

 

Thank you. I installed the first campaign for the f-16. Worked perfectly. I didn't test it extensively just started the campaign and exited. The error message did not pop up. A text file with a summary of the mission did pop up as it is supposed to. I then installed the F-14 Tom Cat and the  F-18 Hornet But for those 2 campaigns the error message popped up and the summary text file did not. I checked the path.bat for all three they looked identical. I have no idea why it is working for one and not the other 2. I have attached the log file and the path bat for all 3 campaigns. The first one is the f-16 which is working. The next one is the f-14 and the f-18 which are not working..

dcs.log path.bat path.bat path.bat


Edited by Orestd
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...