FriedrichNix

No point in buying RAZBAM modules, if they are not maintained. They will probably stop working at some point. So it is actuall good, that they are not for sale any more. And because this came from RAZBAM, I guess even they/he doesn't believe in settlement any more.

You, Sir, are awesome! I know that you keep your campaigns - all of them - up to speed with the current DCS versions and that is impressive. The effort and the time you put into this. Thank you for your continuing support. I find this extraordinary!

Finally... 't was hard. But rewarding. Although I was swearing quite some times and got frustrated, I learned the jet much better than many others. Impressive campaign. Now the assignements come and I will be off to the Marianas... *Edit: Not first scores. I have to admit, some I needed to do quite some times and others I didn't understand quite well at the first try. But that's ok. For me it is. *Edit 2: After the last DCS patch and update to mission 8, I was able to AVERAGE Run 2 also. Great thing and very satisfying! Thanks again!

Hi there, on mission 9 (carrier day qualification) after landing you get the message: "No parking available, you will be automatically moved to parking. Awaiting wing fold". Then - after you fold your wings - you get put under deck. There you may request a relaunch from the menu. Then a message is displayed "Awaiting free terminal". On the carrier deck all elevators and parking slots are taken and no aircraft is about to start. Unfortunately you won't be put on the deck and you cannot continue with the continuing traps.

Like in my opther thread, I cannot get the g-breathing loud enough to hear anything. Also I do not have for some reason a g-effect (blackout)...

I replayed this mission now about 30+ times and I have the same experience. With the current DCS version (2.9.15.9599.1) the notching does not work as intended in the campaign. I break lock, I turn, I get immediately locked on again. I somehow managed to get an "unsatisfactory" when overstressing the airframe and shooting right to the ground to evade the missile and then manage to get the F16 finally shot down, but most of the time I get locked up and shot at.

Unfortunately the G Breathing Effect is not audible for me. I changed every audio option and I cannot make it out. It is very stressfull, not to have a feedback, when to overstress the airframe. I put on G-Effect to simulation, but I never get a blackout either. Kind of frustrating... although I know, it's got nothing to do with the campaign, but rather with DCS core.

I am also having a really hars time with the 2v2 2nd run and the 4v4 2nd run. While watching the above playthrough and lanky pilot's playthrough and seeing my own experience, I think missions vary sometimes greatly with the current DCS version and AI behavior. Nothing much Reflected (or any other mission builder) can do about that, but one should know that maybe a too strict plan on AI behavior and expected player behavior/reaction is greatly influenced by DCS and various changing parameters. Although I like the campaign and the idea about it very much, some parts are very frustrating.

Hi, I just started recently this great campaign. I wanted to get some 80s action. And what could be better, than to get out the good ol' F14. And let me tell you: It was a good choice. Not only "Speed and Angels" but also "Zone 5". At the moment I am in the middle of the Speed and Angels campaign after completing the Zone 5 campaign. Now, I often get in the feedback "you oversteered the jet". And I did, when looking at the g-meter just then. I fly VR and I am obviously most focused on the HUD and the leftish instruments (speed, verticometer, altitude). I lately included the AOA meter in my attention cycle, since this also can give you a hint when flying too tight and with too much g. Are there any tips? How do you not over g/oversteer? Is it just a lot of practice and learning how hard to pull or rather not pull your flightstick? Do you actually look in a dogfight on your g-meter on the bottom right?

Hey, I want to quick tell you also, that this is one of the best campaigns I played. I learned a bunch about the Warthog, although I could fly the beast berfore and it was really entertaining and educational. Keep doing campaigns and keep your plans up to someday get Part II done. I know there were some time/real-life issues, but this campaign is a jewel for all Warthog Pilots! Thanks for your time and effort!

I have seen the messages on screen like "Chico: Switching 2" (or something like that). Just no chatter. Checklist items were coming through (heard the chatter between Chico and 'You') and checklist was done properly. Later message was displayed on screen "Hold short Runway 3R, do not cross the line". I waited. I then saw that Chico switched channels and then the message disappeared. I figured, I may take off and did so (as done in the missions before). So I guess everything went fine "internally", only that the chatter between ground and tower was not heard for some strange reason. After takeoff I could hear the departure/approach messages again. No biggie, I can try and stream-record it. I also can wait for the next DCS update and see if the problem still exists for me and then stram-record, if you are interested. I am able to advance through the mission and my RAG (1v1 next up at the time of writing).

I encountered a few ... abnormalities (DCS World v.2.9.15.9599.1) In Mission 3: After start and takeoff until LOADING NEXT TASK, I got an error "Could not load Speed and Angels - 03b_Parade.miz". After restarting the mission in the campaign window, it worked. In Mission 4: On the next day, I got the same bug with the first LOADING NEXT TASK, DCS could not load Speed and Angels - 04b_Intercept.miz. After restarting in the mission selection from the campaign window, it worked. Mission 4: Sound files for taxiing to the runway at start didn't play. Mission intro worked, ATIS worked and when I finally just taxied, the checklist items worked. All communication with ground and tower until after wheels up didn't play Mission 4: Maybe not a bug: Grading for LATT was recieved, after switching tasks (RTB), from that time though, it wasn't possible to redo the LATT evaluation. To get to this quickly (after landing and finishing the mission), I loaded up "Speed and Angels - 04d_LATT.miz" in the mission editor to practice LATT some more. So far awesome campaign! It really keeps the pressure on and I feel constantly like I am evaluated as a pilot. I learn a lot and with retaking the evaluation, it gives a lot of practice. Still after Mission 4 (and the whole Zone 5 campaing) I feel already a better pilot for the F14. Thank you for the great experience!

