JTFF - Raph

Hi Nineline, No problems everything is from my personnal learning or public DBs (no shenanigans with dorking etc). I do not have access to any classified data so I am sure it will be fine. I will wait for your feedbacks guys and as said I would be happy to help further. Have a nice day

@BIGNEWY Hello, I had the bug one hour ago. What I noticed. Setup : no mods, flying on Flashpoint EU with satnav. I have a track but it is to heavy for forums restrictions, feel free to download it with this link : https://wormhole.app/1pM4q#eQDAn5dSaIHKH4clwE_SXA I understand if you do not trust external file uploads but I have no choice here ^^ The file will be available during 24 hours. Behavior observed : - Lost ability to lock SAMS with the Harm Attack Display - After selecting a steerpoint and doing a cursor zero with TGP, the sensor is correctly pointing towards it, but after a couple seconds it always points towards BULLSEYE - All my navigation system was broken and even if I selected any steerpoint every sensors where pointing towards BULLSEYE - One the HSD I could see filled selected steerpoint but the HSD cross was stuck on the BULLSEYE, also the HUD was displaying wrong informations (e.g. BULLSEYE range infomations towards another steerpoint) - On the HAD I displayed SEAD coordinates on DED and they where also stuck on BULLSEYE coords What I tested : - Checked if it was an INS drift or something bound to Satnav, but it seemed to be fine (tought I had a huge delta with estimated position at first) - Checked steerpoints coordinates - Tried to disable the BULLSEYE on stp 25 - Tried to cycle A/G A/A and NAV modes - Tried to switch TGP to standby to see if it wasn't "slaving" all my sensors by error - Tried to cycle between POS and HAS modes - Tried to cycle steerpoints from C&I page or HSD Results : - Unable to resolve in flight with previous manipulations How to reproduce : Hard to reproduce, but I destroyed an SA-2 site before it happened, maybe as in SP it could come from HAD. Also BULLSEYE or TGP could create shenanigans on top of an HAD issue. I was cycling between all SAM site on HAD page when the problems started. Hope it helps a little, this bug is really blocking if it happens during flight. Good day

Hello, Did you guys reported the bug and attached a track ? If not we should do it to make sure ED team is aware of that problem (even if INS is in early access state) Have a good day

Hello, 1 - DTC for all aircraft in M.E. or at start menu (first autocompletion in the mission editor depending on mission and environnement) + personnal DTC profiles per category 2 - Auto generate kneeboards and comcards, ability to remove default kneeboards 3 - Huge amount of Callsigns from different countries. 4 - More AI reactions and behaviours like BARCAP, TARCAP, CSAR, AI, CAS etc (less triggers and scripting) +AI refueling management or automation 5 - SAM interconnexion ability 6 - Advanced weather options like snow, icing, rain (maybe with dynamic weather?) 7 - 3D edition tool (to place objects and check terrain instead of launching the mission) 8 - Multiple selection of objects and related functionalities 9 - More units templates + more objects (FARP, hesco walls, infantry for example) 10 - Map filters (roads, borders, water etc) It's more in sim feature, but the possibility to create/edit the flight plan of the selected aircraft before jumping in the cockpit while joining a server slot, in brief menu, would be awesome. Kind regards, Raph.

@BIGNEWY Sorry for the ping but this thread seems to be in relation with this one : Proof of concept here : https://www.dropbox.com/t/BMLOpihqauNaX707 My track reached 5.3MB. Kind regards, Raph.

Hello, I was asking myself the same question, but i finally understood. In DCS now you have to validate your location in NORM within 2 minutes, but it's not mandatory in the case of a Stored alignment. If you don't confirm your coordinates, you will be aligned, but it seems like the HSI and HUD have no inputs about the flight plan. Kind regards, Raph.

Hello, The wing flex is at this moment incorrect, if you apply a load on stations 3, 4, 6 or 7 (especially on 4 and 6) the wings are twisted in all directions. Client side bug (cause wing flex seems to be only client side). Wing_flex_bug.trk The bug works with every type of load, but will be different depending on the weight and the location. Sincerely yours, Raph.

