Fix the F-15C Single Player Configurations Please!

[JUICE-AWG]

:thumbup: ED/DCS, Please fix the F-15C single player missions to equip both wings with a pylon. Currently all the air-start missions begin with a single wing pylon with ACMI pod on it and the asymmetrical load is unrealistic. I know can change all this in the mission editor, but it will only return with each update.

 

Also, for the F-15C Landing Mission, reduce internal fuel to about 8,000 pounds to get players close to the realistic landing weight.

 

On an additional note, why can't you correctly encode the data needed to make the magnetic headings read correct on the compass when aligned on the runway. True course is irrelevant as it only reflects the runway alignment relative to True North. Pilots need "Magnetic Readings for the fields in the earth under that point on the globe to land, not the difference for the TRUE indications. Read this and let me know if you need help figuring it out...:pilotfly:

https://en.wikipedia.org/wiki/Runway

 

This heading differs from true north by the local magnetic declination. A runway numbered 09 points east (90°), runway 18 is south (180°), runway 27 points west (270°) and runway 36 points to the north (360° rather than 0°). When taking off from or landing on runway 09, a plane would be heading 90° (east).

[JUICE-AWG]

Detailed breakdown on runway 03 at Nellis AFB. Of course I'm using the FC3 F-15C aircraft which you can't change the HSI in cockpit.

 

https://forums.eagle.ru/showthread.php?p=3241286#post3241286

Edited September 9, 2017 by =JUICE=

[Crew Dog]

Runway numbering is rounded to the nearest ten degrees, so for example, a runway marked "11" could be anywhere from 105 to 114

[Bulldog_1]

:thumbup: ED/DCS, Please fix the F-15C single player missions to equip both wings with a pylon. Currently all the air-start missions begin with a single wing pylon with ACMI pod on it and the asymmetrical load is unrealistic. I know can change all this in the mission editor, but it will only return with each update.

 

Also, for the F-15C Landing Mission, reduce internal fuel to about 8,000 pounds to get players close to the realistic landing weight.

 

+1

[draconus]

:thumbup: ED/DCS, Please fix the F-15C single player missions

 

+1

1. Known bug in Caucasian "fighter sweep" mission where your wingman blows up right after starting taxi because the truck stays so close that aircraft crashes into it.

2. Problems with Caucasian campaign - mission#6 "mozdok strike" where you could not send SEAD strike or the F-15E strike is jettisonig all their weapons while beaing attacked.

[MadDog-IC]

+1

1. Known bug in Caucasian "fighter sweep" mission where your wingman blows up right after starting taxi because the truck stays so close that aircraft crashes into it.

 

Checked on mission #7 Fighter sweep and flight starts on runway nowhere near a truck and take off successfully.

 

2. Problems with Caucasian campaign - mission#6 "mozdok strike" where you could not send SEAD strike or the F-15E strike is jettisoning all their weapons while being attacked.

Are you referring to how it was some time back, as the F-15 Bear Trap campaign had a revamp about a year ago, and I just re-tested Mission #6 with the english version of DCS 1.57x and it plays out fine.

 

SEAD and STRIKE aircraft are programmed to not jettison weapons under any conditions (Especially whilst being attacked), this was a new setting when dcs 1.5x came out.

 

And all radio commands to send in SEAD worked appropriately, with the result of all SAMS destroyed and strike package hitting the runway.

 

Sounds like your are playing an older version of DCS or a non-english version that wasn't updated, because these issues don't exist in my english version. The modified versions in english are available on the Eagle Dynamics website under user files.

 

https://www.digitalcombatsimulator.com/en/files/?PER_PAGE=100&arrFilter_pf%5Bfiletype%5D=&arrFilter_pf%5Bgameversion%5D=&arrFilter_pf%5Bfilelang%5D=&arrFilter_pf%5Baircraft%5D=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=MadDog-IC&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter

 

Regards, Ian.

Edited November 25, 2017 by MadDog-IC

[draconus]

Checked on mission #7 Fighter sweep and flight starts on runway nowhere near a truck and take off successfully.

 

I am sorry, I really meant the "Clean Sweep" single player mission. This is what I see at the start:

Any doubts? As soon as I taxi and turn left this guy starts rolling and blows up.

 

