-Rudel-

Dear All, In order to better accommodate both current and future project update needs, we'd like to urge all users to cease reporting bugs on the Bugs subforum (unless significant discussion is indicated) and instead help us out by registering a new account and reporting a bug on the bug tracker. This will allow us to more effectively receive bug reports from users, convey what is received and already fixed, as well as offer an insight into our post release support process. We also hope that the added transparency will better indicate how many changes are made that previously were not noted in changelogs. Bugtracker: https://leatherneck-sim.mantishub.com/ HOW TO REPORT A BUG Write an accurate and detailed report. Do not be vague, or leave simple things out. The more information that is presented, the better, as we can recreate the problem exactly as the user experienced it. Include all the steps taken to produce the bug(s). Attach Missions, TacViews tracks, and/or SARPP, dcs.log data files, and screenshots. Show real world data compared to the modules' data. Preferably in English or Serbian. Keep all the information presented in a neat, orderly easy-to-follow format. This will help us immensely in reproducing the issue and confirming it. You can also add further comments or updates on an issue after reporting it. Once a report is submitted, we will take a look at it ASAP. Please note that this bug tracker is separate from our internal one, thus issue statuses will not be accurate unless set to resolved or closed. If a bug that is reported is not seen, please add it. It's likely we are already tracking it, but better safe than sorry! Most of all; we'd like to thank all of you for taking the time to report bugs and help us build better products. Many Thanks, Leatherneck Simulations

Dear All, In order to better accommodate both current and future project update needs, we'd like to urge all users to cease reporting bugs on the Bugs subforum (unless significant discussion is indicated) and instead help us out by registering a new account and reporting a bug on the bug tracker. This will allow us to more effectively receive bug reports from users, convey what is received and already fixed, as well as offer an insight into our post release support process. We also hope that the added transparency will better indicate how many changes are made that previously were not noted in changelogs. Bugtracker: https://leatherneck-sim.mantishub.com/ HOW TO REPORT A BUG Write an accurate and detailed report. Do not be vague, or leave simple things out. The more information that is presented, the better, as we can recreate the problem exactly as the user experienced it. Include all the steps taken to produce the bug(s). Attach Missions, TacViews tracks, and/or SARPP, dcs.log data files, and screenshots. Show real world data compared to the modules' data. Preferably in English or Serbian. Keep all the information presented in a neat, orderly easy-to-follow format. This will help us immensely in reproducing the issue and confirming it. You can also add further comments or updates on an issue after reporting it. Once a report is submitted, we will take a look at it ASAP. Please note that this bug tracker is separate from our internal one, thus issue statuses will not be accurate unless set to resolved or closed. If a bug that is reported is not seen, please add it. It's likely we are already tracking it, but better safe than sorry! Most of all; we'd like to thank all of you for taking the time to report bugs and help us build better products. Many Thanks, Leatherneck Simulations

Dear All, In order to better accommodate both current and future project update needs, we'd like to urge all users to cease reporting bugs on the Bugs subforum (unless significant discussion is indicated) and instead help us out by registering a new account and reporting a bug on the bug tracker. This will allow us to more effectively receive bug reports from users, convey what is received and already fixed, as well as offer an insight into our post release support process. We also hope that the added transparency will better indicate how many changes are made that previously were not noted in changelogs. Bugtracker: https://leatherneck-sim.mantishub.com/ HOW TO REPORT A BUG Write an accurate and detailed report. Do not be vague, or leave simple things out. The more information that is presented, the better, as we can recreate the problem exactly as the user experienced it. Include all the steps taken to produce the bug(s). Attach Missions, TacViews tracks, and/or SARPP, dcs.log data files, and screenshots. Show real world data compared to the modules' data. Preferably in English or Serbian. Keep all the information presented in a neat, orderly easy-to-follow format. This will help us immensely in reproducing the issue and confirming it. You can also add further comments or updates on an issue after reporting it. Once a report is submitted, we will take a look at it ASAP. Please note that this bug tracker is separate from our internal one, thus issue statuses will not be accurate unless set to resolved or closed. If a bug that is reported is not seen, please add it. It's likely we are already tracking it, but better safe than sorry! Most of all; we'd like to thank all of you for taking the time to report bugs and help us build better products. Many Thanks, Leatherneck Simulations

