NineLine

Hi, I have this reported, its a little better using the Extreme setting but for sure needs to be tweaked, thanks!

Hi, you can see what we are modeling here:


"It is also important to remember that all features of our Viper are in regard to a United States F-16CM Block 50, roughly M4.2+, operated in the 2007-time frame."

What does roughly mean? It means we can not always find the exact info we need so we might use something a little older, or maybe we cant add it at all based on classifications. However, the above statement is where we try to focus on the DCS: F-16. Thanks. 
 

Reported, thanks!

They are still there, although very subtle. We are working on standardizing these effects and then looking at the possibilities of user options for strength. Thanks. 

It depends on the surface, areas around runways and such do not throw up dust, this is a known issue with terrains. Other locations should show it just fine.
Thanks

I'm sorry I do not have any new info on this currently. Soon as we do we will share. Sorry. 

The last one was a little light, but I don't think it is fair to judge based on 1 patch, previous too that there were quite a few, and because of the new patch timeline it can take a little longer to get things out to everyone based on internal testing. 
August 14 (interim patch)
Fixed: RWS target symbols no longer show altitude when cursor is hovering over it 
August 9th (major patch)
Fixed: Crash during rearming in some cases.
Fixed: Freeze/CTD when selecting STN field in TNDL page, from dynamic spawn only
Fixed: FCR is detecting targets ignoring scan volume.
Fixed: HYD OIL PRESS and TO/LDG CONFIG lamp housing.
Fixed: Typo on throttle RNC - RNG.
July 22 (interim patch)
Fixed: Crash during rearming F-16C in some cases. 
July 11 (major patch)
Radar: Introduced false targets. They are caused mainly by internal receiver noise and ambient noises at receiver input. The radar internal circuits maintain false target rate constant with an average frequency of one false alarm per minute. 
Fixed: Сrash when switching weapons when using unlimited weapons.
Fixed: Crash when receiving SEAD Target into steerpoint 127.
Fixed: Crash using GBU-24.
Fixed: ACM modes stop working if you lose lock.
Fixed: Laggy HUD TD box.
Fixed: Level 5 gun piper.
Fixed: ACM lock lagging/lost.
Fixed: Bomb mode selection not updating dynamically.
Fixed: Unable to bug MSI tracks that are correlated to radar memory tracks.
Fixed: Non-selected AGM-65 seekers that are not in TRACK mode are not resetting to SLAVE or BORE modes.
Fixed: Search target hot lines don't work.
Fixed: AGM-65 can become non-space stabilised after launching.
Fixed: Elevation bar scan values are wrong in certain circumstances.
Fixed: Texture artefacts and geometry errors.
Fixed: Maverick seeker LOS slave to FPM at TMS Down Ignores SPI.
Fixed: TGP cannot change level setting in MGC mode.
Fixed: FCR "NONE" hides everything, including your own FCR tracks.
Fixed: FLCS TO/LDG Gains affected by weight-on-wheels.
Fixed: In external view, pilot helmet clips canopy when looking back.
Fixed: Inconsistencies with the JDAM AD CNTL settings.
Fixed: CBU-87/97 inconsistencies with CCIP/CCRP calculations.
Fixed: Impact Distance setup in SMS ripple is halved on impact.
Fixed: Need to reverse left arm patch orientation.
Fixed: TNDL Power resetting to HIGH in ME.
Fixed: HARM in POS missing leading zeros on bearing in HUD.
Fixed: AGM-65 in EO-VIS mode removes range scale after first launch.
Fixed: Switching AG Weapon on SMS page keeps delivery mode of previous selected AG weapon.
Fixed:  Able to move A-G radar cursor without SOI.
Fixed: Rename option on HSD CNTL page 2 to "A SMDL".
Note: Although not ready for this update, the Sniper Advanced Targeting Pods is in advanced development and planned for release later this year.
June 5th (F-4 interim patch))
Fixed: Сrash when switching weapons when using unlimited weapons
Fixed:  Reverse left arm patch orientation 
Fixed:  Bomb mode selection not updating dynamically
May 22 (F-4 Release)
 
