I'm suspicious here, since I'm a fan of the work done by the LFT group, but I can't help but congratulate and thank the LFT for this great work; Congratulations and thank you!
Well... as I said earlier, I'm fond of and a fan of LFT work, but that doesn't mean they're perfect works; What are they? Please, I am far from criticizing such works as they are of high value to me! But, one of the things that presents itself as problems, and I've talked to ElWeon18 and he acknowledged having some bug in his BTB that generates this problem, are the walls of his circuits being transferable to the AI... well, as I find this extremely unpleasant aesthetically speaking, I try to work the AIW so that this doesn't happen anymore... Not very often, but in overtaking it becomes almost impossible to control...
Thanks for your fixed AIW! AI racing GPS has been improved significantly in it.
Thanks for the feedback; It is very important for me to know if I am getting close to good results, since I would try harder if it were the other way around. Of course, I still expect some good AIW programmers to also work better on it (AIW), since I believe they have more capable people than me who can generate more quality of performance in this AIW, without leaving the cars crashing into the walls.
I improve the route lines and limits using the AIW editor guitarmaen AIW CAM Editor 422: https://www.racedepartment.com/downloads/guitarmaen-aiw-cam-editor.54199/download
So... man, as for the conversion to GTR2, I personally don't, but maybe you should look for abrimaal here on RD; it has a job aimed at converting tracks to GTR2 and works with great quality! Present the clue to him and see if he is interested in the project; I believe this is the best way.
About the small problem with the display that I reported, as I suspected, I believe that the problem was generated when configuring the AIW in BTB; After all, I understand that it did not even go through any external editor which was eventually confirmed by the author of the clue himself. Well, and as I suspected also the conflict was being generated by one of the two; In this case, I understand that it is in Xsector 1. In fact, as I said earlier, I had never seen this problem in any other circuit and therefore had never paid much attention to the lines that demarcate the xsector 1 and 2, as well as the xfinesh... But, looking for a solution, I ended up visualizing the lines of the sectors and saw that the line that is demarcated to meet the xsector1 does not correspond to the place where the corresponding mesh object is and this is probably the generator of the conflict described. I've already changed several xsector objects of various circuits, even to fix some other type of conflict and always got good results, but now this does not occur and I can not give solution to the problem, because I believe that it can only be solved from the original by redoing it in BTB and this is a kind of non-transferable thing... I've never done that action so I don't know... but I believe that if the LFT group remakes it the conflict will disappear... even if I re-edit it in the AIW format that was made available in the download along with the track, and that is bad, I, having the sectors well demarcated, could redo the strokes and offer an even better AIW... in short, it is at the discretion of the creators of the track; I'm available to help.
Yeah, I have no problems with a conversion. Again, always keep the credits in the loading screen.
Hi. I guess that the problem it's a bug in the sector times, right? I was worried about that issue cause BTB have a bug itself. If the starting point of the track is after the sector 1 (like F.E tracks where pitlane it's in a different place, the starting grid in other and the finish in other too), the track will get that issue (even if you have GID plugin, the sectors are no separated, it's all yellow). If the sector 1 is after the starting point (like in the majority of the tracks) it will run correctly.
Well... I found a way to organize Xsector 1 that eliminates the bug, but... it's kind of a weird thing... Anyway, actually, in the training sessions, I didn't notice any bugs... The times are marking correctly in all three sectors and for me it is ok; The problem for me, as I said, is during the races, where on the stretch of the return straight the display goes crazy. Based on my observations, and with the clarification of the cause of the problem generated by BTB, I understood that, in fact, the game is even mixing the sectors xfinish and xsector1, that is, in the position in which the two sectors are, the game is confused with "thinks" that you are entering the 3rd sector (xfinish), "skipping" sector 2 (xsector2), But when we reach this sector 2 the game reorganizes itself and everything goes back to normal... anyway, hard to explain... But then what I did was put the object xsector1 after the exit curve of the sector xfinish... Any position prior to this curve that places Xsector1 the bug presents itself, even if the conflict time decreases, it does not end... So the solution I found was in that position. Well, with that I pushed xsector2 further forward because actually the best position for xsector1 now put is where xsector2 was. In this way, the bug disappeared completely and, during the race, there is no longer any problem with the display that now perfectly marks the positions of the cars that are in front and behind and its own position.
Hi! Well the solution that you mentioned of reducing the sectors 2 and 3 was what I thought. But the problem is that in the real indycar track, are not like that.
Hi ElWeon18. I already converted another track of yours (Paris e-Prix 2019) and I want to convert Nashville. I ask your permission, please. And I want to give a big congratulations to Finno Zidjian for fixing the AIW. AI's no longer collide with walls. Great job Finn! great job too, ElWeon18 !
Hi, Sergio!
Hi Finno! I see this quality in what you do and write. And that's about it...you're right. And I saw and already saved your startlight. I will use it for sure. It deserves one more congratulations for that!... I haven't put it on yet, because I'm in the first track tests. But I'm already running it. And the look of the bridge with the river below is awesome...very good. There's only one detail with the AI's: I thought they were a little slower on somes turns (90º turns). I plan to check this out in AIW. If I can improve, I'll let you know and post the file here. Greetings !
Hi, Sergio!
Hi! Thanks for your words, I'm glad that you like Finn's work on the AIW and my work. Of course you can convert it, just keep the credits of my work in the loading screen.