Dear All, In order to better accommodate both current and future project update needs, we'd like to urge all users to cease reporting bugs on the Bugs subforum (unless significant discussion is indicated) and instead help us out by registering a new account and reporting a bug on the bug tracker. This will allow us to more effectively receive bug reports from users, convey what is received and already fixed, as well as offer an insight into our post release support process. We also hope that the added transparency will better indicate how many changes are made that previously were not noted in changelogs. Bugtracker: https://leatherneck-sim.mantishub.com/ HOW TO REPORT A BUG Write an accurate and detailed report. Do not be vague, or leave simple things out. The more information that is presented, the better, as we can recreate the problem exactly as the user experienced it. Include all the steps taken to produce the bug(s). Attach Missions, TacViews tracks, and/or SARPP, dcs.log data files, and screenshots. Show real world data compared to the modules' data. Preferably in English or Serbian. Keep all the information presented in a neat, orderly easy-to-follow format. This will help us immensely in reproducing the issue and confirming it. You can also add further comments or updates on an issue after reporting it. Once a report is submitted, we will take a look at it ASAP. Please note that this bug tracker is separate from our internal one, thus issue statuses will not be accurate unless set to resolved or closed. If a bug that is reported is not seen, please add it. It's likely we are already tracking it, but better safe than sorry! Most of all; we'd like to thank all of you for taking the time to report bugs and help us build better products. Many Thanks, Leatherneck Simulations

Dear All, In order to better accommodate both current and future project update needs, we'd like to urge all users to cease reporting bugs on the Bugs subforum (unless significant discussion is indicated) and instead help us out by registering a new account and reporting a bug on the bug tracker. This will allow us to more effectively receive bug reports from users, convey what is received and already fixed, as well as offer an insight into our post release support process. We also hope that the added transparency will better indicate how many changes are made that previously were not noted in changelogs. Bugtracker: https://leatherneck-sim.mantishub.com/ HOW TO REPORT A BUG Write an accurate and detailed report. Do not be vague, or leave simple things out. The more information that is presented, the better, as we can recreate the problem exactly as the user experienced it. Include all the steps taken to produce the bug(s). Attach Missions, TacViews tracks, and/or SARPP, dcs.log data files, and screenshots. Show real world data compared to the modules' data. Preferably in English or Serbian. Keep all the information presented in a neat, orderly easy-to-follow format. This will help us immensely in reproducing the issue and confirming it. You can also add further comments or updates on an issue after reporting it. Once a report is submitted, we will take a look at it ASAP. Please note that this bug tracker is separate from our internal one, thus issue statuses will not be accurate unless set to resolved or closed. If a bug that is reported is not seen, please add it. It's likely we are already tracking it, but better safe than sorry! Most of all; we'd like to thank all of you for taking the time to report bugs and help us build better products. Many Thanks, Leatherneck Simulations

Dear All, In order to better accommodate both current and future project update needs, we'd like to urge all users to cease reporting bugs on the Bugs subforum (unless significant discussion is indicated) and instead help us out by registering a new account and reporting a bug on the bug tracker. This will allow us to more effectively receive bug reports from users, convey what is received and already fixed, as well as offer an insight into our post release support process. We also hope that the added transparency will better indicate how many changes are made that previously were not noted in changelogs. Bugtracker: https://leatherneck-sim.mantishub.com/ HOW TO REPORT A BUG Write an accurate and detailed report. Do not be vague, or leave simple things out. The more information that is presented, the better, as we can recreate the problem exactly as the user experienced it. Include all the steps taken to produce the bug(s). Attach Missions, TacViews tracks, and/or SARPP, dcs.log data files, and screenshots. Show real world data compared to the modules' data. Preferably in English or Serbian. Keep all the information presented in a neat, orderly easy-to-follow format. This will help us immensely in reproducing the issue and confirming it. You can also add further comments or updates on an issue after reporting it. Once a report is submitted, we will take a look at it ASAP. Please note that this bug tracker is separate from our internal one, thus issue statuses will not be accurate unless set to resolved or closed. If a bug that is reported is not seen, please add it. It's likely we are already tracking it, but better safe than sorry! Most of all; we'd like to thank all of you for taking the time to report bugs and help us build better products. Many Thanks, Leatherneck Simulations