And all radio commands to send in SEAD worked appropriately, with the result of all SAMS destroyed and strike package hitting the runway.

 

Just to be clear I run updated DCS EN ver 1.5.7x and I just played recently the "OCA strike on Mozdok" a few times without success so I began to wander and checked the forums, so I didn't know if the mission was fixed or not, because I had the symptoms that it did not. Then I tried the mission from your fix (thx man!) and finally beat it whith proper success message and F10 options working. You fixed it yourself not so long ago so don't tell me it's all fine.

 

After your post, last night, I got back to the original mission and gave it a try. The F10 call option does not disappear (wherever I call them, WP1-4) but it looks like it does push the strike - being less experienced before I thought it did nothing. I survived through the mission this time and RTB but did not get "mission success" message nor do I know it from the briefing log. Can you tell from log?

Edited November 26, 2017 by draconus
update

[feefifofum]

Check your score at any time with the ' key.

If result > 50 the mission is considered successful and the campaign will progress.

 

For Clean Sweep, open the mission in the editor and move the truck over. You've identified the issue, just click and drag the problematic unit out of the way. :thumbup:

[MadDog-IC]

I am sorry, I really meant the "Clean Sweep" single player mission. This is what I see at the start:

 

Whilst I don't doubt what you are seeing, I am seeing things totally differently on my Dcs 1.57.11762 install, which lead me to believe you don't have the latest.

 

I had checked that mission also, in the version that I have with the game, those 2 trucks are now beside the players aircraft but out a lot further of the tarmak as to be not a problem.

 

I even checked "Clean Sweep" in the older Dcs version v1.216 and it looked like the picture you posted with the two trucks too close in the parking bay opposite the players spawn point.

 

ED did update all of the the missions in "d:\Games\DCS World\Mods\aircraft\Flaming Cliffs\Missions\Single" recently, to add multi language support so mission files are now dated 27-05-2017. I would check that to see if you have same.

 

As a side note, the missions editor does have a nasty habit of forgetting where the aircrafts parking slot is assigned and randomly placing them else where which can cause issues like you describe, but doesn't appear to be the issue here.

 

Just to be clear I run updated DCS EN ver 1.5.7x and I just played recently the "OCA strike on Mozdok" a few times without success so I began to wander and checked the forums, so I didn't know if the mission was fixed or not, because I had the symptoms that it did not. Then I tried the mission from your fix (thx man!) and finally beat it with proper success message and F10 options working. You fixed it yourself not so long ago so don't tell me it's all fine.

 

Just to be clear, my original updates to the F-15 Bear trap campaign were completed around 03-10-2016 (over a year ago), they were then only updated recently 04-03-2017 to only correct the refueling tanker speeds and mission 1 where a missile problem was introduced with a dcs patch to do with the SEAD.

 

So over a year ago they were completed, and sortly after that they were incorporated into the DCS game engine by Eagle dynamics for release with the Flaming cliffs 3 module. So that means that the game has exactly the same mission set as my files available from the user files download section.

 

This is why I think something is a miss with your install:

 

1. I have had this issue before with other users, there issue was they were running a foreign russian version of DCS, which were never updated, only english version.
   
2. Do you have the full Flaming Cliffs 3 module, or just the F-15c standalone module, there has to be a reason we are seeing different things in mission.
   
3. Most of the issue your are describing with the campaign and single player missions are all related to older versions of the missions, I know because I have already fixed them before, I just haven't posted the single player missions anywhere.
   

 

After your post, last night, I got back to the original mission and gave it a try. The F10 call option does not disappear (wherever I call them, WP1-4) but it looks like it does push the strike - being less experienced before I thought it did nothing. I survived through the mission this time and RTB but did not get "mission success" message nor do I know it from the briefing log. Can you tell from log?

 

No the log is no help to me, but you can check your progress anytime in mission with the ' key it will show your RESULTS (50 for starting the mission and only goes to 100 when you have completed the requirements for the mission as per the brief), if you get no mission complete message and your RESULT is still 50 you haven't done the mission correctly, or mission may be bugged in some way.

 

My repair log tells me with original mission logic was broken so mission complete was impossible and had issues with radio commands to other flights such as SEAD, Strike:

 

