tracks2013
Posted by holemad
I've let it do a long run and had the ctd too.
Already removed all objects, all cameras but problem seems to move within the track.
Also ran it without the jams, but same result.
No solution yet.
Already removed all objects, all cameras but problem seems to move within the track.
Also ran it without the jams, but same result.
No solution yet.
a problem with external camera could be the depth of the visual. the farer you see the more the game engine has to elaborate data. is there a specific place in the track where it happens? a specific moment or is all pure random?
-------------------------------
-------------------------------
if the problem is really the camera you can try to work with some of the arguments and see if they really do something. i guess their combination does lens effect like wide angle etc. i never knew what most of those values really do so i kept universlly the same values in all my tracks supposing they do something by themselves. can't exclude the high details of the track overloads the game engine.
First of all i suggest you don't remove anything. keep your testing version the same as the one publically shared so feedback and tests match both ways.
try this experiment. open one by one all the cameras and reduce the amount of Zoom In/Out on the leftside column. set them no higher than 3000/4000 if you find any big value. Save and do your testings.
Eventually, on a second run, for each camera change the arguments on the rightside column like these and see if anything changes with CTD:
unknown 1: 1024
unknown 2: 128
unknown 3: 1
unknown 4: 0
unknown 5: 0
unknown 6: 1
unknown 7: 0
Gp3 ? 1: -1
Gp3 ? 2: -1
Gp3 ? 3: -1
= the editor will transform them into 65535 on reload. that's fine.
by the way, is the gp3 2k version giving the same issues? Belini always said his tracks are done for gp3 2k, and i found it has some little diversity than gp3 1.13. even with jam id
-------------------------------
First of all i suggest you don't remove anything. keep your testing version the same as the one publically shared so feedback and tests match both ways.
try this experiment. open one by one all the cameras and reduce the amount of Zoom In/Out on the leftside column. set them no higher than 3000/4000 if you find any big value. Save and do your testings.
Eventually, on a second run, for each camera change the arguments on the rightside column like these and see if anything changes with CTD:
unknown 1: 1024
unknown 2: 128
unknown 3: 1
unknown 4: 0
unknown 5: 0
unknown 6: 1
unknown 7: 0
Gp3 ? 1: -1
Gp3 ? 2: -1
Gp3 ? 3: -1
= the editor will transform them into 65535 on reload. that's fine.by the way, is the gp3 2k version giving the same issues? Belini always said his tracks are done for gp3 2k, and i found it has some little diversity than gp3 1.13. even with jam id
-------------------------------
in gp3 2k i guess you drive the full version? does it crashes from the cockpit view while racing? or at the start of the race? that could still be the Far Sight curse
-------------------------------
-------------------------------
Verbosity means that in debug mode GpxPatch "talks" to you : it says what it is doing, and so, what makes the game crash.
The higher the verbosity is set, the more info you get on the reason of the crash.
The higher the verbosity is set, the more info you get on the reason of the crash.
I changed the left values all under 3000 : ctd after 1 lap and 2 corners
changed the right values in what rob suggested : same result but 1 lap later
no more testing for me today
changed the right values in what rob suggested : same result but 1 lap later
no more testing for me today
i'm sorry Dirk, I've put just a couple of ideas, i seem to have read it happened watching the race from the external camera but seems to be happening from cockpit, so the external camera has nothing to do with it.
you and meanmc say it happens always at the same place. do you confirm it happens only in race and not in practice/qualy? i opened the 2013 version and found turn 2 and the long straight til the hairpin full of Far Sight commands, maybe would try removing them. From menu TRACK-> Remove all OXxx Commands. Select first 0Xc5. then repeat and select 0Xc6
other than this i can suggest to call the author and ask for hints.
-------------------------------
Edited 4 time(s). Last edit at 04/29/2013 09:37PM by R_Scandura.
you and meanmc say it happens always at the same place. do you confirm it happens only in race and not in practice/qualy? i opened the 2013 version and found turn 2 and the long straight til the hairpin full of Far Sight commands, maybe would try removing them. From menu TRACK-> Remove all OXxx Commands. Select first 0Xc5. then repeat and select 0Xc6
other than this i can suggest to call the author and ask for hints.
-------------------------------
Edited 4 time(s). Last edit at 04/29/2013 09:37PM by R_Scandura.
this seems to confirm my theory that it could be a far sight problem. both in turn 2 and the long straight next to the hairpin.
these commands force to show parts of the track additional to the area already computed. so when you cross these commands you trigger the extra sections. the game has to elaborate them and if those areas are heavy detailed or crowded it's like putting a foot on a buried mine. that's why you can't pass those turns. because commands lay there.
-------------------------------
Edited 1 time(s). Last edit at 04/30/2013 02:09AM by R_Scandura.
these commands force to show parts of the track additional to the area already computed. so when you cross these commands you trigger the extra sections. the game has to elaborate them and if those areas are heavy detailed or crowded it's like putting a foot on a buried mine. that's why you can't pass those turns. because commands lay there.
-------------------------------
Edited 1 time(s). Last edit at 04/30/2013 02:09AM by R_Scandura.
sounds good! experimenting has payed 
-------------------------------
-------------------------------
Sorry, only registered users may post in this forum.