RAZBAM_ELMO

This is not bullying. Its simply a way to distinguish a bug that is from the module or another bug caused by a mod or a corrupted file that the devs can see that you might not. Maybe its a script messing with it, maybe SRS, maybe VIACOM. As far as this bug goes, I am not seeing it on my side so I am inclined to believe it is your side but I might be wrong. I use the same OB that everyone else uses. As for whether it gets reported or not, rather than flood the internal system with bugs that might not actually be bugs or issues that are the users error, I vet and sift through all of them and collect all the necessary evidence on the matter. Once I have all of that info, I pass it along to the CB testers to verify the bug and collect a sample of information for the dev team. Once the investigation is complete, I then add it to the internal tracker and assign it to team members depending on the issue. This is a streamlined and more efficient approach which reduces clutter and enhances the focus of the team in order to see, fix, and release a patch for it. Also to add to any speculation of "well why dont they test this so it doesnt happen?" Lets say in a period of 4 weeks, the dev team uses 2 of those weeks to find, fix and repair the issues, then in 1 week they test that 1 system to make sure it works, then they submit the fix to ED. ED runs their own tests with CB Testers which might not even look at our bug. Then theres a week cutoff prior to the release which all #PDs have to meet and enter their data into. After all of that, the patch makes its way to you. Now imagine in all this time your fixing bugs, testing and working on new material simultaneously. Theres not alot of free time left in the day. I remind you these are regular people like you and I who have jobs, families and other life commitments that we have to work into our schedules. While I appreciate the effort everyone goes through, I do not appreciate when people assume, judge or accuse anyone (whether its the dev team, another 3PD, myself or anyone else part of this community) without knowing the full scope of the situation. Your post will remains TRK FILE REQ. until your evidence is brought forth. Once that information is in, I will carry it through the proper steps as I have described to you above where it is thoroughly investigated and a proper fix is made. If you do not want to, thats ok. I wont close the thread or delete it. I will leave it here, ask for updates on it when a new patch comes, and wait for the proper information to be entered. I hope that sufficiently answers your questions @ataribaby

Hi. Yes I did send you off an email earlier when the issue occurred. Sent from my SM-N960F using Tapatalk

Are you experiencing any crashes at this time? Sent from my SM-N960F using Tapatalk

Nothing youre doi g wrong. We simply added color so hitting MAPM in the main EHSD or DATA page and look at your bottom OSBs you should see a COLOR option Sent from my SM-N960F using Tapatalk

@re4ly i seem to be having an issue. All parts I got installed correctly but seems either im not getting power or my PC is not recognizing the controller. I installed the software in the pdf and even it does not recognize the controller. Do you have any idea what may be causing this? Sent from my SM-N960F using Tapatalk

This is what happens when a target in front is jamming. This behavior is as intended. Marking as AS INTENDED and moving to RESOLVED. Sent from my SM-N960F using Tapatalk

The trk helps us determine in your game whether its the module and a bug or something within your own files that is causing the issue.

Just to make things clear. This snuck itself in and was meant to wait until it was more complete. So apologies for it getting out and not being entire finished. Sent from my SM-N960F using Tapatalk

This is more of what I'd like to see in our community. Nobody jumping on each other or trying to assume things without knowing the story. The OP had concerns but needed to think first. Apologizing for the way it was interpreted was a great start ad he has my forgiveness. During this trying time I know anxiety and frustration can boil over but we all need to be compassionate and understanding of everyone's unique situations in order to work together. Im very proud of how everyone has responded and is working to better understand everyone's point of view from here, to discord and even in game on the radios. You are all doing a great job. Keep it up. Sent from my SM-N960F using Tapatalk

did you update the .trk file as well? If not please attach it to the post above this

Not at this time. Feature has yet to be implemented. Sent from my SM-N960F using Tapatalk

Thats alright. DCS is complex and frustrating, we all know that. But we need to step away and breathe sometimes, ask others for help. Sent from my SM-N960F using Tapatalk

Did you try performing the tests and then hit the AP STBY button on the stick? Sent from my SM-N960F using Tapatalk

You make a very good point. Think of it this way though. The longer we work on and perfect it, the better the end product will be. Slowly adding things into the module will make sure all the systems are perfected and work together. I look forward to all the teeny tiny bugs you guys find in the future. Sent from my SM-N960F using Tapatalk

