https://drive.google.com/file/d/0B5ctW4QlgobdYTdwRFNTZXhLaGc/view?usp=sharing (https://drive.google.com/file/d/0B5ctW4QlgobdYTdwRFNTZXhLaGc/view?usp=sharing)
updated 07/04 v0.2
@DD feel free to host it on track database
Converted but need help - team testing indicates some can run it easily and others struggle to load it.
Looking to see if its worth continuing.
If you could try the test model and report your experience with system details then much appreciated.
Model is full track with textures
No shading on this versions compile (would take to long for a test build)
Long press bike reset is troublesome
with my system i get 100 fps i5/8GB/GTX1050ti 6GB at 2.5k res/win7 64bit
Thanks for the help :)
Update 23/10
OK, strictly WIP but just to test
https://drive.google.com/file/d/0B5ctW4QlgobdQUpOVVNnVjZsNTQ/view?usp=sharing (https://drive.google.com/file/d/0B5ctW4QlgobdQUpOVVNnVjZsNTQ/view?usp=sharing)
Unfortunately, since my computer broke, I've been stuck with a piece of shit, 32bit, 2.8Ghz Dual Core, 3.5GB RAM, Windows 7 Home Edition computer... with a single GTX 770.
So, I can get the track to load, but it takes AGES, and once it loads up, it crashes GP Bikes. It's a high quality track, but texture quality, sadly needs to be reduced :'(
EDIT: OK, I'm 100% sure it isn't a texture quality issue. Something else is wrong.
Thanks for the feedback, all helps in trying to identify the root cause problem. It is a great track if you can get it to run on you system.
It loads normally on my laptop
i5-4200m 2.5GHz, GeForce GT720m, 8GB Ram, Win 10, 64-bit
I tested with the WSBK 2015 Ducati, the track seemed to run fine at 60fps for a few minutes, after that I would get a massive drop for a couple seconds (1-2 fps) and further 10 seconds of 40fps followed by 60fps again. This seemed to be time triggered rather than a specific sport on the track because I've done a couple laps and it happened at steady intervals, in random places.
When I tried to reset the bike by holding the reset, I was put half a lap back by Aremberg twice.
Oh, and there seems to be a bit of texture missing on the inside of mini carousel, it was pure white both times I went by.
Other than that, the track looks and rides great. It feels just wide enough and flows nicely with no super slow corners in there.
Thanks miki :)
I will check that texture section - I think its concrete IRL on the inside but could do with a bit of colour to bring the texture out.
Goddamnit, I hope I'm not the only one who can't run it :'(. Jesus. h106frp PLEASE do your best to ensure the track runs on most systems. PLEASE! Lol.
@miki: Have you made any custom changes to GP Bike's settings? I've set texture_quality to 1 in the gpbikes.ini, and have everything maxed out, but that's it. I've tried reducing all graphics settings as well as removing the "texture_quality" command, but the same issue remains. The track won't work.
Compared to the AC version the track feels a bit too narrow, or the bikes in GP bikes are too big ;)
For me it runs without any problems. 130+ fps troughout the whole track on max graphic settings on a gtx 780, a i7 3700k @ 4.5 ghz and 16gb . No problems loading aswell.
This is by far the best version of the ring we`ve ever had in GP bikes. Keep up the great work!
@UrbanChaos I've got the texture quality 1 and everything maxed out
Instant crash for me before reaching the track (on the "syncing" page).
Tried to lower graphics, replay size, texture quality, no plugin, close anything else. Always crash.
i5-2500K @4.4Ghz, GTX970, 16GB ram, win7 x64.
First total crash to Max :)
Strange, very similar spec to my machine ???
This is what the inside of mini carousel looks like to me
(http://i.imgur.com/W3UL6jdh.jpg)
Quote from: JamoZ on April 06, 2017, 10:58:06 PM
Compared to the AC version the track feels a bit too narrow, or the bikes in GP bikes are too big ;)
For me it runs without any problems. 130+ fps troughout the whole track on max graphic settings on a gtx 780, a i7 3700k @ 4.5 ghz and 16gb . No problems loading aswell.
This is by far the best version of the ring we`ve ever had in GP bikes. Keep up the great work!
Track centreline is within 50m (in 21850m) so a simple 'scale up' would not work, i do wonder if the elevated position compared to a car makes it appear narrower. The track is the AC one before the official AC laserscan version as far as i know
I did spot the white texture :) and you can see it in Bing maps as well, but agreed it neds a more convincing colour :) On the to do list
Quote from: h106frp on April 06, 2017, 11:04:08 PM
First total crash to Max :)
Strange, very similar spec to my machine ???
Hmm recently I've been experiencing more crashes than usual, almost all of them at sturtup/going to track (some of them when I have Visual Studio 2015 open, as soon as I close it, all goes OK).
I also have troubles using Manu's Fuji, seems to be related to memory (weird).
Maybe it's just windows going rotten and needing a reinstall :)
Very confused still, similar to what we had with CAWS team, hardware spec level does not appear to be the root cause problem.
The inside looks like the rest of the track in this on-board, have they redone the surface recently?
https://youtu.be/BjeXN1ljdUA?t=7m40s (https://youtu.be/BjeXN1ljdUA?t=7m40s)
https://www.google.co.uk/maps/place/N%C3%BCrburgring/@50.3579269,6.9805827,329m/data=!3m1!1e3!4m5!3m4!1s0x47bfad369010c559:0x80dbc21b73ca589a!8m2!3d50.3340981!4d6.9426625 (https://www.google.co.uk/maps/place/N%C3%BCrburgring/@50.3579269,6.9805827,329m/data=!3m1!1e3!4m5!3m4!1s0x47bfad369010c559:0x80dbc21b73ca589a!8m2!3d50.3340981!4d6.9426625)
Not sure what it is but agreed its too bright and plain - looks like a drainage modification. Don't worry it can be fixed if we can resolve the bigger issue of getting it to run for everyone.
Another GTX970 owner here :) The specs are similar enough to Max'
The track takes long enough to load, then for several second the mouse is lagging hard. Then, after getting on the track, everything lags again for a bit, and finally everything seems to be loaded. The framerate appears to fluctuate wildly, sometimes hitting several hundreds fps, sometimes sinking down to 30 or maybe worse, but at a very rapid rate. The end result feels like 30 or 40. With VSync on everything gets a little bit better. I will bring the view distance down from 3 km and see if it helps :)
I suppose that the track hits the 970's "proper memory" 3 GB limit, after which it starts "cheating" and underperforms, that's why the 1050 with 6 GB homogeneous (I hope?) memory on board performs better in this case.
As for the track itself, it's the dream coming true :) Never expected to try the laser-scanned version in GPB, to be honest, but it's finally happened :D Biggest thanks for this attempt!
Had to switch the new buggy view mode off, but it was worth the trouble. It's a laser-scanned Nordschleife, after all :)
Quote from: passerBy on April 07, 2017, 04:34:24 AM
I suppose that the track hits the 970's "proper memory" 3 GB limit, after which it starts "cheating" and underperforms, that's why the 1050 with 6 GB homogeneous (I hope?) memory on board performs better in this case.
I'd need to test a bit bit but I'm not under the impression the problem comes from the 3.5GB limitation.
I'm sure we have plenty of people with GPU's with less than 3GB and some do not seem to have the problem.
Maybe worth a dedicated post ? [I'l ldo one to ask PiBoSo some basic logging from GPB so that we at least know roughly where it crashes]
Quote from: passerBy on April 07, 2017, 04:34:24 AM
Another GTX970 owner here :) The specs are similar enough to Max'
The track takes long enough to load, then for several second the mouse is lagging hard. Then, after getting on the track, everything lags again for a bit, and finally everything seems to be loaded. The framerate appears to fluctuate wildly, sometimes hitting several hundreds fps, sometimes sinking down to 30 or maybe worse, but at a very rapid rate. The end result feels like 30 or 40. With VSync on everything gets a little bit better. I will bring the view distance down from 3 km and see if it helps :)
I suppose that the track hits the 970's "proper memory" 3 GB limit, after which it starts "cheating" and underperforms, that's why the 1050 with 6 GB homogeneous (I hope?) memory on board performs better in this case.
As for the track itself, it's the dream coming true :) Never expected to try the laser-scanned version in GPB, to be honest, but it's finally happened :D Biggest thanks for this attempt!
Had to switch the new buggy view mode off, but it was worth the trouble. It's a laser-scanned Nordschleife, after all :)
Sorry to disappoint but this is not the the laserscan version - its the previous one which I think is a hack from RF + many mods.
Unless we can work out the reasons for the performance variance i think we are already hitting limits and its only half the length we would need for a full IOMTT track with acceptable scenery.
I am going to have an experiment with the texture format - the textures are not as big as you might think but there is some scope to experiment with the structure.
Quote from: HornetMaX on April 07, 2017, 06:27:35 AM
I'd need to test a bit bit but I'm not under the impression the problem comes from the 3.5GB limitation.
I'm sure we have plenty of people with GPU's with less than 3GB and some do not seem to have the problem.
Maybe worth a dedicated post ? [I'l ldo one to ask PiBoSo some basic logging from GPB so that we at least know roughly where it crashes]
The GPUs with no slower memory region would probably try to take on only as much graphical data as needed (at the expense of the visual fidelity). 970 tries hard to be taken for a proper 4 GB card, but when the whole memory gets stuffed, it starts to choke on the data. Or so I think :)
For me it doesn't crash, but the frame rate fluctuations are extreme both in the frequency and the amplitude. Still, usable enough.
Quote from: h106frp on April 07, 2017, 07:24:20 AM
Sorry to disappoint but this is not the the laserscan version - its the previous one which I think is a hack from RF + many mods.
Unless we can work out the reasons for the performance variance i think we are already hitting limits and its only half the length we would need for a full IOMTT track with acceptable scenery.
I am going to have an experiment with the texture format - the textures are not as big as you might think but there is some scope to experiment with the structure.
That's really disappointing, to be honest. AC in itself was a complete waste of money for me. I hoped I could make at least some use of it. Either way, this is still the best Nordschleife for GPB we have currently.
We might very well be hitting those limits indeed. After all, the alternative view mode seem to only have issues with the longer tracks. Might be related somehow.
Quote from: passerBy on April 07, 2017, 09:12:22 AM
The GPUs with no slower memory region would probably try to take on only as much graphical data as needed (at the expense of the visual fidelity). 970 tries hard to be taken for a proper 4 GB card, but when the whole memory gets stuffed, it starts to choke on the data. Or so I think :)
Hmm ... a bit far fetched, choking due to the slow 0.5GB seems to matter for only a a few % of the fps in other games.
Quote from: passerBy on April 07, 2017, 09:12:22 AM
After all, the alternative view mode seem to only have issues with the longer tracks. Might be related somehow.
The "view=1" in "[mode]" ? What problems exactly ?
I see no particular reason why it would have an issue with longer tracks.
Quote from: HornetMaX on April 07, 2017, 11:02:49 AM
Quote from: passerBy on April 07, 2017, 09:12:22 AM
The GPUs with no slower memory region would probably try to take on only as much graphical data as needed (at the expense of the visual fidelity). 970 tries hard to be taken for a proper 4 GB card, but when the whole memory gets stuffed, it starts to choke on the data. Or so I think :)
Hmm ... a bit far fetched, choking due to the slow 0.5GB seems to matter for only a a few % of the fps in other games.
Well, it's not just a problem of losing some fps, the framerate seems to oscillate like crazy for me. In a split second it can go through a 30 to 300 cycle or so. Mostly seems to stay around 120, but it feels like 40 instead. I think I saw a similar behavior from the unit once the 3.5 GB threshold was crossed before.
QuoteQuote from: passerBy on April 07, 2017, 09:12:22 AM
After all, the alternative view mode seem to only have issues with the longer tracks. Might be related somehow.
The "view=1" in "[mode]" ? What problems exactly ?
I see no particular reason why it would have an issue with longer tracks.
I see no reason for that either, but ever since I switched to view=1, all the hell broke loose for me with longer tracks. I had to switch FFB off, for I had a really nasty ~10 Hz low amplitude noise introduced into it (some of it was even picked up at a standstill), but the view in both "cockpit cams" was equally jittery (I think, mostly in the yaw axis). The 3rd person camera was fine, but I can't even ride in that view, nor have I any inclination to learn to.
So, I had to change it to view=0. Now everything's fine and I can start enjoying the most interesting tracks all over again.
Quote from: passerBy on April 07, 2017, 05:35:51 PM
I see no reason for that either, but ever since I switched to view=1, all the hell broke loose for me with longer tracks. I had to switch FFB off, for I had a really nasty ~10 Hz low amplitude noise introduced into it (some of it was even picked up at a standstill), but the view in both "cockpit cams" was equally jittery (I think, mostly in the yaw axis). The 3rd person camera was fine, but I can't even ride in that view, nor have I any inclination to learn to.
So, I had to change it to view=0. Now everything's fine and I can start enjoying the most interesting tracks all over again.
You mean that bike standing still, mode=1 --> 10Hz FFB noise, switch to mode=0 --> no noise ?
That's worth a bug report, documented if you can. Once again, it just shouldn't happen.
Quote from: HornetMaX on April 07, 2017, 08:07:00 PM
Quote from: passerBy on April 07, 2017, 05:35:51 PM
I see no reason for that either, but ever since I switched to view=1, all the hell broke loose for me with longer tracks. I had to switch FFB off, for I had a really nasty ~10 Hz low amplitude noise introduced into it (some of it was even picked up at a standstill), but the view in both "cockpit cams" was equally jittery (I think, mostly in the yaw axis). The 3rd person camera was fine, but I can't even ride in that view, nor have I any inclination to learn to.
So, I had to change it to view=0. Now everything's fine and I can start enjoying the most interesting tracks all over again.
You mean that bike standing still, mode=1 --> 10Hz FFB noise, switch to mode=0 --> no noise ?
That's worth a bug report, documented if you can. Once again, it just shouldn't happen.
Rather, some unwarranted, non-regular noise with the bike standing, then switching to more regular noise with similar amplitude going on at about 10 Hz after starting to roll. And yes, mode=0 cures that.
I will make a bug report later.
We might just be upgrading to the laserscan version if luck holds out ;)
That would be awesome
Quote from: h106frp on April 08, 2017, 10:08:16 PM
We might just be upgrading to the laserscan version if luck holds out ;)
Crossing my fingers for that :)
...I've been getting into this track lately and it's very ridable, even with the big bikes.
would be nice to have some "sprint" races there in the future.
is there something you can do about the incorrect respawn positions and the replay crash?
Thank you for that track! Works perfectly!
OMFG..........................
How did I miss this track..............................baby daddies home at last
Thank you so much love it
Will host it asap on database and race coming soon!!!
DD
I just tried it on first person view vith view mode=1. It's barely unrideable. It shakes all the time like a parkinson !
I did it 1st person was fine for me, sure your not on the old one Takeme baby? ;D
DD
I get fps issues with this track. Between 15 and 1. I already lowered my settings and use the LAA hack.
Quote from: tchemi on August 18, 2017, 07:29:27 PM
I just tried it on first person view vith view mode=1. It's barely unrideable. It shakes all the time like a parkinson !
For me it only does that when riding at walking speed, so it's not that criticial IMO (of course still very annoying).
I am waiting for the next beta which hopefully fixes the track compiling issues (transparent objects) before doing any more track work. If the new beta is OK we may see a significant improvement to Nordy ;)
Quote from: vini97 on August 18, 2017, 08:54:26 PM
Quote from: tchemi on August 18, 2017, 07:29:27 PM
I just tried it on first person view vith view mode=1. It's barely unrideable. It shakes all the time like a parkinson !
For me it only does that when riding at walking speed, so it's not that criticial IMO (of course still very annoying).
This.
In mode=1 does the same in all tracks, some worse than others , like in Nordschleife, even Victoria does. Pretty annoying indeed but.....
Quote from: Warlock on August 28, 2017, 01:37:17 PM
Quote from: vini97 on August 18, 2017, 08:54:26 PM
Quote from: tchemi on August 18, 2017, 07:29:27 PM
I just tried it on first person view vith view mode=1. It's barely unrideable. It shakes all the time like a parkinson !
For me it only does that when riding at walking speed, so it's not that criticial IMO (of course still very annoying).
This.
In mode=1 does the same in all tracks, some worse than others , like in Nordschleife, even Victoria does. Pretty annoying indeed but.....
Yeah, old news but no comments from Pib since the new view came out:
Quote from: HornetMaX on February 22, 2017, 11:47:26 PM
Result: I find the new view lovely. Seriously lovely. Fuckin' lovely in fact. I absolutely love the way it behaves when you have an head-shake: if it's moderate (wobble), you only see the bike shaking, but if it becomes more serious (weave), the view shakes too. Just perfect.
I'm finding the behaviour in case of wheeling more tolerable, so yeah, i't may be just a matter of getting accustomed to this.
I still think there's some filtering to apply (wouldn't know where though, either on the ground reference or on the sight pitch movement): in some low-speed turns in which the bike is seriously leaning there seems to be some sort of high-freq vibration in the sight. There's a chance this may be due to poor track surface as the track is pretty old (don't know, maybe Hawk can check this out), but I'd tend to say that the onboard view should work reasonable even with a poor surface. If somebody can try the same I'd like to hear your feedback.
...so what's the plan now that beta12 is out? :P
imo the track is fine as it is if it weren't for the bugs.
Still no updated track tools or exporter though.
The intention is to move to the improved full laserscan version which has a much better track surface and visuals, most of thee work is done, just need the tools for a reliable compile to finish it off.
sounds great!
regarding the current version, am I the only one having problems with the replay? i see that the tsc file contains a full camset but it doesn't work for me in-game (cam stays in the sky).
also is the respawn bug caused by the game or is there something you can do about that?
The respawn should be fixable in tracked by generating new reset lines
Hi,
Track impossible to ride on.
It takes a long time to load and when arrive to the menu it keep black during 1 or 2 minutes and when menu appears with normal color the fps keep 0.00, so it's impossible to launch the track because the mouse cursor doesn't move because FPS = 0.
I use LAA Hack
My spec:
win7 pro 64bits
intel core quad 2.83GHz
8Go RAM
Geforce GTX 960
Thank you
any updates? :P
Added a link at bottom of first posting
awesome, thanks!
The new LS version is way better framerate wise.
(on AMD FX4300, 8GBram, AMD 260X)
Looking forward to trying this because it wasnt working before.. Getting 2fps..
AMD 4.2 cpu
Gtx 670
16g ram
the track loads fine in testing mode but whenever i try to open a server, my game crashes.
could anybody else open up a server?
setting one up for ssp600 and r6 cup bike to test if it runs
can you include the MotoGP bikes please?
i can will restart
thanks
myself i cant get in, it cores on syncing, tried several different bikes everytime the same.
i'll test it in a minute. still have to update a few mods.
Core.exe for me all the time.... :-(
@ H:
[testing session]
Testing it loads fine fps around 19 when loading.
In game for me runs smooth most of the time fps 166 sometimes short shoot outs from 160 to 180 fps.
[race]
On loading it shows an fps of 166 for me then CPU usage goes up by like 20% and ram shoots from approximately 4 too 8 GB ram (50% of my system)
then it cores while it syncing.
I use GPB with LAA hack, and the server we use is also using the LAA hack
Was there more you would like too know H ?
What is the core.exe process RAM usage ?
If it hits 4GB then we will have a problem, even with LAA :(
as a reference I get 1.8 gig in standalone mode
I am trying at the moment too record the ram usage of GPB when loading.
It seems not happy with me ALT_Tabbing too desktop too have a look at processor monitor.
I can record it while it is syncing but when it core.exe's it also crashes my graphics drivers which recover afterwards.
Happens everytime, is there a nifty prgram that stays on top of game screen displaying the usage info?
Using Rainmeter now, but it does not display on top of GPB.
There are surely others, but if I recall correctly MSI Afterburner allows to log all sort of data (GPU and CPU load/memory/temps etc) to a file and it can also show it in the overlay.
ill try that Max ta very much, i saw it online but thought i give rainmeter a go first.
If you just need it once, probably MSI afterburner is a bit too much (it does plenty of other stuff). HWinfo should work too (at least for logging, not sure it has an overlay).
If you have a second screen, it's very easy to monitor any load on your gpu, cpu and what else.
I can do it later today.
Quote from: h106frp on October 23, 2017, 09:20:32 PM
What is the core.exe process RAM usage ?
If it hits 4GB then we will have a problem, even with LAA :(
as a reference I get 1.8 gig in standalone mode
About 1.7 gb in testing mode, when joining the server it cores at about 3.8gb.
It has nothing to do with both gpu and cpu usage.
yep sounds about right boeren thank you.
But now the question...why it works in testing mode and not in server mode ?
Far from sure it's the reason, but online your client has to load all the server's bikes, not only your own bike (as in testing/offline mode).
Bit if no ones is in it yet is it then not the same as atesting session? Or does it hold the bike models in memory for the classes supported by the server?
Which would make sence for this... if you core, then you also stay in the server so to speak at least for some while.
I always wait until i am dropped from the server befeore i reconnect/sync again. Works faster reconnecting.
Just restarted the test server with only 1 class which holds 1 bikemodel and i got in, so it seems to be the number of bikes thats causing it or tiping it over its limits
How to get into a server with Nord_LS_NDS running test:
What Works sofar...
- 1 class GP600, 1 bike model
- 1 class Street, 2 bike models
- 2 classes GP600/R6 Cup, 2 bike models
What NOT Works
- 2 classes GP600/Street, 3 bike models
- 3 classes R6 Cup/GP600/Rookies17, 3 bikemodels
Server is running now with the Street class ( 2 bike models ) if some would be so kind to try and get in please.
And let me know if you succeeded or not or that you where with more then one person in the server.
i'm on the server with the kit bike.
no problems.
edit: oops, ODE error after catching some air at schwedenkreuz.