------------------------

Mission - BEAR TRAP - 06 (Escort OCA strikes on Mozdok).miz

------------------------

- Triggers

- Added Win and Loss messages.

- Removed Flag=50 from Loss trigger - Should only be on for Win

- Total rewrite of US Sead and US Strike hold and radio commands for timing (Changed flags on orbits to suit)

- Added Voice overs

 

- Waypoints

-

- All CAP aircraft set to cap -a -x and Engage in zones set.

- All SEAD aircraft set to sead -a -x and Engage in zones set.

- Added "Switch waypoint" commands to make all attack aircraft loiter around Battle area

-

- Fixed Airport Coalitions

 

- Units

- Fixed all US aircraft Callsign Numbers

- Changed US STRIKE 1 + 2 flight path to stay low on run in to runway bombing

- Changed US SEAD 1 + 2 + 3 Flights from 2 to 4 ship so able to take out SA-11 batteries

 

- DCS v1.5x compatability

-

- Changed - US Sead Flight 1+2+3 - Reaction to Threat = Evasive Maneuvers, Restrict Jettison = ON

- Changed - US Strike 1+2 Flights - Reaction to Threat = Evasive Maneuvers, Restrict Jettison = ON

- Fixed - US F-15c (Player) Weapons Load out - Replaced the missing 6 x Aim-120c's on Pylons

- Changed - Weather - Set Fog ON to enable defined settings

- Works Fine

------------------------ DONE

 

Regards, Ian.

Edited November 27, 2017 by MadDog-IC

[draconus]

Do you have the full Flaming Cliffs 3 module, or just the F-15c standalone module, there has to be a reason we are seeing different things in mission.

 

This - I only have F-15C. Shouldn't the dedicated missions be no different? Am I missing some more beacause of that?

Edited November 27, 2017 by draconus
spelling

[Ironhand]

This - I only have F-15C. Shouldn't the dediacated missions be no different? Am I missing some more beacause of that?

Maybe so. I'm in a completely different spot with nothing close by at the start of Clean Sweep SP F-15C.

 

I've attached the mission I have below for you to check out.

FC3-F-15C-Clean Sweep.miz

Edited November 27, 2017 by Ironhand

[MadDog-IC]

This - I only have F-15C. Shouldn't the dedicated missions be no different? Am I missing some more because of that?

 

I wouldn't have thought they wouldn't be any different, but ED may have just forgotten to update them, as I don't just have the F-15c stand alone module I can't test. You shouldn't be missing mission per say, except the campaign missions will have a lot of issues that haven't been corrected, a list of the missions and their faults was included with the campaign mission set you downloaded from the ED user files section.

 

I would be interested in knowing what directory path the original missions are stored in, their filenames and the files time and dates, when I submit updates to them, the missions have to zipped up with exactly the same directory tree and filenames as the originals, so if the standalone F-15c module uses different paths and or filenames it would be a problem, unless ED themselves correct for it.

 

FC3 default directories:

-----------------------------

Campaigns in: ..\DCS World\Mods\aircraft\Flaming Cliffs\Missions\EN\Campaigns\FC3-F15C-06.miz

Single Missions in: ..\DCS World\Mods\aircraft\Flaming Cliffs\Missions\Single\FC3-F-15C-Clean Sweep.miz

 

Let us know how you get on.

 

Regards, Ian.

Edited November 27, 2017 by MadDog-IC

[draconus]

feefifofum: I once edited the mission, moved damn truck and saved. Worked fine but the log after mission had all object names messed up including player indication.

 

Ironhand: thx for the file.

 

MadDog-IC: Here's the list of my mission files. In case you wander about the dates - it's my DCS install time. No changes since then despite the updates. Please tell me if I'm missing some miz. Your campaign fix has just right path for the standalone module.

 

At least I had no issues with "No fly zone".

list.txt

[MadDog-IC]

feefifofum:

 

MadDog-IC: Here's the list of my mission files. In case you wander about the dates - it's my DCS install time.

 

Please tell me if I'm missing some miz. Your campaign fix has just right path for the standalone module.

 