@Flappie Hello, I'm writing you regarding the page file, I used as you recommended a 32Gb page file on my system SSD coupled with my initial 32Gb of RAM. I haven't flew so much since we talked about it. But I did two full flights. I'm sad to say that we only got arround the problem, because a lot of people are running DCS with only 16Gb of RAM. Thank you for your help, I really hope everybody here will find a solution to fix it. Sincerely yours, Raph.

Hi @Flappie, That's not an easy thing to deal with DCS crashes, I agree! And you guys are doing a good job. I don't agree with the myth of the invicible SSD's but I spended a lot of money and time in DCS and I want to fix it. So I'll run a 32Gb page file while couple days. But as I said I'll crash later... I've already done all theses tests in the ticket wich is not accessible for you. small (or absent) pagefile; overclocking of RAM or GPU; external software messing with the game files, with the drives, the CPU or the GPU; mods ; altered/damaged DCS game files and/or temp files; faulty drivers; faulty SATA cables; dust on the CPU; faulty PSU; GFX effects incompatibilities; low DRAM voltage; BIOS parameters... Do you have a little list of the BIOS parameters, OC settings, voltage issues messing with DCS ? It would be helpfull if I had some of your feedbacks regarding this list you wrote. In fact the hardware on my side is working fine but I'm pretty sur that something doesn't work with DCS on my config since an update (because nothing have changed during the 2 past years) . But at the same time I recommend to ring the bell arround this issue before more users will be impacted. I have more and more people telling me that they have the same problem wich I'm stuck with. Sincerely yours, Raph.

Hello @Flappie , Thank you for your quick answer. I have 32Gb of physical RAM, I don't understand a lot of people is running DCS with 16. As I said I, usually I don't use a swap because I don't need it. I set a page file because ED told me to use one if I would have some help. DCS was running without it since a long time, not everybody has 32 Gb of RAM! I set 10Go to give me "a chance" to achieve the end of my flights, and to prevent the worst case scenario BSOD... It's set on my SSD and thrust me it's not good to write on it like this. If I use 32Gb of swap on the SSD with DCS writing on it everytime that's not good! If I use 32Gb on an HDD it will be laggy and unflyable when the memory will swap. => note that at the second I'm connected to a server all 32Gb will be blasted (Why?). If you refer to this ticket 102143, I did a lot of tests with page file and even if I set 32Gb it's gonna swap and crash. With the system managed page file I reached 70Gb. So I'm currently understanding that you are asking me to use 64Gb of RAM and destroy my professionnnal SSD to fly on DCS? While some friends are running with 16. It's been almost two years now I can't fly properly like @PaulG and I'm being really frustrated by this issue..

Up

@Flappie Hello, I just did what we said: - Removed all mods - Deleted D:\Program Files\Eagle Dynamics\DCS World OpenBeta\MissionEditor - Deleted all my missions from the editor - Done a full clean up / repair I had the time to fly on a server this evening and of course I crashed. dcs.20210228-182802.crash dcs.log

@BIGNEWY Hello, I already done that one year before and even if I do it now it will be the same. - I removed all mods - Reinstalled DCS 4 times - Reinstalled Windows 2 times - Checked all possible hardware issues on my side Now some friends have the same problem. What can we do now ? I can try to open a new ticket, do the same things during months. Or I can wait for more people having this issue to hopefully have an idea of what is causing this. What do you recomend ? Okay I'll do it. Thanks a lot.

