Jump to content

RAZBAM_ELMO

Members
  • Posts

    2093
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by RAZBAM_ELMO

  1. Discord link should be in the main RAZBAM sub thread Different missions with different weather or same mission? PT track IRL is notoriously difficult. Usually if thats the case its being done by a two seater or by a buddy lase/ track so one pilot doesnt have such a high workload.
  2. Well Ramsay pretty much said it. DCS sees icls and awls as the same thing and thats a core issue we have no control of.
  3. Passed along to the team and reported.
  4. Fix made available as this is not something that can be solved for everyone and is a case by case basis. Team is working on a special TAB to allow adjustment in the future. Marking as FIX AVAILABLE and moving to RESOLVED.
  5. Fix has been posted in the link above. This is a case by case issue, and due to such we are looking at implementing these features into a special tabs option. Marking as FIX AVAILABLE and moving to RESOLVED.
  6. Its difficult to tell too if this is just labelled as a GAU12 or if its something different. Quite a few TPOD data things that we dont have on the Gen4
  7. Curious. Ive never run into that. CAn you post a trk of the issue so I can try to replicate?
  8. I would implore you to join our discord and send me a PM. That way I can set up a time and date so we can go over this issue. Not 30 minutes ago I was able to set frequency and entered a laser code to contact and spot a JTAC lase, was able to get a point track on the vehicle from 12nm, then at 6nm got an IRMAV lock first try. Just to confirm you are doing all of this in Stable or open beta?
  9. No it is not. Lukes statement is correct and is how we were told by the SME. Does that answer everything for you? Not everything that is stated in the manual is correct with whats on the actual jet.
  10. RAZBAM DEVELOPMENT GROUP What is The RAZBAM Development Group? RAZBAM Development Group, or RaDG, is being developed for the ever-expanding range of products RAZBAM develops both internally for DCS and its worldwide partners. Its job will be to rigorously test and check all RAZBAM’s modules and assets in various environments to ensure that we produce the most comprehensive and detailed study level modules for our public and private clients. So, you want to be a RaDG Test Pilot? RAZBAM is looking to bring a group of dedicated, like minded pilots to the team to be a part of development now and in the future. We are looking for not only those that can learn and master the modules we develop but can also perform tests in a precise, consistent manner, multiple times in a single session. We will begin accepting applications for the RaDG Test Pilot programme but before you hit send, there are some requirements you will need to have in order to even be considered. - Have a PC system that can handle the high demands that DCS places on our computers as well as enough storage space to have upwards of 2-4 different DCS builds. Being able to privately stream their work to the Dev Team in high quality or record video would be an example. - Be in good standing in the ED forums and with ED. Background checks will be performed through the ED forums as well as on our Discord. - Have a DCS World standalone install (not a steam version) and have one or all of RAZBAM’s currently released modules. - Possess at minimum a HOTAS or similar system, as well as have TRACK-IR or VR compatibility - Be able to learn and memorize multiple systems and documents from various modules. For instance: accurately dropping unguided bombs in a MiG-19P, to inputting coordinates in the Mirage M-2000C’s PCN, or hoping right over and setting up an AUTO precision attack with JDAMS on a specified attack heading and IFR in the Harrier II NA. All seamlessly and done so precisely. - Work well as an individual and take initiative AND work well in a team environment either as a subordinate or a team lead. Additionally, being professional with public and private clients. - Be able to do research and content collection on various subjects pertinent to a specified module. - Have a basic understanding of aeronautics, aerodynamics and physics to apply into the simulator. - Creativity and excellent problem-solving skills. - Can test at minimum 2-3 hours a week or be flexible to test last minute fixes closer to scheduled updates. - Former Pilots and or Maintenance personnel is a plus and would be given higher consideration. - Basic or fluent English is preferred, higher consideration would be given to those who read, write and speak a secondary language as well. If you think you have what it takes to be a part of our Development Group, send an email to z.coulombe@razbamsims.com Please include the following in your email 1. For the title header use: RAZBAM Development Group Application 2. Full name 3. Skype name 4. Any and all usernames on all DCS related platforms (i.e. ED forums, Reddit, Discord and associated names there in) 5. DCS world username (the one you use on the storefront to purchase modules) 6. A brief essay on yourself, your DCS experience, and why you think you would be a good candidate for the RaDG Programme. 7. At maximum, a 20-minute private YouTube video or other video link demonstrating your skills and abilities in DCS World. 8. A table or your expected availability over the course of a week or a month as well as detailing your time zone, country of origin and languages spoken. Tryouts and trials will take place over the month of February and March. We are a busy team now so if we set up a time and date for your interview, we would expect you to make that timing or at the very least notify us that you will not be able to make your timing at least 48 hours in advance and provide us with an alternate.
  11. Where is this evidence you're basing this on?
  12. Updated original OB list. See table below with final table for SSS Functions.
  13. Very interast, we are definitely looking at improving the harriers sounds, first ive seen of this video
  14. From our lead dev on the matter: "YEs it is a known issue. it is a problem with the stroke (SVG) system. Fortunately it can be fixed in code, but it is a case by case basis. What is happening is that we are using a fixed thickness and fuzziness value when the display is exported. static const double thickness_fix = 1 / 0.8; static const double fuzziness_fix = 1 / 0.5; if (purpose == CURR_PURPOSE_GENERAL) { //Normal stroke processing for inscreen display } else { //Exported displays values shaderLineVariableParams.thickness = 8.0 * thickness_fix; shaderLineVariableParams.fuzziness = 3.0 * fuzziness_fix; } So, in the future, we can implement a Special Options that can modify hte fixed value. Unfortunately this cannot be solved for everyone with a single fix as it is a case by case basis. I am leaving this up here for everyone to share and see so individuals experiencing this issue can adjust as needed for themselves.
  15. An update for all of you. AS of todays update OB 2.5.6.60996. Unfortunately an internal error due to climactic conditions in our lead coder's area resulted in an update error which omitted the correct .LUA files being pushed to ED for the Mirage 2000-C. As a result, users may experience; VTB waypoint not showing, CCRP IP not functional and a crash when using hot start. Attached is a HOTFIX that will correct those issues. This HOTFIX is IC cleared and resolves the issues you may experience. We at RAZBAM apologize for the error and will make sure to authenticate all fixes in the future as to prevent the issue for occurring again. Mirage 2000-C Hotfix.zip
      • 7
      • Like
      • Thanks
  16. An update for all of you. AS of todays update OB 2.5.6.60996. Unfortunately an internal error due to climactic conditions in our lead coder's area resulted in an update error which omitted the correct .LUA files being pushed to ED for the Mirage 2000-C. As a result, users may experience; VTB waypoint not showing, CCRP IP not functional and a crash when using hot start. Attached is a HOTFIX that will correct those issues. This HOTFIX is IC cleared and resolves the issues you may experience. We at RAZBAM apologize for the error and will make sure to authenticate all fixes in the future as to prevent the issue for occurring again. Mirage 2000-C Hotfix.zip
  17. can you separate the tracks into their individual bugs you are experiencing? Regarding the PT, in DCS all sensors work as interrogators and not as you would think they should IRL. For the PT you must be in a certain zoom level to "contrast" the target as well as make sure the TPOD TDC crossed the center of the 3D model in order to achieve a PT lock.
  18. So if im getting this right this is affecting exports only? Our team has a wide selection of VR equipment and so far this seems to be a player/ hardware issue especially if using multimonitor display/ exports. Reported.
  19. Changelog for 03 February 2021 2.5.6.60966 DCS AV-8B N/A by RAZBAM Simulations Update: SSS Logic ( see table) final iteration reflecting MLU NA II with Gen 4 TPOD Update: LHA Tarawa search radar definitions. Fixed: ground roll stutter when moving from stopped position Fixed: aircraft rolling forward when chocks removed Fixed: position of AN/AAQ-28 LITENING on wing pylons Fixed: Corrected issue where refueling empty external tanks and then dropping them would result in aircraft unrecoverable spin Fixed: AG Gun gunsight boresight Ottoman Courier Campaign: Prologue M02: fixed rare issue where mission would not progress after radio switch to range fixed issue with truck hitting the Georgian UH-1 fixed issue with N14 not taxiing DCS M-2000C by RAZBAM Simulations Fixed: Flood Light effects. Fixed: Radar Max Detection Range limited to 80NM. NOTE: Any contacts beyond 80NM are for GCI intercepts ONLY and must be set using VTB controls as 'fake' or 'ghost' targets. Fixed: PCN ΔLat/ΔLon distance factor Fixed: Wrong ΔAlt input in PCN Fixed: green radio ch knob not turning when radio off. Fixed: Wrong TWS Closing Velocity Fixed: TACAN not working Fixed: Radar slow elevation increase Fixed: CCRP turn cues (inverted and not reacting to roll) Fixed: Added INS switch on to Autostart sequence Fixed: Police light ON/OFF switch Fixed: IFF set OFF on Air Start but still operates as if on Fixed: Adding more than 5 waypoints to VTB does not remove the oldest one Fixed: Can only add 4 waypoints to VTB instead of 5 Fixed: VTB WP persistence across flights. Fixed: CCRP-IP release cue Fixed: HUD WP reticle at correct place with wrong INS alignment Fixed: Waypoints position displayed on VTB is not affected by the INS drift Fixed: VTB Waypoints can't be added if outside radar azimuth cone Fixed: VTB Waypoint system stuck when 5 waypoints are added
×
×
  • Create New...