Added new model pilot - work in progress.
Added  improved movements of the pilot head and torso - work in progress.
Added Maverick and HMCS Auto-Boresight, automatic for hot starts. Cold starts require manual boresight.
Fixed: Increased G-warmup effect time.
Added Bomb Fuze Options and Settings  from ME  - work in progress - missions where laser code is set to anything but default (1688) will need the code edited in Mission Editor using the new method. 
Fixed: Tuning the IFA alignment and further FIXes.
Fixed: Missing scale on the standby attitude indicator.
Fixed: GPS time starts at 00:00 when entering a mission.
Fixed: FCR Air to Air Header fix.
Fixed: Wheel friction imbalance.
Fixed: FCR target Min/Max altitudes inverted in negative antenna elevation.
Fixed: Handoff from TGP to TV-guided AGM-65's is partially functional using TMS Right.
Fixed: RWR displays radars in "Track" mode in the inner "Missile Launch" ring.
Fixed: CCRP lateral drop limit too small.
Fixed: Scan volume twitching around when bugged target near or beyond gimbal limit.
Fixed: RWR SYS Test no longer functions.
Fixed: True heading on ICP stuck at 00.
Fixed: Boresighting Mavericks is aligning with point mid air.
Fixed:  HSD zoom glitch.
Fixed:  Spotlight scan volume and EXP reference box snap from centre of display instead of appearing directly at cursor location.
Fixed: Entering OVRD while in spotlight search can cause radar to stop working.
Fixed: TGP does not take INS drift into account well (coordinates and height of the point changes).
Fixed: Rolls left under positive G.
Fixed: Search target hotlines don't work.
Fixed: RWS SAM cannot change radar range scale is designated inside an auto-range zone.
Fixed: Maverick seeker LOS Slave to FPM at TMS Down ignores SPI.
Fixed; Right MFD rocker switch labels incorrectly refer to Left MFD.
Fixed: JDAM with nose plugs fitted show 0 second AD in SMS by default.
Fixed: Exhaust "turkey feathers" graphical clipping/misaligned.
NOTE: The Sniper Advanced Targeting Pod is in active development for release later this year.

This appears to be fixed internally, I will leave this open and you can report back if you still see an issue in future patches. Thanks.

AI gunners are not working at the moment, sorry. 

I have reported this, thanks!

Yes, it works.
If you are in the pilot position you need to make sure on the Pilot Light Panel it is set to On, so the controls on the thrust handle will work. Make sure it says Pilot Control, there is one for Co-pilot control as well. 

Then on the Thrust handle you can map Searchlight On/Off and the position. 

I think it's probably a link to a dev build so I will pass it along but I am sure they will get sorted. I don't think they are impacting your FPS as those folders won't exist for anyone. 

These are not modelled yet and will come later in EA, thanks. 

So the issue is you did not have Dynamic Cargo selected for the Helipad, only the main airfield, hence the reason it worked on the runway but not the helo parking.
We do have a report about overlapping zones, but right now both need to be turned on. Thanks!

First off, there is nothing new to report as of the date of this post, this new thread is simply a clean-up and ease of access for all current official information on the current issues between Eagle Dynamics & RAZBAM. Hopefully, this will make it easier to see the current known information and weed it out from the theories, guesses and suggestions in the other thread. If you want to see that one, the link will be available at the bottom of the post.
The first public knowledge of the disagreement happened with an announcement on the RAZBAM Discord here:
https://discord.com/channels/536389125276827660/544501300134543380/1225494495458627634
razbam_prowler — 04/04/2024 10:17 AM
Dear Customers and Community,
You may have noticed that the that the latest RAZBAM announcements does not include a changelog or any updates for our products. We would like to inform you that, until further notice, all support for RAZBAM-developed aircraft modules is on hold. This suspension encompasses, but is not limited to, bug fixes and updates.
We want to reaffirm our unwavering commitment to this exceptional community, our current customers, and prospective clients. Unfortunately, due to circumstances completely beyond our control, we are temporarily unable to continue our work at this time. Our team, a group of highly skilled and professional developers, is first and foremost made up of dedicated individuals. They invest not only their expertise but also their personal dedication and sacrifice into crafting our products. For many, this work provides essential supplementary income or even constitutes their primary livelihood.
We are hopeful for a swift resolution so that we can resume our normal operations. However, until these issues are resolved, we will not be issuing any updates about our products. We ask for your understanding during this challenging period, a situation that RAZBAM Simulations did not seek and which has previously seriously affected other parties, for example Heatblur Simulations. We have been patient, perhaps too patient, waiting for a resolution from the responsible parties. Now, we find it necessary to take a stand and await a practical solution to this deadlock.
I also want to extend my heartfelt thanks to my fellow third-party developers. Their support, once aware of the relevant facts, has been overwhelming. Thank you for elevating DCS to new heights; it truly wouldn't be the remarkable experience it is without your contributions.
The suspension will remain in effect until the significant issues between Eagle Dynamics and RAZBAM Simulations LLC are resolved to our mutual satisfaction. Once these issues have been addressed, we will resume our standard practices of bug fixing, updates, and upgrades, just as we have since our inception as developers for DCS. We hope this resolution results in a more stable and optimistic future for DCS and all 3rd Party Developers.
Best regards
Ron Zambrano
CEO
RAZBAM Simulations, LLC
Eagle Dynamics was compelled to respond shortly after on their Discord found here:
https://discord.com/channels/542985647502393346/543013214485610520/1225540029493936219
04/04/2024 1:18 PM
Following the message published by Ron Zambrano of Razbam Simulations, we believe that it is necessary to rectify some of the unfounded allegations and to reassure the Community that everything is being done to resolve the current situation promptly and for the benefit of all concerned.
 
