RogerRoadie

@BIGNEWY Hi, no I am not using any unusual graphic tweaks or edits. Log is attached. Just FYI I am using the Steam Version! When I start DCS it gives me the options: 1. Play DCS Steam Edition 2. Launch SteamVR in Steam VR mode 3. Launch OculusVR in Oculus VR mode 4. Play MT Preview I have always used option 1 as I don't have VR. Just for trouble shooting I have tried option 4. Play MT Preview. When I use this option I can see the wands and everything looks normal, but the game sometimes crashes. When I use option 1 as I always have in the past, the game runs without problems but I can't see the wands!? The attached log file is from option 1 "Play DCS Steam Edition" Thank you for your help!! Rudy dcs.log

Hi Flappie, checked my mods, I have no mods installed other than TacView and DCS-SRS Radio. Before the update to 2.9 the Supercarrier deck crew worked flawlessly. Attached my track from taxi to the catapult to cat-shot.... Any help is appreciated, Thank you!! Cheers Rudy Deck Crew No Wand Track.trk

Since my update to DCS 2.9.0.46801 the Supercarrier deck crew has no light wands during night operations anymore! See attached screen shot. The light "shadow" ie. green and red or yellow light sheen on the deck crew body is visible, but the actual light wand is missing. This makes it extremely difficult to see the deck crew hand signals at night. Any ideas??

Same here, after the latest update, I have bright green wire frames around some of the AI aircraft!!?? Attached screenshot is a IL-76 at night, sorry not very good visual....

@baltic_dragon First of all thank you again for an awesome campaign, I really enjoy the story line and the way you converted the book into a DCS campaign. Just as information I experienced a bug flying mission 11 (Back to Bandar Abbas) yesterday. (Spoiler alert: the bug description kind of gives away what happens, so if you don't want to know, don't read any further :-)) I flew the mission 5 times and each time the sim behaved the same! After dealing with the inbound aircraft and heading back to WP3 I received the new tasking. After entering the coordinates and looking at the FLIR the coordinates are off (on purpose I know!) When slewing the targeting pod to the correct target and firing, the JSOW strikes the target, but the target remains intact and "no joy" is called. When firing the second JSOW to the exact same point again, this time the target is destroyed and tasking for the 2nd target commences. The 2nd tasking has to be adjusted as well (on purpose I guess) but this time target is killed on first attempt. 3rd tasking coordinates are exact and no problem. However on all 5 occasions that I flew the mission, the wingman disappears after engaging the enemy aircraft and flies back towards the carrier/tanker. When assigning a target Raven 3-4 always acknowledges "coordinates loaded" and acknowledges that he will engage (when selecting the F10 option), but never does. The wingman continues to fly around on HDG 160ish for a long time and descends then comes back up north, but does not engage on the assigned targets. With only 2 JSOWS and 3 targets as well as the first hit always not destroying the HAWK, it is impossible to finish. I therefore loaded 4 JSOWS on my last attempt and managed to complete the mission. Same thing happened, wingman disappeared south after engaging the enemy aircraft and getting back to WP3. First JSOW missed (even after using the corrected coordinates) 2nd JSOW hit, 3rd JSOW on target 2 (refined coordinates) hit, 4th JSOW on target 3 hit. In this configuration you are going to be low on fuel during recovery, since you have to take two drop tanks off when loading the extra JSOWs, but can use a center drop tank. Just FYI radio comms on the RTB seem to work normal with option for the tanker, kissing off your wingman (even so he is not there) and case III recovery. (I did not use the tanker, so can't comment if this works or not) All in all a great mission with a few bugs (at least for me), but can be solved with a work-around (ie. loading extra JSOWs). Not a complaint!! Just giving you some feedback to help improve and make troubleshooting a bit easier for you. If you need any more details, I am happy to fly it again and make some notes! Thanks for your effort and continued support with all the updates DCS throws at us :-).

@Sylosis you are absolutely correct the JDAMs don't use degrees and decimal minutes. Target data entry has to be done in D-M-S and decimal seconds. Having said that I also had trouble hitting the house and when slewing the TGP, I found that the coordinates that are given by Bowser are actually degrees and decimal minutes and not as the formatting in the text and voice message suggests D-M-S, so therefore the target coordinates are N30°30.04' E47°48.04' this format works for creating a waypoint, but for correct target entry in the JDAM that has to be converted into DMS and therefore the correct entry would be N30°30'02.40" E47°48'02.40" the elevation is 3 meters but is not required. This has at least for me sorted out the problem. For anyone that still has problems you can as already has been suggested create a target waypoint with the coordinates as given and WPDSG, then you have the targeting pod looking at the correct target and drop in TOO mode, however if you want to drop in PP (pre-planned) mode you have to convert as given above. In fact if you create a target waypoint N30°30.04' and E47°48.04' and load it across into the JDAM TOO target coordinates will be automatically converted. @baltic_dragon that's why it worked for you when you dropped in TOO mode. Thanks for a really awesome campaign and so far despite all the updates and changes I have had no problems with the missions. Keep up the good work, really appreciate this. For anyone that is interested, the book Raven One is very good IMHO and the sequels "Declared Hostile" and "Fight, Fight" are also excellent and maybe even better, this could be made into a sequel campaign......

Ok 3rd attempt didn't work either. After complete restart of the computer the result is the same! Mission is complete and then the black screen with "x Can not open debriefing file" appears. See attached screenshot. But thanks for a great campaign so far!!

I have the same problem, flown the mission twice now to its conclusion. After 'Mission Complete' back on the carrier I tried to exit and it brings up an error message x Debriefing File cannot be loaded. Then DCS freezes and the screen remains black. I have to quit with Task Manager. Giving it one more go after a complete PC restart.......