Well bud, if you're having issues im sure there are better ways to go about it than going out and calling it a POS. Hop on our Discord, find me, PM me and ill find a time to sit down and show you the ropes. Perhaps its that you aren't doing something correctly that is leading to the inconsistencies you're having. Practice doesn't make perfect. Perfect practice makes perfect. Sent from my SM-N960F using Tapatalk

Standby on the pictures gents, having issues, getting on the ringer with ED now to see if its a me problem or a forum problem

Hello everyone. During this difficult time the world finds itself in, we here at RAZBAM would like to offer our condolences, prayers and thoughts to all those who may be affected or know someone who has been affected by the COVID-19 pandemic. Our team is no exception, yet I’d like to take this moment to thank the team for their hard work over the last few weeks in the re-approach. I would also like to thank the community for their steadfast support, insight and yes criticism in the last few weeks. You have all done an amazing job and the future is already bright because of it. I know most of you are not here for the sappy stuff, so I’ll move right along and let you know what’s happening on the inside. First off you probably already know that a lot of big changes came in the last update from us and the next big one is no exception. Now this is in part due to reassigning some team members from other projects and back onto the ones currently out and flying with you guys. Because of this, a halt was put on serious development of other modules like the Super Tucano and F-15E. The goal is to get all of the modules to a stage where any future issues with bugs or new systems integration can be handled by one person or takes the team a short period of time to deviate in order to correct. ​​​ In the effort to better connect with the community, RAZBAM would like to announce its endorsement of its official display team. Formerly X51, The RAZBAM Harrier Display Team will represent the Harrier module and RAZBAM in virtual airshows beginning with VFAT and into the future. We are excited to see what routines the Display Team is currently cooking up for the new flying season so be sure to check your virtual airshow calendars in the future and show your support. ​​​ As you may or may not have seen in our social media pages, Progress is developing on the Falklands map. I have those photos here for you to gaze upon. ​​​ ​​​ ​​​ ​​​ ​​​ As always this is WIP and is not indication of the final product. There is no release announcement as of yet or timeline ​​​ The MiG-23 work continues. Focus currently is on the external 3D model which is close to completion and entering its final stages with the cockpit internal model entering the early stages of design. Coding for any systems has not begun as work is focused on elsewhere. The RAZBAM MiG23 will be a Soviet VVS MiG-23MLA. In the Mission Editor, there will be a single option to introduce “ Iraqi ML Modifications “. This will include replacing the RWR with the SPO-15 unit and adding the ASO-2 Countermeasure Dispensers. They will not be individually selectable and must be set in the ME. ​​​ ​​​ ​​​ Some other 3D work has also been progressing on the English Electric Lightning. ​​​ ​​​ ​​​ ​​​ ​​​ ​​​ ​​​ ​​​ ​​​ ​​​ ​​​ ​​​ ​​​ Again, like the MiG-23, the external model is in its final stages while initial work to the cockpit model is in its infancy. No release date or schedule added, and all work here is WIP and subject to change in the future. Just for all of you who may or may not know, I am a member of the Canadian Armed Forces in the Regular Force, with this comes moves and last-minute transfers. Due to this I will be absent for the first few weeks of November. However I will still be on the forums making sure your bug reports for the next update are added to our internal tracker though I might not be able to personally interact with you guys or fly during this time. I appreciate the patience and encourage you all to work together if you encounter problems. We all can learn something new, in the end that person you help with a problem could probably save your butt in a fight somewhere down the line in Multiplayer. Now because I won’t be able to be at my computer for the update, I’m going to post WHAT WE HAVE CONFIRMED with ED as far as fixes that will be in the next update. Last minute hot fixes may make their way in but this is a pre-emptive list for you all to keep in mind when it drops. This list of CONFIRMED fixes for the next Open Beta Update are as follows: AV8B NA 1. GBU-54 are now loaded on DITERs. 2. Removed all TERs with 3 bombs from Stations 3 and 5 3. Improved JDAM Relative targeting procedure. Now it is possible to do multiple JDAM relative releases. 4. Improved: High Drag bombs can now be released as Low Drag 5. Improved: Ghost Velocity Vector on HUD will now flash when at limits of HUD display area. 6. Improved: Long W-inc does not disable JDAM Relative Targeting (TOO mode). To disable you must un-designate. 7. Added flight control system joystick switch abstraction key-binds 8. Fixed: FPM erratic behavior in NAV or AG mode when total velocity close to zero 9. Fixed: TPOD/JDAM CTD when releasing the bombs. 10. Fixed: TPOD erratic behavior when using JDAMs. 11. Fixed GBU-32 not tracking. 12. Fixed Waypoint Icon not visible if designated and NWS is pressed. 13. Fixed Com channel selector key-bind incorrect behavior. 14. Fixed LAR rings not showing on EHSD for GBU-54. 15. Fixed EHSD ground track digits still use TRUE when EHSI set to MAGNETIC. 16. Fixed: No mark-point menu option in AG mode. 17. Fixed: DMT roll stabilization when in A/A mode. 18. Fixed: AGM-65F internal handling inconsistency. 19. Fixed: HUD Velocity Vectors going invisible at some limits of HUD display area. 20. Fixed: Release tone to sound after each release. 21. Fixed: NSW not changing IRMAV FOV when missile is uncaged. 22. Fixed: AAR zone circle out of position when EHSD is decentered. 23. Fixed: Various issues with the caged velocity vector. 24. Updated: TPOD Functionality for G4 integration with aircraft systems: 24.a. TDC button (PB14) has been deleted. TDC modes are now only two: AC TDC and HTS. 24.b. HTS TDC now updates System Designation. 24.c. Super Wide FOV (SWFV) mode has been enabled (PB10). 24.d. LSS/LST Mode has been improved. To enable LSS/LST you must long press PB19 (INR). 24.e. Zoom factor has been incremented from 10x to 16x. Zoom factor increases/decreases by 0.3X. 24.f. Zoom factor now changes when long pressing PB3 or PB4 24.g. New laser modes have been added. 24.h. Tracking has been modified: AR (Area Track) only locks a ground position. PT (Point Track) can lock a moving target. MT (Moving Target) works the same as PT. 24.i. When the TPOD is the SOI, NWS slaves the sensor to the aircraft system designation. In addition to these added features, we plan on adding more functions to the TGP to better represent a n AV8B NA Mid life Upgrade. The following is a list of intended features which are being added slowly while cross checking its behaviour with the SME. AV-8B N/A Harrier II Midlife Upgrades Folks, there are important updates/upgrades coming to the AV-8B N/A. With these upgrades we are striving towards increasing the realism of the aircraft system behavior when compared with the real one. The following systems are affected: AUTO release mode JDAM relative targeting LITENING II pod (TPOD) integration with aircraft systems. AUTO release mode The AUTO release mode has been updated so it accurately simulates its behavior on the real aircraft. The changes are as follows: AUTO is fully integrated with the INS system via the EHSD page. To enable AUTO mode, it is necessary that the INS is in DESIGNATION mode. Otherwise AUTO mode will not engage, and no bomb release will be possible. This affects all bomb types: GPs, LGBs and JDAMs. The procedure to enable and use AUTO release mode is as follows: On the EHSD page, set the steering mode to WYPT or W/OS. Click on the DESG button (PB01) and box it. This will designate the current steer-point (waypoint, Mark-point, Target-point or their offsets) as the System Designated (SD) Target. The EHSD will show DESG STP on PB01. This indicates: DESIGNATION mode is enabled and that the steer-point and the SD are in the same location. Be aware that the INS will ALWAYS navigate towards the steer-point, not the SD. At this moment, the AUTO cues will appear (ALS, Release Cue, JDAM NIRD, etc). Now you can select a new target by using any of the aircraft’s sensors (TPOD, DMT, HUD, etc.). After the new designation, the EHSD will show DESG TGT on PB01. This indicates that the steer-point and the SD are not in the same location and that the aircraft is navigating towards the steerpoint. The AUTO cues will recalculate for the new SD. At this time, it is necessary to do a LONG WINC (pressing the Waypoint Increment HOTAS button for more than 0.8 seconds). This will accomplish the following: The SD location will be stored in Target-point 0 (T0) and T0 will become the new steer-point. It is at this point that the aircraft will start navigating towards the SD. The EHSD will show DESG STP on the PB01. Follow the AUTO cues for a successful release. Click on the DESG button to disengage the designation mode. Navigate towards your home base. Please be advised of the following: While DESG is boxed, any change in the steer-point by using the UP/DOWN arrows push buttons (PB12 and PB13) or a SHORT WINC, will cause the new steer-point to become the SD. It is possible to follow the flight plan route while in DESG. Just change the steer-point as needed. Just remember that the new steer-point will become the SD. JDAM absolute targeting is NOT affected by the changes in SD, since they use a different target contributor. JDAM relative targeting is affected since they use T0 as the target contributor. CCIP to AUTO conversion is not affected by the EHSD not being in DESG mode. When T0 is the steer-point, you can update it just by slewing the TDC. Do not do a new designation since that will place the system back to DESG TGT and you will need to do a LONG WINC. JDAM relative targeting JDAM relative targeting, also known as TOO mode, has become more practical. Initially you had to designate a target with the TPOD, lase it, and then LONG WINC to pass the target coordinates to the bomb and then release it. If you wanted to drop another bomb to a different target in the same area, you had to LONG WINC to release the previous coordinates and then redo the entire procedure for the new target. That is NOT how it works on the real aircraft. The procedure to do a JDAM relative targeting is as follows: Enable AUTO mode by following the AUTO release mode procedures. After the EHSD is DESG STP, designate your target with the TPOD. This will become the System Designation (SD). The EHSD will show DESG TGT. Use Laser ranging to get an accurate position of the SD in relation to the aircraft. LONG WINC to pass the SD position to T0. The EHSD will show DESG STP and T0 will be the new steer-point. Follow the release cues and drop the bomb when ready. To select a new target, just slew the TPOD sensor with the TDC. DO NOT DO A NEW DESIGNATION (pressing TDC down). T0 will automatically update itself. The EHSD will remain in DESG STP. Follow the release cues and drop the next bomb when ready. Repeat steps 8 and 9 as required. To leave JDAM relative targeting, just unselect the bomb or un-designate the target. LITENING II pod (TPOD) integration with aircraft systems The TPOD as originally simulated was Ver 1, or G1 in USMC parlance. The TPOD is being currently upgraded to the latest version: G4. There are several important changes: TDC control has been simplified. There are only two modes: Aircraft HOTAS (AC TDC) and TPOD HOTAS (HTS). The TPOD slew control (underlined TDC) mode has been deleted. To enter HTS you only need to double press the SSS switch as always. HTS now updates the System Designation, unlike the G1 version. We have corrected the AREA and POINT tracking modes. Now if the TPOD is in AR (AREA Tracking), it will only lock the spot on the ground it is aiming, even if a moving vehicle is there. To track a moving vehicle, the TPOD must be in PT (POINT Tracking), so it will attempt to track the selected vehicle. Please be aware that even on the real sensor, this is a difficult process. A new mode exists MT (Moving Target). This mode behaves exactly like PT but it has additional features that are not available at this time since they require some updates from ED. [*]The Laser modes have been increased to 5: TRNL (training), MRKR (Marker), LASER (Laser designator), D+M (Designator and Marker) and EYES (A low power Laser designator used to prevent damage to the eyes of the troops on the ground). [*]Super Wide FOV has been included. In this mode the screen increases from a 3.5º (CCD Mode)/6º (FLIR Mode) FOV to a 20º FOV. It only works in FLIR mode, if enabled when the TPOD is in CCD mode, the mode will change to FLIR. To enable press the SWFV button (PB10). Please be aware that if you long press SWFV, instead of entering SWFV mode, you will enable NAV mode, which has a 24º FOV but disables the TDC. In both SWFV and NAV modes the laser is disabled. [*]The Zoom has been increased from 10X to 16X. The Zoom factor changes by 0.3X. You can continuously change the Zoom factor by long pressing the Zoom buttons (PB03 and PB04). [*]A new mode will be included: MTC, which means Multiple Target Cueing. This mode is not available at this time, but it will be on next release. More info will be provided when the mode is ready. MTC will be enabled/disabled by clicking on the MTC button (PB14). [*]To enter LSS/LST mode, you must long press the INR (PB19) button. [*]When the TPOD is the SOI, pressing NWS will do the following: Stop LSS/LST mode and: Slave the TPOD to the SD. If the TPOD is slaved, it will undesignate both the TPOD and the SD. If no SD exists, it will set the TPOD into SNOWPLOW mode. This mode is not enabled yet, but it will be ready on next release. ATTENTION The AUTO mode release update is not certain to be released on the next update, since it was committed nearly the end of the submission cutoff date. In any case, it will be certainly released on the following update. As for the rest of the modules, because a lot of the focus has been on the Mirage and Harrier, Some fixes for the 19 did not make the cut for this update and only a few were added for the Mirage. They are as follows; Mirage 2000-C 1. Fixed: Missing wheels 2. Fixed: left/right wheel brake combined axis command not working. 3. Fixed: throttle deadzone at high throttle. 4. Fixed: Various issues with the caged velocity vector. That is your Q4 update from RAZBAM Simulations. I hope you all stay safe and healthy; I wish you all the best of luck in the endeavors you are taking and look forward to seeing you all in the skies! Sincerely, Zackery “Elmo” Coulombe RAZBAM Simulations Community Manager

