IronMike Posted September 18 Posted September 18 Hey Everyone! Time to start shipping what we've been working on this summer; starting this patch with a large upgrade to the DCS: AJS-37 Viggen! From here, we're setting our sights on launching the AI Intruder and Early -A in the next patch. This large Viggen update overhauls and enhances many core and fundamental systems. The biggest highlight is the new electrical system, bringing a host of new warnings and failures, circuit-breaker functionality, instrument fault indications, improved RAT and AC/DC failure modelling, and more. We’ve also fixed the issue preventing RB-24 and RB-74 missile lock ons — our sincere apologies for the inconvenience. Additional improvements include an updated RWR and database, restored KB automatic mode, major fixes to the RUTA display, and refinements to instruments, cartridge and WP management and more. In all, this update delivers a wide range of fixes and quality-of-life enhancements. Please see the full Viggen changelog below and we can't wait to hear your feedback. We hope you enjoy! Stay tuned for the launch of the Intruder and early Kitty as we wrap up the summer's work. Your Heatblur Team DCS: AJS-37 Viggen by Heatblur Simulations NEW and overhauled Electric System NEW warnings and failures Electrics Hydraulics Autopilot AFK Reverser Changes to the RWR Updated database to be closer to the F-4’s Fixed radar carrier freq. not being set (ELINT file now has the emitter band set correctly) KB’s automatic mode works again. Added full fidelity MiG-29 to RWR library Added logic for the breakers ADI aligns to magnetic heading (+ deviation correction set) on the ground and if the fast erect button is pressed. Calibrated to true heading on rotation (based on stored runway heading) Added warning flag logic to air speed indicator and altimeter (LDOK) Cartridge loading now requires being on the ground and in BER Airbrake will slowly close from the airflow if hydraulic pressure is lost in Syst. 1 RAT failure when extended happens at much lower air speeds (>700 km/h) Added AC-DC rectifier failure Implemented a fix for “rough search” on reciprocal runways Fixed the “BANA line” hiding Fixed RR/ANF “cross” on CI stuck on screen Temperature measuring logic has been improved Flood lighting is now on during cold starts Implemented a random start position for the ADI Fixed kneeboard WP names Backup heading now shows raw magnetic heading, without declination correction Fixed HUD/ADI commands being stuck to U point Added logic to unselect U point (Safety unsafe or ANF selected) U point can now be reselected after having been overflown Timeline and compass now shows in LowNav mode when <40s from U WP Fixed RB-24 and RB-74 (Sidewinders) not locking anymore Setting rb15 ToT now only requires pressing BX button (without needing to press 8 as well) Updated rb15 ToT calculations FÄLLDLAST now illuminates on light test Added variable indicator light brightness Added instrument backup lighting Added instrument fault indications Distance Fuel Speed Altimeter ADI Pitch trim Corrected RUTA display Circle now shows R point location – it moves between them on “WP change” when drawn Line now alternates pointing toward previous and next RUTA WP Only draws R points that are “in order” (ie. with R1,2,3,4 all 4 are shown, but with R1,2,3,5 only 1 to 3 are) Changes to “Destination presentation” when a R WP is selected AoA indicator shows aircraft pitch on the ground Changed yaw Trim switch hint from “Emergency Yaw Trim” to “Yaw Trim” Updated the manual 6 6 Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/
dsc106 Posted September 18 Posted September 18 Love that you guys are still working on this, its a wonderful module. Thank you! Also a user request (prayer?) - your other modules come with some bundled campaigns and mini-campaigns. Here's begging for a Heatblur Kola map campaign for the beloved Viggen! 4 VR Exclusive (5950x/5090/G2) | All DLC | Buttkicker + HF8 | Virpil Everything w/MFG Crosswinds [CM3 Base + 200mm Extension]
gabuzomeu Posted September 18 Posted September 18 Hi, there are 3 free heatblur campaigns with Viggen already. (2 caucasus, 1 nevada) 1 Details: Asus Z-170E, Intel i5-6600K @ 4.2GHz, 16GB RAM MSI GTX970 Gaming 4G Win 10 Home
Rudel_chw Posted September 18 Posted September 18 1 hour ago, gabuzomeu said: Hi, there are 3 free heatblur campaigns with Viggen already. (2 caucasus, 1 nevada) and this one is of high quality and set at kola: https://www.digitalcombatsimulator.com/en/files/3345732/ 2 1 For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Coragem Posted 10 hours ago Posted 10 hours ago I had DCS Crash 2 times just hiting the previous dtc binding key. I opened kneeboard moved to the proper page, hit previous dtc binding and DCS crashed. 2 times same error. Wonder if this is a bug and where is the best place to report it Here is the stack trace from the log. And the F10 marker plan i had setup. 2025-09-26 02:20:50.637 INFO EDCORE (Main): try to write dump information 2025-09-26 02:20:50.915 INFO EDCORE (Main): # -------------- 20250926-022051 -------------- 2025-09-26 02:20:50.916 INFO EDCORE (Main): DCS/2.9.20.15384 (x86_64; MT; Windows NT 10.0.26100) 2025-09-26 02:20:50.917 INFO EDCORE (Main): C:\Jogos\DCS World OpenBeta\Mods\aircraft\AJS37\bin\AJS37-Avionics.dll 2025-09-26 02:20:50.919 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007fff5d54b2dc 00:00000000 2025-09-26 02:20:50.920 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Jogos\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'varbe' 2025-09-26 02:20:50.921 INFO EDCORE (Main): OS-Version: 10.0.26100 () 0x100-0x1 2025-09-26 02:20:50.930 INFO EDCORE (Main): 0x000000000008b2dc (AJS37-Avionics): RadarMaterial::Init + 0x2CBC 2025-09-26 02:20:50.931 INFO EDCORE (Main): 0x0000000000115eba (AJS37-Avionics): cockpit::AJS37::NavigationIndicator::initialize + 0x2CCA 2025-09-26 02:20:50.931 INFO EDCORE (Main): 0x0000000000115c84 (AJS37-Avionics): cockpit::AJS37::NavigationIndicator::initialize + 0x2A94 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x00000000001de75a (CockpitBase): cockpit::avDevice::setUpdateHandler + 0xCBA 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x0000000000233a6e (CockpitBase): cockpit::avDevice::performClickableAction + 0x5E 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x00000000004009b7 (CockpitBase): cockpit::avSyncable::update_entity + 0xCC57 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x000000000085840d (DCS): SW + 0x23C1DD 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x0000000000b53ddb (DCS): SW + 0x537BAB 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x0000000000a623c0 (DCS): SW + 0x446190 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c253a (WorldGeneral): ActionDispatcher::process_ + 0x7A 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c2056 (WorldGeneral): ActionDispatcher::dispatch + 0x16 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c5b80 (WorldGeneral): TimedActionBuffer::feedEventsUpTo + 0xF0 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x000000000000430f (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x1DF 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000004aa2 (World): wSimCalendar::DoActionsUntil + 0x262 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a6d1fd (DCS): SW + 0x450FCD 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a6ced4 (DCS): SW + 0x450CA4 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a90809 (DCS): SW + 0x4745D9 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a44cf4 (DCS): SW + 0x428AC4 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x0000000000a46333 (DCS): SW + 0x42A103 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x00000000025b8d0c (DCS): AmdPowerXpressRequestHighPerformance + 0x1097D08 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x00000000010dac82 (DCS): SW + 0xABEA52 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17 2025-09-26 02:20:51.822 INFO EDCORE (Main): Minidump created. F10-map markers plan Scooter 3-3 _ Coragem.ini
ASW Posted 9 hours ago Posted 9 hours ago 1 час назад, Coragem сказал: I had DCS Crash 2 times just hiting the previous dtc binding key. I opened kneeboard moved to the proper page, hit previous dtc binding and DCS crashed. 2 times same error. Wonder if this is a bug and where is the best place to report it Here is the stack trace from the log. And the F10 marker plan i had setup. 2025-09-26 02:20:50.637 INFO EDCORE (Main): try to write dump information 2025-09-26 02:20:50.915 INFO EDCORE (Main): # -------------- 20250926-022051 -------------- 2025-09-26 02:20:50.916 INFO EDCORE (Main): DCS/2.9.20.15384 (x86_64; MT; Windows NT 10.0.26100) 2025-09-26 02:20:50.917 INFO EDCORE (Main): C:\Jogos\DCS World OpenBeta\Mods\aircraft\AJS37\bin\AJS37-Avionics.dll 2025-09-26 02:20:50.919 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007fff5d54b2dc 00:00000000 2025-09-26 02:20:50.920 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Jogos\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'varbe' 2025-09-26 02:20:50.921 INFO EDCORE (Main): OS-Version: 10.0.26100 () 0x100-0x1 2025-09-26 02:20:50.930 INFO EDCORE (Main): 0x000000000008b2dc (AJS37-Avionics): RadarMaterial::Init + 0x2CBC 2025-09-26 02:20:50.931 INFO EDCORE (Main): 0x0000000000115eba (AJS37-Avionics): cockpit::AJS37::NavigationIndicator::initialize + 0x2CCA 2025-09-26 02:20:50.931 INFO EDCORE (Main): 0x0000000000115c84 (AJS37-Avionics): cockpit::AJS37::NavigationIndicator::initialize + 0x2A94 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x00000000001de75a (CockpitBase): cockpit::avDevice::setUpdateHandler + 0xCBA 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x0000000000233a6e (CockpitBase): cockpit::avDevice::performClickableAction + 0x5E 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x00000000004009b7 (CockpitBase): cockpit::avSyncable::update_entity + 0xCC57 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x000000000085840d (DCS): SW + 0x23C1DD 2025-09-26 02:20:50.932 INFO EDCORE (Main): 0x0000000000b53ddb (DCS): SW + 0x537BAB 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x0000000000a623c0 (DCS): SW + 0x446190 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c253a (WorldGeneral): ActionDispatcher::process_ + 0x7A 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c2056 (WorldGeneral): ActionDispatcher::dispatch + 0x16 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x00000000000c5b80 (WorldGeneral): TimedActionBuffer::feedEventsUpTo + 0xF0 2025-09-26 02:20:50.933 INFO EDCORE (Main): 0x000000000000430f (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x1DF 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000004aa2 (World): wSimCalendar::DoActionsUntil + 0x262 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a6d1fd (DCS): SW + 0x450FCD 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a6ced4 (DCS): SW + 0x450CA4 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a90809 (DCS): SW + 0x4745D9 2025-09-26 02:20:50.934 INFO EDCORE (Main): 0x0000000000a44cf4 (DCS): SW + 0x428AC4 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x0000000000a46333 (DCS): SW + 0x42A103 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x00000000025b8d0c (DCS): AmdPowerXpressRequestHighPerformance + 0x1097D08 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x00000000010dac82 (DCS): SW + 0xABEA52 2025-09-26 02:20:50.935 INFO EDCORE (Main): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17 2025-09-26 02:20:51.822 INFO EDCORE (Main): Minidump created. F10-map markers plan Scooter 3-3 _ Coragem.ini 2.42 \u043a\u0411 · 0 загрузок 1 1 GreyCat_SPb
Zabuzard Posted 6 hours ago Posted 6 hours ago It is "just" the known issue. As explained in the threads, the exact way how the bug surfaces on your end changes with each update (for technical reasons - its called "Undefined Behavior"). 1 1
Coragem Posted 55 minutes ago Posted 55 minutes ago 5 hours ago, Zabuzard said: It is "just" the known issue. As explained in the threads, the exact way how the bug surfaces on your end changes with each update (for technical reasons - its called "Undefined Behavior"). Thanks, didn't know that was a thing before this update, i never had it ocurring before, and now I get that crash very frequently, good to know its mapped already thx for the info, any work arounds possible besides not using the DTC?
ASW Posted 44 minutes ago Posted 44 minutes ago 8 минут назад, Coragem сказал: Thanks, didn't know that was a thing before this update, i never had it ocurring before, and now I get that crash very frequently, good to know its mapped already thx for the info, any work arounds possible besides not using the DTC? 1. If I manually enter the coordinates into the inertial system, there won't be a problem. 2. If you insert the cartridge in NAV mode, then close the Kneeboard, switch the mode to BER and dial 9099, everything works. (50%) GreyCat_SPb
Recommended Posts