Jump to content

Recommended Posts

Posted

Bump.

What a great campaign and I’m only on M2!

Bit annoyed I failed though because I switched to ATC before the prompt on way home and the trigger didn’t, er, trigger.

Minor issue though, I’ll just wait for all instructions. Can’t wait to do the rest thanks Sedlo.

  • Like 2
Posted
4 hours ago, L4key said:

Bump.

What a great campaign and I’m only on M2!

Bit annoyed I failed though because I switched to ATC before the prompt on way home and the trigger didn’t, er, trigger.

Minor issue though, I’ll just wait for all instructions. Can’t wait to do the rest thanks Sedlo.

Glad you're enjoying it so far.  The push to marshall will happen sometimes as close in as 20 miles.  Generally it's 20-40 miles out.  I know IRL it can be further out, but in the confines of the Strait I kept it shorter.

Enjoy!  I really hope you like the rest, too.

  • Like 2
  • 2 weeks later...
Posted

Ok so one question - does the skip forward work in the radio menu? I tried it on M4 to take me to the push point and it exited me to the debrief screen.

Tried it from the deck and airborne and did same both times, am I doing something wrong?

TIA

Posted
14 minutes ago, L4key said:

Ok so one question - does the skip forward work in the radio menu? I tried it on M4 to take me to the push point and it exited me to the debrief screen.

Tried it from the deck and airborne and did same both times, am I doing something wrong?

TIA

Hmm, I'll check, standby

Posted

@L4key, I just tried it, all seems to be working on my end.  Make sure you have both

Bold Cheetah Mission 04 - Retribution_Cold Start.miz

AND 

Bold Cheetah Mission 04 - Retribution_Start from Push.miz

all in the same directory on your machine.

If that is not the issue, then I'm thinking it's possibly a mod that is conflicting?  

 

  • Like 1
Posted

Hello Sedlo!

I'm loving this campaign, but unfortunately DCS crashes when I try to run Mission 4: Retribution

It crashes on loading page. The other missions I completed without any problems.

Any thoughts?

I use Stable Version 2.8.0.42718 (Multi-threading)

Tks in advance.

RYZEN 7 2700 3.2 GHz / GAINWARD RTX 2070 / 32 GB RAM 3200 MHz / ASUS PRIME B450M / M.2 NVMe KINGSTON 1TB / SSD SANDISK 480GB / HD 2TB SATA3 / CORSAIR CX650 / AOC AGON AG322FCX MONITOR / THRUSTMASTER T.16000M FCS / CUSTOM HEADTRACK

F-14 Tomcat Side View.png

Posted

Hmm… missions 1-3, did you fly them recently?   I’m wondering because I added an unlimited fuel trigger to Bold Cheetah with the release of 2.9.

I didn’t think it would crash stable, but that is, perhaps what is happening

Did you get a script error? Or did it just ?

I just flew mission 4 in 2.9 multi thread the other day and it had no crashing issue.  

Other than the fuel trigger, I don’t know what would be causing it.

 

Other than the fuel trigger, I don’t know what would be causing it.

If you have a dcs.log file you could send it could help.  You can DM it if you’ve got it. 
 

The other reason, and a request cause of issues I’ve found is mods.  Are you running any, and if so, which ones?

cheers,

 

Sedlo

 

  • Like 1
Posted (edited)
On 11/24/2023 at 11:14 PM, Sedlo said:

@L4key, I just tried it, all seems to be working on my end.  Make sure you have both

Bold Cheetah Mission 04 - Retribution_Cold Start.miz

AND 

Bold Cheetah Mission 04 - Retribution_Start from Push.miz

all in the same directory on your machine.

If that is not the issue, then I'm thinking it's possibly a mod that is conflicting?  

 

Hi, checked and it’s in there. I don’t think I have any mods.

is there a specific time to select the option or can you do it as soon as you load up and are on deck?

Thanks

 

Edit: it’s ok - just tried again and it worked!
 

awesome campaign still!

Edited by L4key
Posted
3 hours ago, L4key said:

Hi, checked and it’s in there. I don’t think I have any mods.

is there a specific time to select the option or can you do it as soon as you load up and are on deck?

Thanks

 

Edit: it’s ok - just tried again and it worked!
 