Hello @Flappie, Thank you for your message. Yeah sure I can send everything. But I really think that nothing (or nobody) will fix it. I haven't done a full flight for ages (one year at least on a server or a medium mission). I received some messages from Andrey Filin, Valery A. Khomenok, Scott Newnham, Alexander Maximov and a lot of help from @BIGNEWY on the ticket number 102143 last year. Now this problem persists since 2 years. With many others we've lost hope to see a way to stop it. If I remember correctly, on ticket was opened for the dev team. We always have: - A crazy amount of memory used - Memory not clreared and increasing - The swap always blasted (I was running the Sim without it until mid 2020) - An access violation error with the vcruntime140.dll Crash cause: # -------------- 20210205-210612 -------------- DCS/2.5.6.60966 (x86_64; Windows NT 10.0.19041) C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll # C0000005 ACCESS_VIOLATION at EBC316E9 00:00000000 SymInit: Symbol-SearchPath: '.;D:\Program Files\Eagle Dynamics\DCS World OpenBeta;D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'rapha' OS-Version: 10.0.19041 () 0x100-0x1 0x00000000000016E9 (VCRUNTIME140): memcpy + 0x3F9 0x00000000000085AE (edterrainGraphics41): (function-name not available) + 0x0 0x0000000000014097 (edterrainGraphics41): (function-name not available) + 0x0 0x0000000000011262 (edterrainGraphics41): (function-name not available) + 0x0 0x000000000000E7F0 (edterrainGraphics41): (function-name not available) + 0x0 0x00000000000DAA50 (edCore): (function-name not available) + 0x0 0x00000000000D73F8 (edCore): (function-name not available) + 0x0 0x00000000000214C2 (ucrtbase): (function-name not available) + 0x0 0x0000000000017034 (KERNEL32): (function-name not available) + 0x0 0x000000000004D0D1 (ntdll): RtlUserThreadStart + 0x21 And in the logs the crash "area" (not full log I haven't set the autoexec) : 2021-02-27 21:26:30.267 WARNING FLIGHT: carrier technician [2: green_hbb] created, id 6 2021-02-27 21:26:30.267 WARNING FLIGHT: carrier technician [2: green_nw] created, id 7 2021-02-27 21:26:31.019 WARNING FLIGHT: procCrewAssignAircraft client id 16829731, crew_id 2, hot_start 0 2021-02-27 21:26:31.019 WARNING FLIGHT: wCarrierCrew::set_LA() assigned aircraft Pilot ROOSEVELT #07 - PAK 1 on runway 2 2021-02-27 21:26:47.335 ERROR SOUND: invalid source_params(woLA-16805920:aircrafts/engines/afterburnerrearclose): gain 2021-02-27 21:26:47.335 ERROR SOUND: invalid source_params(woLA-16805920:aircrafts/engines/heavy_rear_afterburner_crackle): gain 2021-02-27 21:26:47.335 ERROR SOUND: invalid source_params(woLA-16805920:aircrafts/engines/afterburnerrearclose): gain 2021-02-27 21:26:59.009 ERROR SOUND: render time = 0.011144s exceeded allowed slice of 0.010159s 2021-02-27 21:26:59.022 ERROR SOUND: render time = 0.013433s exceeded allowed slice of 0.010159s 2021-02-27 21:26:59.043 ERROR SOUND: render time = 0.011989s exceeded allowed slice of 0.010159s 2021-02-27 21:27:07.756 ERROR GRAPHICSVISTA: Can't open model F-16C_oblomok_wing_R. 2021-02-27 21:28:03.039 WARNING FLIGHT: crew 2 wCarrierCrew::reset_LA() 2021-02-27 21:31:50.299 ERROR Lua::Config: Call error onShowPool:[string "./MissionEditor/modules/mul_playersPool.lua"]:194: bad argument #1 to 'pairs' (table expected, got string) stack traceback: [C]: ? [C]: in function 'pairs' [string "./MissionEditor/modules/mul_playersPool.lua"]:194: in function 'updateSlots' [string "./MissionEditor/modules/mul_playersPool.lua"]:184: in function 'create' [string "./MissionEditor/modules/mul_playersPool.lua"]:288: in function 'show' [string "./MissionEditor/GameGUI.lua"]:398: in function <[string "./MissionEditor/GameGUI.lua"]:392> (tail call): ? (tail call): ?. 2021-02-27 21:31:50.551 INFO EDCORE: try to write dump information 2021-02-27 21:31:50.553 INFO EDCORE: # -------------- 20210227-213150 -------------- 2021-02-27 21:31:50.554 INFO EDCORE: DCS/2.5.6.61527 (x86_64; Windows NT 10.0.19042) 2021-02-27 21:31:50.555 INFO EDCORE: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll 2021-02-27 21:31:50.556 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 53C216E9 00:00000000 2021-02-27 21:31:50.562 INFO EDCORE: SymInit: Symbol-SearchPath: '.;D:\Program Files\Eagle Dynamics\DCS World OpenBeta;D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Raphael' 2021-02-27 21:31:50.563 INFO EDCORE: OS-Version: 10.0.19042 () 0x100-0x1 2021-02-27 21:31:51.001 INFO EDCORE: 0x00000000000016E9 (VCRUNTIME140): (function-name not available) + 0x0 2021-02-27 21:31:51.001 INFO EDCORE: 0x00000000000085AE (edterrainGraphics41): (function-name not available) + 0x0 2021-02-27 21:31:51.002 INFO EDCORE: 0x0000000000014097 (edterrainGraphics41): (function-name not available) + 0x0 2021-02-27 21:31:51.002 INFO EDCORE: 0x0000000000011262 (edterrainGraphics41): (function-name not available) + 0x0 2021-02-27 21:31:51.002 INFO EDCORE: 0x000000000000E7F0 (edterrainGraphics41): (function-name not available) + 0x0 2021-02-27 21:31:51.002 INFO EDCORE: 0x00000000000DAA50 (edCore): (function-name not available) + 0x0 2021-02-27 21:31:51.002 INFO EDCORE: 0x00000000000D73F8 (edCore): (function-name not available) + 0x0 2021-02-27 21:31:51.002 INFO EDCORE: 0x0000000000021BB2 (ucrtbase): (function-name not available) + 0x0 2021-02-27 21:31:51.003 INFO EDCORE: 0x0000000000017034 (KERNEL32): (function-name not available) + 0x0 2021-02-27 21:31:51.003 INFO EDCORE: 0x0000000000052651 (ntdll): (function-name not available) + 0x0 2021-02-27 21:31:51.021 INFO EDCORE: MiniDumpWriteDump failed. Error: 2147943855 2021-02-27 21:31:51.023 INFO DCS: enumerating loaded modules 2021-02-27 21:31:51.024 INFO DCS: D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe, 18610608 bytes, created 19:12:2020-11.23.47, written 19:12:2020-11.23.47, accessed 27:2:2021-21.28.30 2021-02-27 21:31:51.024 INFO DCS: C:\WINDOWS\SYSTEM32\ntdll.dll, 2024224 bytes, created 27:2:2021-17.24.7, written 27:2:2021-17.24.7, accessed 27:2:2021-18.29.2 2021-02-27 21:31:51.024 INFO DCS: C:\WINDOWS\System32\KERNEL32.DLL, 764976 bytes, created 12:2:2021-17.44.55, written 12:2:2021-17.44.55, accessed 27:2:2021-18.29.2 2021-02-27 21:31:51.024 INFO DCS: C:\WINDOWS\System32\KERNELBASE.dll, 2922392 bytes, created 12:2:2021-17.45.3, written 12:2:2021-17.45.3, accessed 27:2:2021-20.50.29 2021-02-27 21:31:51.025 INFO DCS: C:\WINDOWS\SYSTEM32\apphelp.dll, 570880 bytes, created 15:10:2020-18.28.24, written 15:10:2020-18.28.24, accessed 27:2:2021-21.26.57 2021-02-27 21:31:51.025 INFO DCS: C:\WINDOWS\SYSTEM32\AcGenral.DLL, 370176 bytes, created 15:10:2020-18.28.42, written 15:10:2020-18.28.42, accessed 27:2:2021-20.36.55 2021-02-27 21:31:51.025 INFO DCS: C:\WINDOWS\System32\msvcrt.dll, 637360 bytes, created 15:10:2020-18.28.26, written 15:10:2020-18.28.26, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.025 INFO DCS: C:\WINDOWS\System32\sechost.dll, 628616 bytes, created 12:2:2021-17.45.3, written 12:2:2021-17.45.3, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.025 INFO DCS: C:\WINDOWS\System32\RPCRT4.dll, 1222056 bytes, created 17:1:2021-19.26.24, written 17:1:2021-19.26.24, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.025 INFO DCS: C:\WINDOWS\System32\SHLWAPI.dll, 342440 bytes, created 17:1:2021-19.26.28, written 17:1:2021-19.26.28, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.025 INFO DCS: C:\WINDOWS\System32\USER32.dll, 1702416 bytes, created 17:1:2021-19.26.17, written 17:1:2021-19.26.17, accessed 27:2:2021-20.40.5 2021-02-27 21:31:51.026 INFO DCS: C:\WINDOWS\System32\win32u.dll, 132752 bytes, created 27:2:2021-17.24.3, written 27:2:2021-17.24.3, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.026 INFO DCS: C:\WINDOWS\System32\GDI32.dll, 161680 bytes, created 17:1:2021-19.26.13, written 17:1:2021-19.26.13, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.026 INFO DCS: C:\WINDOWS\System32\gdi32full.dll, 1075864 bytes, created 17:1:2021-19.26.24, written 17:1:2021-19.26.24, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.026 INFO DCS: C:\WINDOWS\System32\msvcp_win.dll, 634760 bytes, created 12:2:2021-17.45.1, written 12:2:2021-17.45.1, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.026 INFO DCS: C:\WINDOWS\System32\ucrtbase.dll, 1044888 bytes, created 12:2:2021-17.45.1, written 12:2:2021-17.45.1, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.026 INFO DCS: C:\WINDOWS\System32\ole32.dll, 1212232 bytes, created 17:1:2021-19.26.22, written 17:1:2021-19.26.22, accessed 27:2:2021-21.26.58 2021-02-27 21:31:51.027 INFO DCS: C:\WINDOWS\System32\combase.dll, 3507000 bytes, created 27:2:2021-17.24.6, written 27:2:2021-17.24.6, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.027 INFO DCS: C:\WINDOWS\System32\SHELL32.dll, 7639536 bytes, created 27:2:2021-17.24.9, written 27:2:2021-17.24.9, accessed 27:2:2021-21.31.2 2021-02-27 21:31:51.027 INFO DCS: C:\WINDOWS\System32\ADVAPI32.dll, 689024 bytes, created 7:11:2020-18.59.10, written 7:11:2020-18.59.10, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.027 INFO DCS: C:\WINDOWS\SYSTEM32\USERENV.dll, 176656 bytes, created 15:10:2020-18.28.25, written 15:10:2020-18.28.25, accessed 27:2:2021-21.26.58 2021-02-27 21:31:51.027 INFO DCS: C:\WINDOWS\SYSTEM32\MPR.dll, 109504 bytes, created 15:10:2020-18.28.27, written 15:10:2020-18.28.27, accessed 27:2:2021-20.56.54 2021-02-27 21:31:51.028 INFO DCS: C:\WINDOWS\SYSTEM32\SspiCli.dll, 230904 bytes, created 12:12:2020-12.51.15, written 12:12:2020-12.51.15, accessed 27:2:2021-21.26.58 2021-02-27 21:31:51.028 INFO DCS: C:\WINDOWS\System32\IMM32.DLL, 185448 bytes, created 15:10:2020-18.28.27, written 15:10:2020-18.28.27, accessed 27:2:2021-21.26.58 2021-02-27 21:31:51.028 INFO DCS: C:\WINDOWS\System32\WS2_32.dll, 427200 bytes, created 15:10:2020-18.28.27, written 15:10:2020-18.28.27, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.028 INFO DCS: D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\edObjects.dll, 264704 bytes, created 19:12:2020-11.23.28, written 19:12:2020-11.23.28, accessed 27:2:2021-20.36.56 2021-02-27 21:31:51.028 INFO DCS: C:\WINDOWS\System32\WLDAP32.dll, 326656 bytes, created 15:10:2020-18.28.25, written 15:10:2020-18.28.25, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.028 INFO DCS: D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Terrain.dll, 298496 bytes, created 19:12:2020-11.23.28, written 19:12:2020-11.23.28, accessed 27:2:2021-20.36.56 2021-02-27 21:31:51.028 INFO DCS: C:\WINDOWS\System32\CRYPT32.dll, 1425440 bytes, created 27:2:2021-17.24.6, written 27:2:2021-17.24.6, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.029 INFO DCS: C:\WINDOWS\System32\WINTRUST.dll, 382720 bytes, created 12:2:2021-17.44.59, written 12:2:2021-17.44.59, accessed 27:2:2021-18.29.2 2021-02-27 21:31:51.029 INFO DCS: C:\WINDOWS\System32\imagehlp.dll, 107416 bytes, created 15:10:2020-18.28.26, written 15:10:2020-18.28.26, accessed 27:2:2021-18.28.59 2021-02-27 21:31:51.029 INFO DCS: C:\WINDOWS\System32\OLEAUT32.dll, 831024 bytes, created 12:2:2021-17.45.1, written 12:2:2021-17.45.1, accessed 27:2:2021-21.26.58 dcs.log dcs.20210205-210612.crash dcs.20210227-213150.crash DxDiag.txt

