Page 1 of 1
AI Traffic XP11
Posted: Wed Sep 12, 2018 11:26 am
by ivo
Does 124thATCv2 plugin support to add AI traffic in XP11 ?
- where is download AI traffic for XP11 ?
- I tried add WT3 AI Traffic, but XP11 crash
Thanks
Re: AI Traffic XP11
Posted: Wed Sep 12, 2018 9:30 pm
by ntnll
ivo wrote: ↑Wed Sep 12, 2018 11:26 am
Does 124thATCv2 plugin support to add AI traffic in XP11 ?
- where is download AI traffic for XP11 ?
- I tried add WT3 AI Traffic, but XP11 crash
Thanks
Hi Ivo,
There is a basic AI support, but is experimental. It uses the native xplane AI model. Is under development, and not stable. I'll try to work implementing it in the future, now I'm busy with other priority, but I would like to work on it ASAP, and provide a support to WT3 as well. No enough resources to do everything together. Not in the next versions though
Re: AI Traffic XP11
Posted: Thu Sep 13, 2018 12:43 pm
by ivo
thank you fro replay.
Re: AI Traffic XP11
Posted: Sat Feb 02, 2019 3:24 pm
by aeroflo
I tried it with the X-plane 11 default planes and it also crashed. Is that what "should" happend?
OS: macOS 10.14.2
X-Plane 11.30R3/11.31R1
Re: AI Traffic XP11
Posted: Sat Feb 02, 2019 4:17 pm
by RandomUser
aeroflo wrote: ↑Sat Feb 02, 2019 3:24 pm
I tried it with the X-plane 11 default planes and it also crashed. Is that what "should" happend?
Yes.
Re: AI Traffic XP11
Posted: Mon Feb 04, 2019 9:12 am
by ntnll
aeroflo wrote: ↑Sat Feb 02, 2019 3:24 pm
I tried it with the X-plane 11 default planes and it also crashed. Is that what "should" happend?
OS: macOS 10.14.2
X-Plane 11.30R3/11.31R1
The last version is unstable, I hope to fix the bug in the next build. I suggest to keep it disable in the current version, this feature is definitely in a embryonic state
Re: AI Traffic XP11
Posted: Mon Feb 04, 2019 9:12 am
by ntnll
aeroflo wrote: ↑Sat Feb 02, 2019 3:24 pm
I tried it with the X-plane 11 default planes and it also crashed. Is that what "should" happend?
OS: macOS 10.14.2
X-Plane 11.30R3/11.31R1
The last version is unstable, I hope to fix the bug in the next build. I suggest to keep it disable in the current version, this feature is definitely in a embryonic state