Thanks for the file structures and names, that will come in handy if I talk to WAGS at ED about this issue. (I can only deal with the campaign missions as I haven't any releasable single player, Quick or Multiplayer mission updates for the F-15).

 

Seems that there are quite some differences:

 

1. The install path is different: ..\DCS World\Mods\aircraft\F-15C\Missions\EN\Campaigns instead of ..\DCS World\Mods\aircraft\Flaming Cliffs\Missions\EN\Campaigns\, that makes sense.
   
2. The single, Quick and Multiplayer mission sets have some different names, etc.
   

The Flaming Cliffs 3 layout is attached in PDFs:

 

At this stage I would recommend you play my version of F-15c campaign for a more trouble free experience, as for other single missions, just use the games ones.

 

I will see if ED are agreeable to updating the F-15c standalone campaign to the same as the Flaming cliffs 3 F-15c set in one of their up and coming patches.

 

Knowing the directory structure, means I can send the fix to them directly and they only have to install into their release stream.

 

Regards, Ian.

DCS World_Mods_aircraft_Flaming Cliffs_Missions_Multiplayer_.pdf

DCS World_Mods_aircraft_Flaming Cliffs_Missions_QuickStart_.pdf

DCS World_Mods_aircraft_Flaming Cliffs_Missions_Single_.pdf

DCS World_Mods_aircraft_Flaming Cliffs_Missions_EN_Campaigns_.pdf

Edited November 28, 2017 by MadDog-IC

[draconus]

Thanks, MadDog-IC and all, you've been very helpful :thumbup: Good news is I'm not missing any Eagle's mission file I should have, just some of them are older/bad versions.

[draconus]

MadDog-IC, you might want to revisit those campaign files again as I was flying the updated version mission #7 yesterday and the briefing with map does not add up. There were differences between map WPs and briefing WPs (these are correct) - even the BULLs WP differ. Then you have "2xAIM120C + 4xAIM120B" in mission details and down the briefing it says "6xAIM120C" in weapon payload section (which you do not get in the mission). I bet other missions are like that too.

[MadDog-IC]

MadDog-IC, you might want to revisit those campaign files again:

 

Maybe in the future, any faults you care to list will be compiled for modification, and consideration will given to pushing an update through.

 

Thanks for the feedback, keep them coming if you spot any other issues.

 

I received word that the F-15c Standalone module will be getting updated in some form to the same as the Flaming Cliff 3 F-15c module in a future DCSW 1.58x update, this would be the Bear Trap campaign and hopefully most of the single player missions.

 

I was flying the updated version mission #7 yesterday and the briefing with map does not add up.

 

There were differences between map WPs and briefing WPs (these are correct) - even the BULLs WP differ.

 

Yep, this is an originally unforseen consequence of mission updating, I have been aware of this issue in other missions recently, but due to the amount of time I spend on multiple missions and the shear number of things you have to look out for correction, I made a decision that I wouldn't be changing briefing pictures due to extra time involved. I do try to stay true to the original authors design, But there are some times I have to add or subtract waypoint, change routes and wind direction to get AI to do the missions.

 

I have corrected the waypoints, etc back to match the mission brief so I don't have to edit the picture. , changed payload and fuel cells to match brief also.

 

Then you have "2xAIM120C + 4xAIM120B" in mission details and down the briefing it says "6xAIM120C" in weapon payload section (which you do not get in the mission). I bet other missions are like that too.

 

Yet another consequence of payload change in an update patch to DCS v1.5x which corrected an incorrect pylon mounting and moved the pylons for the Aim-120c and after effect was F-15c not having any aim-120c in missions, when I re-instigated the correct pylon and payloads, it was easier to put AIM-120B instead, and didn't correct briefs, not a big issue.

 

There will always be issues, some created by me, some already in the mission to start with, either way some modules get checked over more thoroughly than others, Each mission I do may be re-flown 10-20 times or even more, whilst I look out for inaccuraces in briefing, Triggers, messaging and voice overs, Scoring logic, Radio calls, Artillery not firing, FARPS not workings or having no support vehicles for refueling, lighting an repairing, Flights having wrong skins, callsigns, payloads, speeds, the list just goes on.

 

Regards, Ian.

Edited December 2, 2017 by MadDog-IC

[JUICE-AWG]

+1

 

 

Here, here! Agreed!