Hi, What is the situation for you ? I have the same problem I'll crash everytime. Last year I opened a ticket. The support did not helped me so far (during 4 month approximately). I reinstalled a Windows 10 pro version, I thought the problem was solved but nows it's back! Crashing because of the memory used by DCS. Look at this: Here you can see memory swaping. I'm destroying my SSD by setting a page file on it only for DCS. And you ca be sure that everytime I fly it is writing on it like crazy. Here is one interesting topic you can read if needed: It's re-opened since June 2020 I really hope ED is gonna do something to solve this one day, the number of users experiencing theses crashes is increasing this year. Sincerely yours, Raph. DxDiag here.DxDiag.txt

Hi, I'm having the exact same issue, and I'm not finding solutions... I'm having CTD on every MP missions and also on SP if I set some units. My crashes are exactly the same, DCS crash, black screen, sometimes the video driver crashes. I can accelarate the passive memory leak while loading some liveries in spectator view. My 32Go are destroyed in a couple of seconds when I do this. Did someone find a way to fix this?

Good job thanks! Just saw Dan's post! Is he still alone on the Gazelle?

Hello, as everybody knows ED just changed core lights settings in the 2.5.6, it affected all modules. The Gazelle still looks like a Christmas Tree, will we have an update soon? I assume that this is only values to change in the code so why is'nt it done? Is the module just abandonned at this state? Cheers.