Mine stops also at 4.5, which is the maximum height for the radar altimeter. It actually went off at about 5k. And yes, I also hat to do quite some "mouse wheeling" or when holding the left button and moving the mouse upwards, I needed more than 1 pass... After the first flight, you are on your own to set the height. At least on Day 2...

I missed my grading in Mission 1. Didn't see it. Is there any way to see what I got? Thanks btw. making me feel, line I was in flightschool again. Was long ago in Germany, but I felt the pressure directly. Again! Edit: I get it: You can do so bad, you don't even get the "unsatisfactory" grade... I now flew days 1 and 2 and did all right...

One of the best campaigns I have played so far. Not only very well thought through, but I also like how you tried to make it as realistic as it goes with the means at hand. A very great job. As a non airforce pilot and never be able to be sitting in a jet, but a "child of TopGun", this was one of my finest experiences. I do not have really an idea, what you can do better. Just keep doing, what you do! For the former question about "flying each mission with an air start", I came to the conclusion, that this is actually NOT necessary. You could consider one thing, though, if you wish: You could put into the 2 v unk and 4 v unk missions a bit more randomness, conserning SAMs and the wildcard. Say for example, a 40% chance on mission start to have a SAM-site up and a 60% chance to have a wildcard in the game. and even maybe a 10% chance to fly against Floggers. That would be everything you had in the campaign and no need for an air start of every single mission, which I understand is not your intend and goal in the campaign. Nevertheless - awesome job to you, Sir, and Bio! Next up for me will be "Speed and Angels" and since you made some missions for the Phantom, I consider buying these along with the jet! A fan

I have seen that, thank you. But again, I really enjoy the campaign and I am looking forward to "Speed and Angels" afterwards!

That's what I really like about that campaign. You basically cannot "fail" a mission if you start and land. Very much, like ... in TopGun ... I guess. At least in the movie they also were shot down and only some managed to do a kill or two. So I really like that. What I'd really would love to see is an air start practice for every encounter (like the practice missions), so that you could quickly hop in, try something, hop out and in again. Practice the encounters quick - like in a simulator.

Just encountered the VDI-camera problem in VR on the Zone 5 Campaign - Mission 4: 2 vs Unk

For everyone who also struggles with this: My solution is, I use the third party software Joy2Key and have different profiles for different aircraft. In DCS I bind keys to the two VR zoom options. In Joy2Key I then bind these keys to the buttons I want to use for the VR Zoom. Last step is deleting the button-bindings in the aircraft section in DCS, so that these buttons (on the HOTAS) have no function in DCS. It works quite well, although means running another program in the background. It also needs to be preselected when chosing your desired aircraft, but since I change HOTAS for that, I usually pick the desired aircraft for the gaming session anyways.

Unfortunately ... not. Example: In the F18, I use Thrustmaster's F18 Stick on a Virpil base. In the A10C, I use Thrustmaster's A10 Stick on that Virpil base. When I now assign a button on the A10 Stick to VR Spyglass (for example), it may interfere with the controls in the F18, once I change out the sticks. So it would be much easier to have this option per aircraft, because only then you can truly have a non conflicted solution. There are solutions with 3rd party software, but it would be much easier to have this option in DCS.

It's 2025 and this still is an issue, for me at least. I use different HOTAS, but same bases. Orion 2 for example with F15EX handles and Navyace handles. And I use a stick base with F16 stick and F18 stick. So I have to use different keys for VR Spyglass and VR Zoom. @BIGNEWY can you please pass this along, again?

I know, this is an old thread. I love the A10C and I used the Thrustmaster Warthog because it is a replica. BUT it is so scrappy inside, that in my lifetime now over about 15 years the 4th throttle/stick broke due to inferior internal wiring. I cannot fix stuff myself and need to rebuy. I am not buying the 5th any more. I went with the Winwing F15EX and even if I need to swap Boatswitch and Chinahat it would very much be worth it, for the better hardware quality. So, I congratulate you on choosing the Winwing hardware and hope you found a good solution for yourself. I just wanted to give you a heads up, that in my opinion you made the right choice.

They probably won't touch the older campaigns. First of all, they still can sell these for the people who are not buying the FF Eagle and then, they even didn't update the RedFlag 16-2 Campaign for the A10C(II) form the A10C. So it will either be a totally new campaign or none at all. Probably not so much work to get it updated to the FF Eagle. Waypoints could still be just the same and radio is usually not a problem in these campaigns. Just make a kneeboard sheet wit the different radio channels, like done in the other FF RedFlag campaigns.

This issue is resolved. I am terribly sorry and it is kind of embarrissing for me. I missread the "Cargo Hook ARM Switch" and the "Cargo Hook Arming Switch" and used the wrong input. Everything works just fine. Totally sorry here...

I will have to investigate further...