That will be announced after the next OB update

This is in the single player missions? Please attach a .trk of the incident

Because it provides detail for the devs of what exactly is causing this issue. Whether thats pilot error or code error or possibly a mod creating the issue.

Thanks Raptor

I have already stated what is and what will be. If at some point it changes, then that will be so. I'm not going to continue beating this dead horse after I have already talked to the team, the SME and done my own tests to come to the conclusion pouring alot of my own personal time into trying to figure out the is and outs of the perception this is inaccurate behavior. I have no issues accurately hitting a target by using the top of the hexagonal pipper, not to mention I never use this unless its a column or a large area target. The behavior persists throughout every airframe that carries MK82SEs. We actually found the MK82AIRs tend to be more accurate and fall less short when using the center of the pipper but every single one had to use an earlier point of aim in order to hit the target accurately. But again using a method ill suited to this type of weapon. I am not a coder, im simply volunteering my spare time right now to help Ron and the RAZBAM team streamline their bug reporting, moderating the forums as well as assisting in acquiring talent for projects. Im also not sure where you assume our SME belongs to 2/5. Sure, the squadron does actively use our module in its simulators that is true but the identity of our SME is not public knowledge due to security concerns for them. So I would suggest avoiding assumptions as we all know that rumors can spread and in accurate information can be bad for everyone. What I ask is that there be a certain level of trust garnered here. I am doing the most that I can, with the free time I do have, to best represent the communities concerns. I'm coming from the community to help a dev team. I'm not paid, im not endorsed, nor am I receiving special benefits like CB access or free modules. I simply care about you all and the dev teams having great relationships free from harrassment and toxicity. Looking at other bugs and other resolutions I think its fair to say that what I say isn't a lie and I'm not deceiving or lieing to anyone for any reason. I do my best to bring the issues to the attention of the devs and have them look at it as well as working closely with community members and CB testers to find the root of the issues so they can be solved. When I do get a result, answer or resolution to the issue, that means I have done everything in my position to fix it for you guys. I've probably sat down and flown with several dozen folks who have had problems and simply needed coaching or a person to talk to who doesn't hide behind a forum label and just puts the blanket over everything. Im open and honest as much as my NDA contract allows. I hope this explains everything for you and we don't need to discuss things further regarding the matter. If the individuals who are considered "experts" want to reach out to me then it will go through the proper channels with regards to classified information and security measures to authenticate their identity and then perhaps using them as an SME if contracts and legalities allow. If you still have further concerns then I encourage you to PM me here or on the discord and we can set up a time to talk voice to voice to better ease concerns you may have and not babble on about it here. Sent from my SM-N960F using Tapatalk

trk file showing the issue please.

We are currently working with Baltic Dragon to bring a full Campaign in for the Harrier. Sent from my SM-N960F using Tapatalk

None taken. Its all a balance tho of trying to release a product for those that want it early and can deal with bugs and issues over a period of time before it gets finished vs. those who would rather have a fully complete module when they buy it. Can't make both happy at the same time. I mean look at the A-10C, it had flight model issues for years and it finally got fixed and addressed. Sent from my SM-N960F using Tapatalk