That's exactly the question I was asking myself, I was discussing with friends on an "other sim". I don't want to name it because I'll get censored or banned ^^. And we get better performances on this one... I gonna ask it to BN.

Hi, it's the same for all ED modules at this moment!

So there is a problem somewhere else, an AMRAAM not able to reach a 55nm launch considering that DLZ are not implemented. Before this update we where capable to get a real max range over 60 nm

+1

Hi there, Since the update, loft seems better, but I founded an issue on the guidance. Note that the first AMRAAM is lauched at 56nm with a low aspect, high altitude and high closure rate. I'm launching this missile way before my HUD indicates max range because DLZ are not implemented (cf this post https://forums.eagle.ru/showthread.php?p=4265751) It seems like the missile is not updated and dumb in the last seconds. Missile was supported continuously during the F-POLE and goes HPRF when I still have a SAM lock on the hostile. As you can see, the AI will not defend or do anything when a missile is not gonna be dangerous. This missile is considered as "no factor". Second launch is inside the "max range" and reach the hostile. Everything in this one: Track AMRAAM.trk Tacview here: https://we.tl/t-6PzkDPICJs Cheers, Raph.

Second content with tracks on wetransfer (there is more than 3 slots for joint files in the forum) tracks here https://we.tl/t-ETHd8vT5Qx diagrams will be updated as soon as i can: