Jump to content

RAZBAM_ELMO

ED Closed Beta Testers Team
  • Posts

    2093
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by RAZBAM_ELMO

  1. 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.
  2. Marking as RESOLVED and moving to RESOLVED
  3. So the SSS functions work correctly however its the key binds for it that reverse?
  4. 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
  5. 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
  6. Have you looked into the new HTS mode switch logic that was posted a while ago regarding the changes? If you are not in TPOD HTS mode and in INS then the controls with not move according to the TPOD but in fact on the EHSD or the HUD
  7. Im gonna need you to recheck things and separate the individual bus into their own tracks.
  8. Pickle button must be held for 1.5 seconds. This is to simulate the data transfer to the JDAM. Marking AS INTENDED and moving to RESOLVED.
  9. 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.
  10. We attempted to have the TPOD zoom specific keys zoom in when held but it was very touchy and did not respond well therefore was left as incremental. As mentioned above, there is not actual TPOD zoom fiunction on the HOTAS and IRL is done through the right MPCD. I too bound the corresponding OSBs to that function......till I get me some cougar MFDs
  11. Can you confirm you are attempting to control the HUD brightness or the UFC brightness. The knob on the UFC labelled BRT controls the brightness of the UFC lights. below the UFC and above the standby ADI and CRS switch you have another row of switches and knobs. The left most knob adjusts the HUD display brightness. The right two control the brightness and contrast of the NAVFLIR.
  12. 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.
  13. TRK file req. alot of it comes down to external factors as well as your entry speed and altitude on release. NOTE: the MK20 CBU in PRI fuse mode will open and release the bomblets at 1500FT ASL while the OP fuze will open up at 1500FT AGL. Take into account your altitude and your TGT atltitude and set your PUC up accordingly. Also note that at higher airspeeds, alot more drag can be induced on the bomb affecting accuracy which is important if youre bombing from a higher altitude. Usually for CBU drops using CIP you would want to ideally be in the realm of 5000- 8000FT AGL in the initial roll in with your TAS at around 400.
  14. No our knowledge this is fixed in internal builds from ED. Marking as DUPLICATE REPORT and moving to RESOLVED.
  15. Part was that, part was there may have been a discrepancy in the HUD format change to SVG. Confirm this now works for all please.
  16. 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
  17. CORRECTION, it appears that there was a mistranslation on how the CCRP cue's behaviour works and is being reconfigured. This will be re-worked an implemented at the earliest possible convenience. Apologies for the mix up.
  18. I have it blinking with less than 6 at 4 remaining. Programs can be edited in the .lua but I also recommend checking out DICE to set up programs alot easier. Will confer with SME on quantities remaining that the IR light blinks.
×
×
  • Create New...