wiwa23

Oh lord. We are talking about an update of a module before it is fully released/out of early acces. Not blaming the request btw but seeing the irony of the way things are nowadays.

It definitely is more sensitive, probably way more realistic. But I've read many reports by many about damaging the gear and a lot of them talk about being on speed, descent rate and stuff but a lot of them don't mention the weight (below 34000 for carrier trap, Below 39000 for flared field landing). In my experience it works pretty well this way. Should do more testing but it feels that it is ok like this. Maybe a bit to sensitive? Maybe crosswinds make it more prone for breaking?

For some time the AB is not working always when launching from the carrier. After testing both online and in SP I can confirm this: 1. AB works when you go AB BEFORE pressing the salute key. 2. AB doesn't work when going AB AFTER pressing salute key. included track files can confirm this. It's not a binding issue ( I can confirm in the track as AB works when leaving the deck). AB doens't work AFTER pressing salute.trk AB works BEFORE pressing salute.trk

Holy smokes, just found the topic you probably meant. So many people having issues with this (also with my buddies of my virtual squadron). Taking into account the fact that it involes so much hardware variables I could not believe what I read in that topic! Why you would not make it adjustable/optionable just for the sake of your costumers is beyound me... I mean ED has that special option for slewing Mavericks as well (depress or not while slewing). That in itself is a perfect example of how to provide the best option for your costomer with respect for realism and practicality. But with this topic many are screaming against a wall that just isn't listening. Very weird, sad and frustrating to read. And just like that it was decided to close the topic... I am baffled.

Hello, As of now the cursor of the SA page and Radar are not matching eachother regarding sensitivity. I Like the way the SA page cursor works but find the radar cursor way to sensitive and very hard to make precise adjustments. If I adjust the Radar cursor (axis tuning) then I find the SA page cursor is way to slow. This inbalance seems not right and is very frustrating to work with. For example the F16 cursor is more on the same level across the different sensors and works just fine. This seems more the way it should be working. What happened, it used to be good in the past? Is there a way to make it balanced again? Are there any plans to fix this? Please allow me to use the word "fix" as I have the strong impression it just should not be like this. Regards!

Holy smokes yes!! Update and Extension would be so cool!

Without this becoming a nasty rage of anger and frustration I totally understand the urge for the original author to poste this and support the message. I really hope for improvement as well! Like the previous poste 'The lack of addition of new features is one thing, but the bugs that take away the fun in using the SC is another.'

Yes this is a good tip. Remember that the speed brakes are extended when doing a cold start. It is easily forgotten to retract them... And you could be extending them by accident as well of course... With this loadout passing mach 1 (and reaching Mach 1.4)should be no problem in level flight at FL250.

Thanks for your reply. I regret these immersion breaking solutions but toally understand why you did it. More due to one of these DCS limitations. It's a shame though, all those incredible cool end complex modules, every year... but missions are still breaking due to core engine issues like AI wingmen not reliable to do stuff like AAR. Anyway, thanks again and I know for sure I'll have fun with your amazing work!

Hello ChillNG, Thanks for your work! It's obvious you went all the way with this and it is very much appreciated. I bought it a few days ago and I'm looking forward to it! Just scanning through the very well made docs. Reading through the welcome doc I have a question regarding the following statement: "... all missions are completable without AAR. Some missions later in the campaign take place in two parts, with part one ending at the tanker and part two resuming after AAR takes place. This means the player (and more importantly the AI) will not have to refuel as well as providing a checkpoint before the action begins. However, should you wish to refuel manually, you're still able to contact the tanker through the default comms menu and do so." Question: If we as a player choose to do AAR can we proceed with the mission without restarting p2? Thanks! Wiwa

EDIT! PROBLEM SOLVED! (Man... so frustrating... I More than triple checked the instructions and the location of the folders but somehow it just doesn’t work. What else could it be?) Hehe...stupid thing that caused this... my notepad window of the readme cut of a piece. Therefore I missed the part 'mods' in the "C:\Users\YOURNAME\Saved Games\DCS.openbeta (Or just DCS World if on stable)\Mods" description. So I have put the tech folder in the wrong location... ok... a bit embaressed here ... But very glad I solved it because the mig 21 surely feels complete with this mod! This way it complements the overall excellent module! It really should be implemented as standard... the default sounds really don't do it justice... Anyway thanks again!

Thanks for your reply. I will check again but I'm quite certain I put them in the right place...or am I going crazy? So strange...

Hello, Thanks for your work! Sadly, somehow I just can't get it to work. All sound are still the horrible immersion breaking default ones. I really think I placed the folders in the right directories. Does it might have something to do with the fact I didn't install DC on my c drive? Therefore the path C:\Program Files\Eagle Dynamics\DCS World OpenBeta is different in my case. For the root folder in my case it is...G:/DCS World OpenBeta. Thanks in advance.

Yes thanks! I already had read it but need to truly investigate further so I understand what numbers to put where...

Oh yes, you told me before. Here is the full log! dcs.log