awesome campaign still!

 

You can do it from the time you spawn until push time, then the option is removed.  
 

glad it’s working for you. 

Posted
10 hours ago, Sedlo said:

Hmm… missions 1-3, did you fly them recently?   I’m wondering because I added an unlimited fuel trigger to Bold Cheetah with the release of 2.9.

I didn’t think it would crash stable, but that is, perhaps what is happening

Did you get a script error? Or did it just ?

I just flew mission 4 in 2.9 multi thread the other day and it had no crashing issue.  

Other than the fuel trigger, I don’t know what would be causing it.

 

Other than the fuel trigger, I don’t know what would be causing it.

If you have a dcs.log file you could send it could help.  You can DM it if you’ve got it. 
 

The other reason, and a request cause of issues I’ve found is mods.  Are you running any, and if so, which ones?

cheers,

 

Sedlo

 

Hello Sedlo, tks for the rapid response.

Now I'm not at my DCS PC, but later I can send the log.

About mods, I have the A-4E Community, SRS and scratchpad.

About the campaign version, I'm confused. I'm using the last release: "version 2.9.A001a Updated Oct.26, 2023" in the title. But in description it's written "This campaign is designed and tested for DCS versions 2.8.0.32066 and later"

My DCS version is Stable Version 2.8.0.42718 (Multi-threading) as stated in my 1st post. If your campaign is for "2.8.0.32066 and later" it should run fine. If it's based on actual Open Beta 2.9 version, then I'll wait for Stable to reach 2.9 version to continue the campaign.

RYZEN 7 2700 3.2 GHz / GAINWARD RTX 2070 / 32 GB RAM 3200 MHz / ASUS PRIME B450M / M.2 NVMe KINGSTON 1TB / SSD SANDISK 480GB / HD 2TB SATA3 / CORSAIR CX650 / AOC AGON AG322FCX MONITOR / THRUSTMASTER T.16000M FCS / CUSTOM HEADTRACK

F-14 Tomcat Side View.png

Posted

Sorry, I forgot to update the "for 2.8.0 or later" part.  I'll change it to "latest open beta", as that's what I've been doing lately.  

Sorry for the confusion, and yeah, if you could update to the latest 2.9 Open Beta, that would work well for this one.  Still not entirely sure why you got the issue there, but I'm assuming it's a 2.9 thing.

  • Thanks 1
Posted (edited)

So I think we've found the problem, I'm still running DCS Stable 2.8 and your campaign was updated to Open Beta 2.9.

For a long time I have resisted to update from stable to open beta, but now I think I'll do it.

Edited by =Skywarp=

RYZEN 7 2700 3.2 GHz / GAINWARD RTX 2070 / 32 GB RAM 3200 MHz / ASUS PRIME B450M / M.2 NVMe KINGSTON 1TB / SSD SANDISK 480GB / HD 2TB SATA3 / CORSAIR CX650 / AOC AGON AG322FCX MONITOR / THRUSTMASTER T.16000M FCS / CUSTOM HEADTRACK

F-14 Tomcat Side View.png

Posted

Yeah, update finished now

Time to launch it!!

  • Like 1

RYZEN 7 2700 3.2 GHz / GAINWARD RTX 2070 / 32 GB RAM 3200 MHz / ASUS PRIME B450M / M.2 NVMe KINGSTON 1TB / SSD SANDISK 480GB / HD 2TB SATA3 / CORSAIR CX650 / AOC AGON AG322FCX MONITOR / THRUSTMASTER T.16000M FCS / CUSTOM HEADTRACK

F-14 Tomcat Side View.png

Posted

Alright Sedlo, in 2.9 it worked as intended!!

Thank you very much for your help!!

  • Like 1

RYZEN 7 2700 3.2 GHz / GAINWARD RTX 2070 / 32 GB RAM 3200 MHz / ASUS PRIME B450M / M.2 NVMe KINGSTON 1TB / SSD SANDISK 480GB / HD 2TB SATA3 / CORSAIR CX650 / AOC AGON AG322FCX MONITOR / THRUSTMASTER T.16000M FCS / CUSTOM HEADTRACK

F-14 Tomcat Side View.png

Posted
2 hours ago, =Skywarp= said:

Alright Sedlo, in 2.9 it worked as intended!!

Thank you very much for your help!!

Awesome!  Please reach out if you have any questions, I'll be here.  I also hope you enjoy the missions!  5, 9, 10, 12 and 13 are my favourites 🙂

  • Thanks 1
Posted

Hi Sedlo,

I also had a problem with mission #4, but firstly, I suspected the issue would be with my PC, so I contacted DCS support in order to analyze the crash logs properly.

Now reading the most recent posts, I know the root cause is the difference between cilent versions (I am using the official DCS 2.8 while the campaign is shaped to 2.9 openbeta), but I would like to share the results with you, maybe it could be helpful for future development and/or bug fixes.

From your log:
2023-11-26 19:21:06.149 ALERT   APP (Main): Unhandled exception: "WrappedAction" unable to create action "SetUnlimitedFuel"
from my log:
2023-11-26 19:35:13.941 ALERT   APP (Main): Unhandled exception: "WrappedAction" unable to create action "SetUnlimitedFuel"

Disabling the "Unlimited Fuel" option in the game settings cannot change the onset of the crash.
This is a mission error. You can tell this to the mission developer (one of the enthusiastic players) if you wish. 

 

As for the campaign, I enjoy it greatly and I cant wait to continue

 

  • Like 1
Posted

@Sedlo Yes the mission #4 crashed the DCS during loading. (this is the most recent topic here, and I tried to "follow-up" the thread, next time I will be more clear)

I am using 2.8 (as I mentioned above) and I know I should use the 2.9 openbeta.

And I just wanted to share the info that I got from support that the fuel trigger causes the issue that you suspected this post:

On 11/26/2023 at 6:36 AM, Sedlo said:

Hmm… missions 1-3, did you fly them recently?   I’m wondering because I added an unlimited fuel trigger to Bold Cheetah with the release of 2.9.

I didn’t think it would crash stable, but that is, perhaps what is happening

Did you get a script error? Or did it just ?

I just flew mission 4 in 2.9 multi thread the other day and it had no crashing issue.  

Other than the fuel trigger, I don’t know what would be causing it.

 

Other than the fuel trigger, I don’t know what would be causing it.

If you have a dcs.log file you could send it could help.  You can DM it if you’ve got it. 
 

The other reason, and a request cause of issues I’ve found is mods.  Are you running any, and if so, which ones?

cheers,

 

Sedlo

 

 

 

 

  • Like 1
Posted
On 11/27/2023 at 7:26 PM, Only__Legs said:

@Sedlo Yes the mission #4 crashed the DCS during loading. (this is the most recent topic here, and I tried to "follow-up" the thread, next time I will be more clear)

I am using 2.8 (as I mentioned above) and I know I should use the 2.9 openbeta.

And I just wanted to share the info that I got from support that the fuel trigger causes the issue that you suspected this post:

 

 

 

Changing to Open Beta solved the problem for me

And now I can play with my friends as most of them always used OB \o/

  • Like 1

RYZEN 7 2700 3.2 GHz / GAINWARD RTX 2070 / 32 GB RAM 3200 MHz / ASUS PRIME B450M / M.2 NVMe KINGSTON 1TB / SSD SANDISK 480GB / HD 2TB SATA3 / CORSAIR CX650 / AOC AGON AG322FCX MONITOR / THRUSTMASTER T.16000M FCS / CUSTOM HEADTRACK

F-14 Tomcat Side View.png

Posted

Hi Sedlo,

 

thanks for the campaign. I got to mission 7 but the Tomcats line up faster than I start and then block the cats....probably a standard DCS AI/Pathing/Carrier type issue but wanted to let you know in case you can work round it for your next update. I've skipped onwards. Small track attached, minimal startup but it shows the issue. I run no mods to the DCS files except I have edited my CMD_ALE47.lua to pre-program my countermeasures and use custom binds.

BC_M7_TomcatBlocks.trk

Posted

OK, @TrigatiI just ran your track but it cut off before the last Tomcat launche.  I then tried it myself and all appeared to work just fine, all F-14 cleared the cats and took of normally.  I will try once more, but I cannot seem to duplicate. 

I'd say maybe try it again?  It could be a one-off thing.

  • Recently Browsing   0 members

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