Without entering into the details of matters that are confidential to the parties, we firmly reject the allegations that the current disagreement between Eagle Dynamics and Razbam Simulations would be as stated by Razbam “due to circumstances completely beyond our control" and that it is "a situation that Razbam Simulations did not seek".
 
On the contrary, the current disagreement is the result of improper actions that have been taken by Razbam Simulations, in breach of its contractual obligations towards our company and of our legally protected IP rights, and for which we are seeking a reasonable and forward-looking commercial outcome rather than entertaining legal claims.
 
We very much regret that Ron Zambrano has decided, without even pre-advising us, to make these disparaging public statements and, more importantly, to take the customers of the Razbam developed aircraft as leverage in the discussions with us. 
Please rest assured, we are addressing the situation with the utmost attention and constructiveness.
Many thanks and kind regards,
Nick Grey
RAZBAM followed with this reply:
https://discord.com/channels/536389125276827660/544501300134543380/1226492074233434182
razbam_prowler — 04/07/2024 4:21 AM
@here 
Dear customers and community
RAZBAM Simulations is actively working with EAGLE DYNAMICS to reach an agreement to resolve our internal dispute and we don't want the discussion that our public declaration has generated to escalate any further. We want to assure you that it has never been nor will it be our intention to abandon our products. We look forward to a prompt and satisfactory resolution, turn the page, and move forward.
Best regards
Ron Zambrano
CEO
RAZBAM Simulations, LLC
This was the last of the official announcements from both management parties.
While both teams have officially been very quiet due to the delicate nature of issues at hand there has been some events that have come up and caused concerns.
Some Anti-Virus programs were picking up a false positive on some DCS DLLs. Sadly it seemed to be worse on some of the RAZBAM modules fueling fears of issues with the modules. This can be solved by adding the DCS install folder to the exceptions for your anti-virus software, this happens from time to time so this was nothing new. 
The M2000 had some issues, including CTDs. This was an accidental merge of some changes one of the developers was working on. Once it was identified the changes were reverted and the issues were solved (although nothing was noted in the changelog at the time). This was not anything related to compatibility with the core game.
June 12th at Midnight the F-15E radar stopped working. While we have internally identified the issue no fix has been presented as of yet. once we have solid news on that we will share that ASAP. Again this had nothing to do with core compatibility but rather something in the coding of the F-15E.
UPDATE: When version 2.9.6 drops it will contain a fix for the F-15E radar. This fix was created by our team and not given to us by any other party. 
Refunds
While at first, we were maintaining our normal refund rules, we decided to bend a little for those who were frustrated with the issues and how they affected an Early Access Product. We have been giving a store credit for the value of the F-15E when you purchased it. You may open a ticket here: https://www.digitalcombatsimulator.com/en/support/ for a refund, but we ask for patience as it may take up to 7-10 business days to process your refund. 
Other modules will not be refunded at this time, all of these are out of Early Access and remain working. It is our commitment that no matter what happens we will do our best to make sure these continue to work into the future. We understand those of you who remember losing the Hawk, this is not something we intend to do again.
Steam refunds are based on the play time of the core game, not the individual module. It is their policy and they handle the refunds. As we understand it, no refunds have been accepted by Valve. All modules continue to work, aside from the current radar issues with the F-15E which we hope will be addressed sooner than later. South Atlantic continues to be updated and as I stated above, the other older modules we plan to make sure they continue to work into the foreseeable future. 
Is ED broke?
No, Eagle Dynamics is very healthy aside from this dispute currently, all other 3rd Parties and the ED development team continue to work and push new and exciting content out to you. 
Is ED pushing things out because they are out of money?
No, most of these recent products have been scheduled for quite some time now, into early last year. The 3rd Party products are based on when they are ready from their own team, although some delays here and there squished some release dates together, nothing has been out of the ordinary except more goodies in a short amount of time. 
How can you keep selling the F-15E or other modules? UPDATE 2025-04-07
Right now we are working within the framework of the legal advice moving forward and not wanting to cause any more riffs or issues. It's a complex process at this point and most likely why it seems to be moving so slowly for everyone. Nothing more can be said about that right now. Sorry.
After receiving an official request by RAZBAM to remove products from sale we have done so. All products will be fully supported by DCS and will continue to operate.
We cannot comment on any more conspiracy theories than this. This was an unfortunate disagreement that had been going on for some time and finally went public. I can only speak for Eagle Dynamics but I believe both teams want to resolve this as fast as possible and get back to making virtual airplanes. 
The discussion below was the old thread. This new thread may be moderated a little harder, so please be nice to each other, know that all the other customers in here discussing this with you are in the same boat and probably want the same thing. So let's be open to their opinions and concerns and understand they are allowed to have them as much as you are. Anything from any user here without an official tag won't be making any official comments, me and @BIGNEWY will only comment on publically available info as this is a legal matter at the end of the day.
I cannot say enough, on behalf of all of us at Eagle Dynamics, how sorry we are that you are being made, in part by us, to go through this. We are committed to getting this sorted as soon as we can.
Thanks
The ED Team
 

