April 14, 20215 yr Didn't manage to get it work in terms of LVAR/HVAR. Was trying to do it with C172G1000 and X-touch mini. AP buttons, HDG, COMs, NAVs - all that work properly. However, FMS knob, G1000 softkeys etc. do not work. They did before yesterdays update, of course, I went carefully through the how-to by @Lorby_SI, applied all the changes needed. My concern is about the number of the Vcockpitsection. Do I have to play the overall next number or the the VCockpit next number?
April 14, 20215 yr hi is the version 2.06 out? i can provide u with my purchase recipe if u need it, I justo don't know where to find that AAO manual
April 14, 20215 yr Author Commercial Member 6 minutes ago, Carlosmax50 said: hi is the version 2.06 out? i can provide u with my purchase recipe if u need it, I justo don't know where to find that AAO manual You will find the link to the AAO manual in the Windows Start Menu, section "LORBY-SI" I don't dare release the 2.06 publicly just yet. This "solution" feels too clunky for my taste. I am somehow hoping that Asobo will fix MSFS rather sooner than later... LORBY-SI
April 14, 20215 yr Author Commercial Member 29 minutes ago, spottair said: Didn't manage to get it work in terms of LVAR/HVAR. Was trying to do it with C172G1000 and X-touch mini. AP buttons, HDG, COMs, NAVs - all that work properly. However, FMS knob, G1000 softkeys etc. do not work. They did before yesterdays update, of course, I went carefully through the how-to by @Lorby_SI, applied all the changes needed. My concern is about the number of the Vcockpitsection. Do I have to play the overall next number or the the VCockpit next number? VCockpit next number. Double check that you really have the new WASM in the panel folder and that the layout.json is correct. Those VCockpit definitions may require some cleaning up. Here are a few examples: Quote FBW A320 NX: [VCockpit18] size_mm=0,0 pixel_size=0,0 texture=$PFD background_color=0,0,0 htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=systems.wasm&wasm_gauge=systems, 0,0,0,0 [VCockpit19] size_mm=0,0 pixel_size=0,0 texture=$PFD background_color=0,0,0 htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=LorbyLVarHookWASM.wasm&wasm_gauge=LCS, 0,0,0,0 WT CJ4: [Vcockpit06] size_mm=0,0 pixel_size=0,0 texture=$PFD background_color=0,0,0 htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=workingtitle-cj4-wasm.wasm&wasm_gauge=FdGauge,0,0,1,1 [Vcockpit07] size_mm=0,0 pixel_size=0,0 texture=$PFD background_color=0,0,0 htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=LorbyLVarHookWASM.wasm&wasm_gauge=LCS, 0,0,0,0 Aerosoft CRJ 700: [VCockpit03] size_mm=2048,2048 pixel_size=2048,2048 texture=$efb_display background_color=0,0,0 ident=12026 htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=ASCRJ_700.wasm&wasm_gauge=EFBV, 44, 20, 1950, 1300 [VCockpit04] size_mm=0,0 pixel_size=0,0 texture=$efb_display background_color=0,0,0 htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=LorbyLVarHookWASM.wasm&wasm_gauge=LCS, 0, 0, 0, 0 Edited April 14, 20215 yr by Lorby_SI LORBY-SI
April 14, 20215 yr Just now, Lorby_SI said: VCockpit next number. Be careful with those VCockpit definitions, they may need some cleaning up. Here are a few examples: Where exactly is this going to be add? I can understand the issue with the 2.06 do u still need my purchase information? I can still can send it if u need it! Can I buy u a cup of coffe?
April 14, 20215 yr Author Commercial Member 2 minutes ago, Carlosmax50 said: Where exactly is this going to be add? I can understand the issue with the 2.06 do u still need my purchase information? I can still can send it if u need it! Can I buy u a cup of coffe? PDF with full instructions is included with the 2.06. As my post says - send me your proof of purchase, then you get the download. You can PM me here too if that is easier. LORBY-SI
April 15, 20215 yr 12 hours ago, Lorby_SI said: VCockpit next number. Double check that you really have the new WASM in the panel folder and that the layout.json is correct. Those VCockpit definitions may require some cleaning up. Here are a few examples: @Lorby_SI, would you like to verify if this config is correct? [VCockpit01] size_mm=1024,768 pixel_size=1024,768 texture=$AS1000_PFD_1 background_color=42,42,40 htmlgauge00=NavSystems/AS1000/PFD/AS1000_PFD.html, 0, 0, 1024, 768 [VCockpit02] size_mm=1024,768 pixel_size=1024,768 texture=$AS1000_PFD_2 background_color=42,42,40 htmlgauge00=NavSystems/AS1000/MFD/AS1000_MFD.html,0,0,1024,768 [Vcockpit03] size_mm=230,45 pixel_size=230,45 texture=$Hourmeter emissive=0 htmlgauge00=Generic/Misc/HourMeter/HourMeter.html, 0, 0, 230, 45 [Vcockpit04] size_mm=0,0 pixel_size=0,0 texture=$PFD background_color=0,0,0 htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=LorbyLVarHookWASM.wasm&wasm_gauge=LCS, 0,0,0,0 [VPainting04] size_mm = 1024,256 texture = $RegistrationNumber location = exterior painting00=Registration/Registration.html?font_color=white, 0, 0, 1024, 256 [VPainting05] size_mm = 256, 64 texture = $RegistrationNumber location = interior painting00=Registration/Registration.html?font_color=white, 0, 0, 256, 64
April 15, 20215 yr Author Commercial Member 26 minutes ago, spottair said: would you like to verify if this config is correct? The "texture=$PFD" part should probably be "texture=$Hourmeter" (or any texture that is actually in the panel.cfg file). Note: I made an automated installer app too. When you re-download the package again, you will find an additional ZIP with the WasmModuleInstaller app. Instructions have been updated as well. The app hasn't been tested a lot, so if you prefer the manual method, that is still in the instructions too. LORBY-SI
April 15, 20215 yr 1 hour ago, Lorby_SI said: The "texture=$PFD" part should probably be "texture=$Hourmeter" (or any texture that is actually in the panel.cfg file). Note: I made an automated installer app too. When you re-download the package again, you will find an additional ZIP with the WasmModuleInstaller app. Instructions have been updated as well. The app hasn't been tested a lot, so if you prefer the manual method, that is still in the instructions too. It still does not work for me (LVARs/HVARs), even with the installer. Bevor proceeding with the installer, I reverted all original aircraft files and then ran the installer. What makes me wonder is the syntax of the additional lines added by the installer to the layout.json file. There are doubled backslashes instead of "normal" slashes as they are used in all remaining entries. Is this correct? }, { "path": "SimObjects/Airplanes/Asobo_C172sp_AS1000/TEXTURE/thumbnail_small.JPG", "size": 36003, "date": 132270119900000000 }, { "path": "SimObjects\\Airplanes\\Asobo_C172sp_AS1000\\panel\\LorbyLVarHookWASM.wasm", "size": 74661, "date": 132598867921473970 }
April 15, 20215 yr Author Commercial Member 2 hours ago, spottair said: Is this correct? Yes, it works either way. Can you be more specific about what exactly is not working? I just tested it on my end with the G1000 C172. Both LVars collection and triggering the PFD Softkey-HVars works fine. I used the installer. Edited April 15, 20215 yr by Lorby_SI LORBY-SI
April 15, 20215 yr Author Commercial Member Hello @ll, since feedback has been positive, I have decided to take the plunge - version 2.06 has been uploaded to the shops, it should already be available on SimMarket. The workaround instructions and the installer tool are in a separate ZIP file, please make sure to read the release note and the instructions carefully. Once MSFS has been fixed, you can deactivate the workarounds with the installer tool and use the standalone module again (I hope…) Edited April 15, 20215 yr by Lorby_SI LORBY-SI
April 15, 20215 yr 4 hours ago, Lorby_SI said: Yes, it works either way. Can you be more specific about what exactly is not working? I just tested it on my end with the G1000 C172. Both LVars collection and triggering the PFD Softkey-HVars works fine. I used the installer. Managed to get it to work. It was probably my fault at the end - I applied all the changes needed to C172G1000, selected that aircraft but with a non-standard livery called Kenmore. @Lorby_SI Thanks for your assistance and the solution you provided to override Asobo's fault.
April 15, 20215 yr 4 hours ago, Lorby_SI said: Hello @ll, since feedback has been positive, I have decided to take the plunge - version 2.06 has been uploaded to the shops, it should already be available on SimMarket. The workaround instructions and the installer tool are in a separate ZIP file, please make sure to read the release note and the instructions carefully. Once MSFS has been fixed, you can deactivate the workarounds with the installer tool and use the standalone module again (I hope…) Thank you very much for your quick support and great communication !
April 16, 20215 yr Author Commercial Member Hello @ll JustFlight customers, here is an open link to the workaround app and instructions, should those not show up in your account: https://www.dropbox.com/s/jqhiy9bdqh6mu2t/AAO_2.06_MSFS_1_15_7_crash_workaround.zip?dl=0 Best regards LORBY-SI
April 16, 20215 yr Author Commercial Member Hello @ll, the MSFS hotfix 1.15.8 is now live. The sim is no longer crashing when a stand alone WASM module is present, so things can go back to normal. Do I need a new version of AAO? No, the 2.06 B08 that is in the shops will work fine How do I remove the workaround? panel.cfg and layout.json must be reverted to their original state. You can do that either manually, by reinstalling the plane or with the WASM installer tool. If you were using the tool and it throws an error when you try to remove a configuration, check the plane folders manually - the original layout.json and panel.cfg files are there, renamed to “.original”. → After that just reinstall AAO If AAO is only displaying a white window in the taskbar, delete the following folders: C:\Users…\AppData\Local\Lorby-SI\LorbyAxisAndOhs_MSFS.exe_Url_czjzikxvfp4omouhsqicacm52dqowlpu (= everything that has those cryptic characters at the end) ATTENTION: Be mindful that this is not the same folder as the one with the configuration database - that is LORBY_SI and you should not delete that!! I don’t know if (3.) happens everywhere, but it happened to me. Edited April 16, 20215 yr by Lorby_SI LORBY-SI
Archived
This topic is now archived and is closed to further replies.