|
Post by javitxin55 on Jul 6, 2021 16:45:53 GMT
Hi!
First of all, kudos for this project. It’s exactly what I was looking for. I’ve been flying and enjoying it since I bought it with no issues on previous versions.
However, after today’s update, I’m not being able to fly the A22. I mean, when autoupdate is done, I reload the plane as stated, and then, when try to proceed with the engine start, no response from any knob, button, etc. They are clickable, the are moving, I can set the Fuel selectors, Lights, carb heater, avionics (but gps doen’t turn on), but nothing happens when done.
So far, with v1.07, the only way to work with it is forcing to start up the engine with the option displayed in xplane menu, but things about knobs behaviour remains the same.
I’ve also noticed the altimeter now is only available for inHg but not for Hpa, since it always shows 0.000 despite for inHg is working fine.
So, now I’m flying in V1.0, since is the one I downloaded when bought the plane from store, and disabling the autoupdate option.
Is this a known situation? What could I do to fix it?
Thanks in advance,
J.
|
|
|
Post by VSL-Admin on Jul 6, 2021 18:50:35 GMT
Hello,
Can you see the autoupdater green message (update complete)?
|
|
|
Post by javitxin55 on Jul 6, 2021 20:05:11 GMT
Hello, Can you see the autoupdater green message (update complete)? Hi! Yes, the update seems to be completed. Then I reload the aircraft and once reloaded is when it starts to not response. I have just tried to update again from a clean instal of the aircraft, but it's the same. Find attached some pictures. Thanks for your support. Edit: in last photo you can see that also the key keeps blocked in starter position whitout coming back to on position.
|
|
|
Post by VSL-Admin on Jul 6, 2021 20:30:22 GMT
Hi! You're welcome Ok for some reason, it looks like an xlua file inside the plugins folder is not being initiated... Please try to disable all 3rd party plugins and reload the aircraft. Let me know your status!
|
|
|
Post by VSL-Admin on Jul 6, 2021 23:00:51 GMT
Hello, Can you see the autoupdater green message (update complete)? Hi! Yes, the update seems to be completed. Then I reload the aircraft and once reloaded is when it starts to not response. I have just tried to update again from a clean instal of the aircraft, but it's the same. Find attached some pictures. Thanks for your support. Edit: in last photo you can see that also the key keeps blocked in starter position whitout coming back to on position. Hello again, Also, please check to eliminate any assignments/hardware conflict that you might have.
|
|
|
Post by javitxin55 on Jul 7, 2021 7:04:20 GMT
Hi! Yes, the update seems to be completed. Then I reload the aircraft and once reloaded is when it starts to not response. I have just tried to update again from a clean instal of the aircraft, but it's the same. Find attached some pictures. Thanks for your support. Edit: in last photo you can see that also the key keeps blocked in starter position whitout coming back to on position. Hello again, Also, please check to eliminate any assignments/hardware conflict that you might have. Good day! Not many 3rd party plugins installed, I have been checking and removing them but not working yet. Regarding possible hw conflicts, I use Aribus sidesticks and it looks like if working ok too, since yokes ar moving well after updating. In addition, after update the plane, I have checked the plane's files and all of them seem to be updated, even the lua files placed in plugin's folder. It's strange because I don´t find the point where it fails, but it's sure that is after updating because in v1.0 and v1.05 it works fine until moving to v1.07. I have been checking the log after reload the plane on v1.07 and I can see this: 0:00:18.875 I/SND: This aircraft is using FMOD in PARTIAL mode. 0:00:18.875 E/SOUN: snd error in file: Aircraft/VSKYLABS Aeroprakt A22-LS Project AU Build v1.0/fmod/VSL Aeroprakt A22-LS.snd line 378 0:00:18.875 E/SOUN: The sound event event:/gps has an invalid command trigger sim/cockpit/radios/transponder_code I attached that log just in case you can see where the fail is. Many thanks Log.txt (76.47 KB)
|
|
|
Post by VSL-Admin on Jul 7, 2021 7:41:00 GMT
Hello again, Also, please check to eliminate any assignments/hardware conflict that you might have. Good day! Not many 3rd party plugins installed, I have been checking and removing them but not working yet. Regarding possible hw conflicts, I use Aribus sidesticks and it looks like if working ok too, since yokes ar moving well after updating. In addition, after update the plane, I have checked the plane's files and all of them seem to be updated, even the lua files placed in plugin's folder. It's strange because I don´t find the point where it fails, but it's sure that is after updating because in v1.0 and v1.05 it works fine until moving to v1.07. I have been checking the log after reload the plane on v1.07 and I can see this: 0:00:18.875 I/SND: This aircraft is using FMOD in PARTIAL mode. 0:00:18.875 E/SOUN: snd error in file: Aircraft/VSKYLABS Aeroprakt A22-LS Project AU Build v1.0/fmod/VSL Aeroprakt A22-LS.snd line 378 0:00:18.875 E/SOUN: The sound event event:/gps has an invalid command trigger sim/cockpit/radios/transponder_code I attached that log just in case you can see where the fail is. Many thanks View AttachmentHello! OK! This was deeply investigated and finally.... a bug was found! In general it was related to the wing-sweep axis assignment (for the braking handle), that broke the whole aircraft code in certain axis positions...the issue was simple to resolve but tricky to be spotted, as it was affected by hardware settings as well. but all is good now. The bug was fixed and was just injected into the project, which turned version v1.07a. Thank you for reporting this, and apologize for the inconvenience!
|
|
|
Post by javitxin55 on Jul 7, 2021 7:41:07 GMT
Edit:
Hi!
You were faster than me with your answer
I confirm it all works fine now on v1.07a
Once again, thank you very much for your support.
Best regards,
|
|
|
Post by VSL-Admin on Jul 7, 2021 8:27:27 GMT
Edit: Hi! You were faster than me with your answer I confirm it all works fine now on v1.07a Once again, thank you very much for your support. Best regards, Hi there! You're welcome!
|
|