119 replies to this topic

[leon_90]

ACHIM KRAFT, on Sep 01 2016 - 03:55 AM, said:

- did this update change and/or remove trackside objects (special i ask for differences from the original papy-version)  or the pit-barrier ?

- did this update (if object changes are in, work with the original-track from papy for online racing ?

Hi Achim! Sorry for the late reply, it's always a nightmare here with no notification system in

1) yes it does for realism sake, in a different way depending whether you play the CanAm 66 version or the F1 67 one

2) I must admit that I don't know.. never play online, so never tested it.

[ACHIM KRAFT]

Hi Leon !


Many thanks for the first answer to my questions.


Greetings

Achim

[tjc]

Hi leon,

Firstly I must say a big thank you to you and the other contributors for this update to Mosport. It looks amazing and has given the track a new lease of life for me. (And many others too I`m sure)

I know I`m late to the party here, I`ve been away from sim racing for quite some time.

I seem to have a bit of a problem though.

Coming over the hump after the back straight I`m getting some kind of graphical corruption. The car I`m driving seems to "disappear" for a second, then comes back. I`ve tried with various cars. Sometimes it happens, sometimes it doesn`t. Sometimes it happens with the AI, sometimes it doesn`t. It obviously makes driving a lap nearly impossible...

Here are some screens of what`s happening.

 1.png   1013.84K   72 downloads

 2.png   791.42K   74 downloads

 3.png   915.64K   65 downloads

 4.png   1MB   58 downloads

 5.png   942.74K   55 downloads

It also happens in "Chase" cam but no need for more screens, the first ones show the problem.

This all happens in just a second as I`ve said.

Going through the thread I noticed that Pete Gaimari had some kind of problem that a re-download seemed to fix but nobody else seems to have had any problems.

Sorry that my first post about the track contains a problem but just wondering if you know what may be causing this.

Thanks again for the update though, hopefully I can get it working.

tj

[gliebzeit]

"Coming over the hump after the back straight I`m getting some kind of graphical corruption. The car I`m driving seems to "disappear" for a second, then comes back. I`ve tried with various cars. "

That is a known 'glitch' with this update.  There is no easy way to remedy the issue.

[tjc]

gliebzeit, on Sep 15 2018 - 11:20 AM, said:

"Coming over the hump after the back straight I`m getting some kind of graphical corruption. The car I`m driving seems to "disappear" for a second, then comes back. I`ve tried with various cars. "

That is a known 'glitch' with this update.  There is no easy way to remedy the issue.

That`s a real shame as it`s a really lovely update and I`m sure a ton of work has gone into it.

When you say "no easy" way to remedy it... makes me think there is a way but it would also be a ton of work to do or I guess it would have been done by leon or another talented person that knows how to do these thigs.

Thanks for the reply Greg. Pity it can`t be fixed up though.

[dario]

AI behaves very strange using sportscars extra mod and F2 mod

For example. Both Mirages are truddling around the track at 1:32 while Parkes in Ferrari goes as low as 1:16 but crashes every other lap. And continues around at the same pace untill he crashes again and ends up on roof.

Edited by dario, Dec 05 2019 - 02:33 AM.

[leon_90]

Never touched the AI for this track. All of the lp files shipped with this update are the original Papy one, while the track.ini contains only minor fixes, none of which related to the AI. In any case, there are both a generic track.ini and a 66 CanAm one, so nothing that would interfere with the XSC mod or the F2.

Edited by leon_90, Dec 05 2019 - 12:13 PM.

[dario]

Maybe my original papyrus files are corrupted. It happened with zandvoort. driver.ini was corrupted and AI behaved strangley. And someone posted his driver ini on forums and with that driver ini it worked perfectly

So maybe that is the case in Mosport too
Can you Please post driver.ini that you are using. Thank you

[leon_90]

I do not have specific track driver.inis in any of my tracks, I always run generic grids

Edited by leon_90, Dec 06 2019 - 06:35 AM.

[dario]

Could it be that my track ini is corrupt!?

[leon_90]

Try mine, see if it helps

Attached Files

•  track.ini   4.36K   5 downloads

[dario]

unfortunately even with your track ini it is still the same
The field qualifies between 1:37 and 1:50
and in the race some of them are going 1:21 and crashing all the time

[dario]

Also with 65 mod
Field qualifies between 1:42 and 1:48 (I did easily 1:30)
Than I let the race run without me. And it was won by Innes Ireland !?

Something is wrong

[dario]

Original (1967) is fine
Field qualifies between 1:21 and 1:26
And in the race front runners are Lotuses at 1:22

[dario]

Can Am 66 is also fine
field qualifies between 1:23 and 1:30
And runs normally in the race without abnormal laptimes, and wierd crashes

So Sportscars and 65 are malfunctioning
Original and Can Am 66 are fine

Can we draw some conclusion from this?

[Ramoats]

What rasterizer are you using ?

[dario]

Ramoats, on Dec 10 2019 - 04:57 PM, said:

What rasterizer are you using ?

I can not remember
How can I check what rasterizer I am using?

[Pavel]

Rasterizer does nothing here. AI performance controled  by four files: appropriative gpl_ai.ini, driver.ini, track.ini and lp files. If in mosport track folder you don't have SC mod specefic track or driver ini files but only stock track.ini then problem should be with general SC driver ini or with mod appropriative gpl_ai.ini. This two files are in GPL root folder.

[Ramoats]

I had remembered some time back they issued a 60fpsaiv1 rasterizer .... (https://srmz.racesimcentral.net/inde...?showtopic=4402)  ... I just thought that maybe it might impact his situation if he were using it.. apparently it involved ai ride height though ... sorry .....

Edited by Ramoats, Dec 11 2019 - 07:59 AM.

[dario]

Pavel, on Dec 11 2019 - 05:04 AM, said:

Rasterizer does nothing here. AI performance controled  by four files: appropriative gpl_ai.ini, driver.ini, track.ini and lp files. If in mosport track folder you don't have SC mod specefic track or driver ini files but only stock track.ini then problem should be with general SC driver ini or with mod appropriative gpl_ai.ini. This two files are in GPL root folder.

But general SC driver ini works fine on other tracks. For example in osterreich ring that too does not have SC driver ini

I also took SC driver ini from daytona and placed it in Mosport folder and AI went 10+ off the pace again. While with that same driver ini they go normally in daytona.