Hi,
I did my first own AI traffic for test only (from small airfield). P3Dv5 and traffic was created using AI Flight Planner (I'm learning it).
I noticed that AI plane goes near straight from parking point (to the forest, next to the inside of mountain ect ). Airport was created using ADE, I think its OK, but maybe I miss something for AI traffic?
hschuit wrote: 12 Mar 2021, 12:09
You need to add a hold short node between the parking spot and the runway start node. If you use the ADE fault finder it will detect issues like this.
Henk.
Thx a lot. ADE fault finder didnt detect this.
I added it, however its the same still (just the plane stops for 1-2 seconds on this point). I added default Cub for the test (to check it's not a model) , the same:
What about the radio chatter between ATC and AI model? Maybe something is wrong with take off clearance. Does the AI model have a correct Aircraft.cfg [radios] section? Does the airfield have a tower frequency? Does the airfield have a correct runway - the black runway taxi path with the runway start circle is not enough.
The red hold short node should be between parking and runway link. And you have to delete the one on runway link. Obvisouly you just added an normal blue node.
hschuit wrote: 12 Mar 2021, 13:46
What about the radio chatter between ATC and AI model? Maybe something is wrong with take off clearance. Does the AI model have a correct Aircraft.cfg [radios] section? Does the airfield have a tower frequency? Does the airfield have a correct runway - the black runway taxi path with the runway start circle is not enough.
Thx for advices. I added the tower, the communication is ok I suppose:
clearance was given. Model has radio entry in aircraft.cfg:
leuen wrote: 12 Mar 2021, 14:59
The red hold short node should be between parking and runway link. And you have to delete the one on runway link. Obvisouly you just added an normal blue node.
Cheers,
Martin
________________________________________ The Owl's Nest * Military Aircraft Reference * ICAO Reference * Distance Calculator * MAIW, Military AI & UKMil Reference
Your 18/36 runway only has one entry at the 18 end and in your screenshot above, ATC gives clearance for a 36 departure. The only way to get there is to taxi the runway down to the opposite end. I thought AI would not have a problem with that but I am not sure. What happens if you enforce a 18 departure by setting the wind direction from the south (180 degrees) ?
gsnde wrote: 12 Mar 2021, 17:16
The ADE Fault Finder does not find anything?
No, looks ok:
What I did now, I take different, finished bigger airport (also its a conversion from FS9/FSX). Added here Piper Cub for the test and result is near the same:
Radio works, he reqested of permission, recived it, starts to taxi but.... goes staright too, like it doesnt see taxi way.
hschuit wrote: 12 Mar 2021, 17:51
Your 18/36 runway only has one entry at the 18 end and in your screenshot above, ATC gives clearance for a 36 departure. The only way to get there is to taxi the runway down to the opposite end. I thought AI would not have a problem with that but I am not sure. What happens if you enforce a 18 departure by setting the wind direction from the south (180 degrees) ?
I tested it (changed direction of the wind), with 18 was the same.
The point is, it's quite a big project, I would like to finally add a little more life here, so AI traffic, but I can see that I have a problem with that. I suspect that I need to verify something more in the airports themselves so as to force the AI traffic to behave properly. Of course I can only stay with static models but AI gives a lot of immersion.
Seeing your test result, it looks like yet another tail dragger problem. AI tail dragger models have a very wide taxi turning radius, that is why they cannot taxi through tight turns and they end up beside the taxi track. The problem can be reduced to some extend by:
- Reducing gear contact distance between main and tail wheels
- Increasing steer angle to 90
- Increase empty_weight_yaw_MOI up to 3x
- Set [contact_points] tailwheel_lock = 0 and gear_system_type = 0
Say, is the aircraft you are using an AI Aircraft? Or do you use a normal user aircraft?
From mobile hence short
Cheers,
Martin
________________________________________ The Owl's Nest * Military Aircraft Reference * ICAO Reference * Distance Calculator * MAIW, Military AI & UKMil Reference
gsnde wrote: 12 Mar 2021, 18:25
Say, is the aircraft you are using an AI Aircraft? Or do you use a normal user aircraft?
From project were models named AI, I converted textures only for DDS standard.
hschuit wrote: 12 Mar 2021, 18:13
You could try these:
...
BINGO!
It was this! So the scenery was ok. Now I know what must be improved. Sorry for the confusion, but I just started Today learning about AI traffic.
So I'll start checking it at the finish, or maybe I'll announce here when I'm closer to the finish of the whole project and someone will check these 20 models which are for AI traffic but not quite as I can see now. Most importantly for me, that it's ok with the scenery for AI traffic. Thank you very much for help.
Cheers,
Martin
________________________________________ The Owl's Nest * Military Aircraft Reference * ICAO Reference * Distance Calculator * MAIW, Military AI & UKMil Reference
). Airport was created using ADE, I think its OK, but maybe I miss something for AI traffic?
:
I suspect that I need to verify something more in the airports themselves so as to force the AI traffic to behave properly. Of course I can only stay with static models but AI gives a lot of immersion.