This effect is from the modelling of the gyroscopic effect of the engine. We believe it is correct as is. Thanks all. 

Please see the road map. I know its take a long time, but the detail and work that goes into a modern-day pilot model is huge, and we do not only have the F-16 to do. That said it is coming very soon and getting very close. Thanks.

This has been requested internally in relation to some of this, some of this might be not so appealing to the masses. Thanks.

No, it will slave to the steerpoint's set altitude, so the only solution would be to create a new one or edit the altitude on the current one. 

The F/A-18C is feature complete based on what we advertised, plus a LOT more we did not advertise on the store page. There are some additional items in progress that we are still working on, some of which are not confined to the F/A-18C. Out-of-early access does not mean the end of development. 
The only unique, new feature is Radar Bump Mode, but even that is in progress and never advertised as a feature. It's an item that we later added to further improve the product.
Thanks!

This is what I said recently on Hoggit about this subject, I did double check with Kate to make sure I was on the correct page:
 
Obviously all this is not fleshed out 100% so what I say is only based on what we have said in newsletters and some times Kate (the COO) has shared on DIscord.
Current maps would not transfer to a world map, in that you couldn't copy and paste them into it based on the tech that it would use to create that world map. Some of the assets and such may, possibly, be able to be used to speed up the development of areas on a World map you might want to raise the details on but not sure how that will all work. But no, the area maps will not transfer (as we understand it at this time) as well Area maps will still have their place for era-specific maps (such as WWII), etc.
All this world map stuff is still very fluid and heavily subject to change, but that is the current understanding right now.
 

We have nothing on a timeline to share right now, but when we are more confident in a possible release window we will announce it. Thanks!

I apologize for your frustrations and for my English here in this section. 
I have recently raised a concern for consistency across all modules, including the Hornet. I hope the team will take a hard look at these issues with reflections and customer concerns. We do hear you and you are not being ignored or discarded. 
Thank you,
NineLine/Norm 

This is now reported for both the 109 and 190A, I apologize it took so long and was missed originally. 

I think the best bet right now is to set the house to late activation and visible before activation.
You can then set a trigger with conditions for the house to activate. This will limit the ability of the house to engage as well as limit the enemy to engage with the house.
I will give some thought to other solutions but this one makes the most sense right now.