Dear All, In order to better accommodate both current and future project update needs, we'd like to urge all users to cease reporting bugs on the Bugs subforum (unless significant discussion is indicated) and instead help us out by registering a new account and reporting a bug on the bug tracker. This will allow us to more effectively receive bug reports from users, convey what is received and already fixed, as well as offer an insight into our post release support process. We also hope that the added transparency will better indicate how many changes are made that previously were not noted in changelogs. Bugtracker: https://leatherneck-sim.mantishub.com/ HOW TO REPORT A BUG Write an accurate and detailed report. Do not be vague, or leave simple things out. The more information that is presented, the better, as we can recreate the problem exactly as the user experienced it. Include all the steps taken to produce the bug(s). Attach Missions, TacViews tracks, and/or SARPP, dcs.log data files, and screenshots. Show real world data compared to the modules' data. Preferably in English or Serbian. Keep all the information presented in a neat, orderly easy-to-follow format. This will help us immensely in reproducing the issue and confirming it. You can also add further comments or updates on an issue after reporting it. Once a report is submitted, we will take a look at it ASAP. Please note that this bug tracker is separate from our internal one, thus issue statuses will not be accurate unless set to resolved or closed. If a bug that is reported is not seen, please add it. It's likely we are already tracking it, but better safe than sorry! Most of all; we'd like to thank all of you for taking the time to report bugs and help us build better products. Many Thanks, Leatherneck Simulations

Dear aviators, We are slowly approaching the middle of October, summer is long gone, and ahead of us we can already see a glimpse of winter. But before that comes, we would like to give you a brief update on our development situation. The programmers' focus and attention is full steam directly aimed at the MiG-21Bis development for Modern Air Combat. Progress should not take longer than a month and they are already at 40% completion. While the programmers are thicc in 1s and 0s, the Christen Eagle 2 is facing an advanced testing phase based on a team of internal testers. We've managed to gather several SME's that have various degrees of experience on this bird, including a few aerobatic instructors. Though the Flight Model has a few minor quirks to address, overall expression is that this module is on par with the real aircraft. Basic and advanced aerobatics seem equitably accurate. We have begun the development of a fabulous new promotional video we hope you all like, while also trying to make up our mind which of the two samples of Lycoming O-360 engine sound we find most accurate and which will be delivered to you with the rest of module. Finally, we are working with Eagle Dynamics to integrate the 3D version of the NS430 GPS navigation system for a more immersive flight experience. And addressing the elephant in the forum, we have a few updates on MiG-21Bis situation. Over the past few years everyone has experience some sort of activation trouble. Eagle Dynamics is currently looking into having our module's DRM get in line with their new "log-in" standard. If successful, users will not have to worry about entering a key ever again. The pilot model that we've shown you some time ago was not shown in the game graphics engine. Below, you will find new screenshots as it will appear in game. The external pilot textures are nearly complete, while animations are ready for presentation. The pilot will be available as soon as the new cockpit update is finished. And yes, there will be an option to view it in cockpit mode. The cockpit will soon be underway for a complete makeover. Your pleas were read, and we're planning...we repeat plan on providing a multitude of cockpit livery options. This includes colors, language, measuring system, and varying degrees of weathering. Though there is no guarantee on the quantity yet. Small fixes are being implemented in patches as well. Other improvements include proper instrument panel lighting, where the light-ray sources will come directly from the light posts. The 3D mesh itself will be totally remodeled to ensure proper alignment to the external model so that users of VR headsets will have a better experience. It has also been decided that the two external 8K textures will once again be split back into separate 4K sets to help mitigate stuttering for low end computer systems, after several users have been reporting performance issues. While the programmers are making headway for MAC, a few bugs are being looked into such as the R-13M, R-3R, and R-3S missiles' performance degradation. We're currently using TacView and comparing our sources to help improve them. Our researcher is currently collecting data on the SPO-10 to further improve it. Improvement work is scheduled to begin later this year, as top priority right now is MiG-21bis for MAC. The programmer for the flight model has stressed it will remain as is. As stated before in previous posts, actual real-time flight data recordings from a Serbian MiG-21Bis (75B) were presented to Eagle Dynamics as requested. There were no objections towards the data presented and all discrepancies in existing documents were explained. Fret not, other bugs will continue to be fixed though. And thus, the programmers have kindly asked, that if changes are seriously needed, and when submitting a bug report, whether it is FM related or systems modeling, to do the following: https://leatherneck-sim.mantishub.io Write an accurate and detailed report. Do not be vague, or leave simple things out. The more information that is presented, the better, as we can recreate the problem exactly as the user experienced it. Include all the steps taken to produce the bug(s). Attach Missions, TacViews tracks, and/or SARPP, dcs.log data files, and screenshots. Show real world data compared to the modules' data. Preferably in English or Serbian. Keep all the information presented in a neat, orderly easy-to-follow format. Last but not least, is a note on F4U-1D Corsair development. We can proudly report that PBR conversion of it's textures is underway.

Everything

Be patient for our update, we'll explain a few things more in detail.

Sound randomization via code, no bug

First it goes up, and when rudder is applied at near stall, she'll hammer head over. )

We left the liveries unassigned to specific countries to allow users to choose a livery that they like without being restricted.

2.5.3.22652 - 2018 Oct 10 Fixed ASO device initialization. Fixed pneumatic pressure gauge from constantly reading zero. Fixed SARPP from not recording all flight information. Reversed DA-200 bank indicator animation Reversed NPP localizer bar animation Reversed UVW for air pressure gauge warning colors

I'll do an art update just for you.

Try changing the 13s to 2s and see if that works. As long as the model has a default material attribute, it should work. Channel 13 is specifically for RoughMet textures, but channel 2 is for specular maps. And can read RoughMet textures there too.

There will be an update on our development in October...

Yorktown is planned... :pilotfly:

2.5.3.22176 - 2018 Sept 26 Fixed PRMG localizer needles' animations. Corrected canopy glass normal map texture: - Huge sun glare removed.

I still have an island mesh that needs to be exported in the new terrain engine. :pilotfly:

Uninstall the plugin. go into the plugins folder and ensure all related files are deleted too. Back date to: edm-plugins-137679.exe, and try again. Also, have you installed the service packs?

Dolphin created the 21Bis FM as best as possible based on charts and his own experiences. He combined the two resulting in mixed feelings from users. The FM went through so many changes because (although a simulation), he wanted to keep a fun factor in it. The 21Bis is not an easy aircraft to fly at all, despite its simplicity in the cockpit. And he took that into consideration, so he adjusted the FM. Yet, user still complained, so he adjusted it more to user likings; and thus other users complained because it may not be to their liking. So he adjusts it again, and the same continues guys. Then there are the users explaining their results based on manuals, hear-say, videos, etc. Or even their own experiences as maintenance crew. Although great research is being presented, it does not always beat a pilot's experiences. And that's what Novak wanted users to feel. How a pilot does. Not only is he a pilot, but he trained others, and I'm pretty sure he put the student through their paces. Now...ED asked for flight Data. So he flew the real aircraft and recorded actual data (cross checked with DCS 21Bis), providing it to ED and proving that FM is at it's best. ED cares greatly about the FM of any aircraft in DCS. In the past 6 years, we haven't heard anything from ED regarding any FM errors.

It is calibrated to work with the current grid.

ED bug, nothing we can do at the moment. I submitted a ticket nearly 2 1/2 years ago

3 years