I have been getting constant core.exe's with no mods, re-installed, CCleaner, deleting everything and installing again. I don't know what to do anymore. It's never been this bad. I ride offline with nothing but the standard bikes and Victoria circuit and core.exe everytime without even finishing one lap.
Can anyone suggest something else I might be able to do?
Hi Mate sorry to hear that and don't get upset for me suggesting obvious stuff ;D just trying to help:
1. When you say you deleted everything before re-installing do you mean everything! GPBIkes Installation folder AND My documents folders (saving your licence.ini first). Make new profiles - use NOTHING from the previous install.
2. Have you modified your gpbikes.ini in any way (for example - replay length).
3. Download the Beta 8 installer yet again! And try a clean install AGAIN!
3 problems that show the same problems as you are experiencing - worth a try even for the bazzilionth time.
Have you tried installing over the top of your current install without uninstalling GPB first? That sometimes helps for some reason.
Also, did you delete the Piboso folder from your "My Documents" folder when you re-installed. That can cause problems on a fresh install if it's not deleted before the fresh install.
Taking into account what you have already stated you've tried, I cannot think of anything else right now. :-\
Hawk.
Thanks for the recommendations guys.
I think I have found the culprit and probably something I should've left alone from the beginning. It seems like its my Geforce Applications settings for GPBikes that I tried to over-ride in order to seek better GFX. I deleted core.exe entry in my Geforce Control Panel and it now seems to be fine.
Sometimes the photos you guys post look better than what my game looks :/. So thought I would give that a try.
I'd like to have the best possible settings for GPBikes, as I like having my games look very pretty and shiny. Apart from the shadows and reflections and texture lines I can put into the .ini folder. Is there anything else I can do?
Suopoib ;)
Seems like Nvidia Control Panel settings was not the culprit. GPBikes def going to be put away now for a while. Can't get around track before core.exe :/
Do you have more problems (cores) playing offline than online?
If so a few of us are having the same issues - maybe PiBoSo could escalate this problem?
I have had to make my replay buffer 400 or I get a ton of cores???
Makes no sense to me
DD
Quote from: doubledragoncc on April 03, 2016, 04:08:48 PM
I have had to make my replay buffer 400 or I get a ton of cores???
Makes no sense to me
DD
I don't know about that.... My replay buffer is set to 700 and I don't get many cores at all, "Touch Wood". Lol
Hawk.
PS: I only ride online. ;)
Imola cores trying to get on it if replay buffer is over 460, Mugello I turned it back down to 400 to be sure but it plays a part in cores for sure. It is also that cores are now happening more offline than ever and a fuckin pain. If YOU dont get cores with 700 for buffer your lucky, but it dont mean its okay for others, I think GPB is unstable and it is also different from EVERY computer and windows that are all different!!!! It sucks
DD
Quote from: doubledragoncc on April 03, 2016, 04:25:27 PM
Imola cores trying to get on it if replay buffer is over 460, Mugello I turned it back down to 400 to be sure but it plays a part in cores for sure. It is also that cores are now happening more offline than ever and a fuckin pain. If YOU dont get cores with 700 for buffer your lucky, but it dont mean its okay for others, I think GPB is unstable and it is also different from EVERY computer and windows that are all different!!!! It sucks
DD
Hopefully Piboso will be getting some good ideas as to where to start looking for these obvious instabilities.... Still no evidence that work is being done on the core.exe issues though. :-\
Hawk.
His too busy with KRP Heats that are so important!!! That said it must be a big job as its taken days.
Core crashes have not really been looked at as they seem to just get worse, not better. MXB never cored once on me!!!
DD
Have to say i have found B8 pretty good, nearly all the cores i have had are due to tiny breaks in the surface between the edge of the track and the scenery/run-off. The track tool could really do with something that checks the continuity of ride-able areas to ensure no breaks.
Quote from: h106frp on April 03, 2016, 10:55:46 PM
Have to say i have found B8 pretty good, nearly all the cores i have had are due to tiny breaks in the surface between the edge of the track and the scenery/run-off. The track tool could really do with something that checks the continuity of ride-able areas to ensure no breaks.
With the majority of the tracks being conversions from older games with many gaps between polygon surfaces a tool like you describe would be a god-send. But I'd have thought an
error-catching routine would be an easier option to allow GPB to continue running instead of crashing the code?
Hawk.
I wonder if Blenders mesh 'clean up' tools could fix the problems automatically ? It has a routine for detecting holes in a mesh and repairing them automatically.
https://www.blender.org/manual/modeling/meshes/cleanup.html#fill-holes (https://www.blender.org/manual/modeling/meshes/cleanup.html#fill-holes)
Quote from: h106frp on April 04, 2016, 03:41:46 PM
I wonder if Blenders mesh 'clean up' tools could fix the problems automatically ? It has a routine for detecting holes in a mesh and repairing them automatically.
https://www.blender.org/manual/modeling/meshes/cleanup.html#fill-holes (https://www.blender.org/manual/modeling/meshes/cleanup.html#fill-holes)
Trouble is that it's not "holes" your looking for, it's gaps in between two separate scene objects. I've not heard of a tool that can detect and close gaps as yet. It's not something that you'd usually have to worry about if they were modelled from scratch, it's usually when a track has been ripped that you end up with loads of gaps in between the scene objects, and some of the gaps can be so small that to find them all wouldn't be viable. It gets to a point were you might as well rebuild the track from scratch. :)
Hawk.
Ok, i understand the problem now - it would indeed need to be track tools or error trapping.
The blender thingy sounds like the winner here.
From Hawks description it seem the track surface and track edge are separate 3D objects butted up together. The blender tool could fix the object OK but not the seam between them, they are separate vertices with the same co-ordinates (or should be ;) ) I guess this is what causes the problem, especially on turns where they have become slightly offset, it probably only takes a tiny error to cause a problem. By default the fbx2edf tools merges vertices within 0.0001m, any greater and they are treated as separate.
In Lightwave the tool is called Merge Points(in Max it's Weld Vertices/Edges) but they only work if all the required points are actally there.
For the curious, here's a guide I wrote a while ago for Seby(who'd never used a 3d package before so it was all step-by-step) of some of the procedures I used most.
The Final Welding chapter shows the Merge Point tool in use and on pages 25 and 38 there are examples of manual welding.
https://www.dropbox.com/s/9z1nn2qv8hutzbb/Track_Editing_Guide.pdf?dl=0
We had the same kind of problems in GP500. Unwelded areas caused dark patches in the game like shadows and gaps caused instant offs and the dreaded 'invisible wall' syndrome...
...so welding was a big deal.
To show the scale of the problem on some models, a quick before-and-after of Aragon. It was obviousy built for a game where you could be a bit lax with the welding.
(http://i69.photobucket.com/albums/i68/Grooveski/GP_Bikes/Unwelded.jpg)
Welded.
(http://i69.photobucket.com/albums/i68/Grooveski/GP_Bikes/Welded.jpg)
I don't really know what to do anymore. I am getting a core.exe every lap or 2. So this game is literally useless to me. I really love the game but at this stage I don't really care if another company or someone else comes along and does it better than piboso. I just want to play a properly working game that I can enjoy. I really do hope that IOM TT game will be very good and/or that someone else really invests into making a proper bike sim.
Waiting another 8 months for changes to lap timings and name tags, and pink tyre smoke is not worth it anymore for me. And I know not everyone is getting the same core.exe crashes as everyone else, but to have a WORKING product is quite vital when trying to make money of it.
Hi dareaper,
I get a lot of core crashes too and if I am on a MOD track and hit a hole in the mesh of the track edge or whereever ther may be one then GPB crashes, it is the track and NOT GPB that is at error. Poor Hawk is doing his best to fix all the tracks as quickly as he can but it is much work.
It has come to the situation that I now OVER INSTALL beta8 once a week to stop a lot of crashes!!! That means I simply re install GPB WITHOUT removing the old copy. This is fine even if MODS are installed they stay, but if you edited your gpbikes.ini or other files, you will need to re-edit them.
It is a pain but it keeps my GPB more stable and I dont edit much in gpbikes.ini except graphics and replay buffer, just keep a copy safe and copy n paste it whe you OVER INSTALL.
DD
I tried everything DD. That is the thing. I am using Stock Bikes with Stock Track. And I still get core.exe. I must admit when using Mod Tracks the cores occur way more just when crashing and touching the line between grass and track.
I re-installed and over-installed and removed Mods and added mods. Nothing seems to work. :/.
Oh and DD, could you copy and paste your entries you have in gpbikes.ini please? I also just changed textures and shadows and replay buffer AFTER you guys suggested it with no success.
MXBikes works for hours on end with no core.exe's.
we need good track makers not bad ones. and when track is released and has core.exe crash dont released it..piboso dont put it on your record list!!!i mean if you want to make a track make it properly!!!if its not the game it is the track makers!
HA.............
I did an overinstall and never re edited my gpbike ini file dude it is standard lol.
I will do it and post here lol. I will test it before posting
DD
What happens for track modders when they try their track and they don't have corexe?
They get a bag of gummi bears Jana lol
People need to understand GPB is unstable and what works on one computer may NOT work on another, real simple.
DD
Quote from: -aGy- on April 19, 2016, 11:28:04 AM
we need good track makers not bad ones. and when track is released and has core.exe crash dont released it..piboso dont put it on your record list!!!i mean if you want to make a track make it properly!!!if its not the game it is the track makers!
It's not just problems with tracks that cause core.exe issues..... ::)
Plus most of the tracks are still work-in-progress(WIP); track modders are not employed by Piboso to create tracks for GPB and can only work on them when time allows in their spare times. As a result of this tracks are often left not updated for long periods of time, but they are in a useable state.... Some are good and should not be an issue towards the Core.exe problem. But you have to understand that they are still in WIP status for most of them.
Asking Piboso not to release them? Lol........ Piboso has nothing to do with what community trackmods are released; that is up to us, the community, to organise.
Bottom line is - Do you want a good selection of tracks in the database that are useable but still a work in progress, or do you want 3 or 4 tracks that we can probably say are good enough not to contribute to the core.exe issue?
For gods sake don't start taking your frustrations out on the few people who give their time and skills freely to help make GPB a better experience or we're soon going to end up with none! :o ::)
Hawk.
Hawk, SlovakiaRing is the best example of tracks needed. It has no core crash holes I can find and frame rates are great. What it lacks in prettiness it more than makes up for in rideability.
DD
Quote from: Hawk on April 19, 2016, 12:57:49 PM
Bottom line is - Do you want a good selection of tracks in the database that are useable but still a work in progress, or do you want 3 or 4 tracks that we can probably say are good enough not to contribute to the core.exe issue?
Both :)
That's why, a long ago, I proposed to group our tracks depending on their readiness/reliability. Something like :
- Perfect: track fully functional (timing, replay cameras, race data), no known issues like holes, gaps etc.
- Good: a few known issues, but usable
- WIP: work to do
- Bad: track with major issues, nobody working on it (as source files not available).
It's just a matter of creating folders on your Mega page and put the tracks inside accordingly.
I like to have plenty of tracks, including ones that are wip or bad, but we need to make very clear what is still wip/bad and can have issues from what is fully functional.
Quote from: HornetMaX on April 19, 2016, 01:12:24 PM
Quote from: Hawk on April 19, 2016, 12:57:49 PM
Bottom line is - Do you want a good selection of tracks in the database that are useable but still a work in progress, or do you want 3 or 4 tracks that we can probably say are good enough not to contribute to the core.exe issue?
Both :)
That's why, a long ago, I proposed to group our tracks depending on their readiness/reliability. Something like :
- Perfect: track fully functional (timing, replay cameras, race data), no known issues like holes, gaps etc.
- Good: a few known issues, but usable
- WIP: work to do
- Bad: track with major issues, nobody working on it (as source files not available).
It's just a matter of creating folders on your Mega page and put the tracks inside accordingly.
I like to have plenty of tracks, including ones that are wip or bad, but we need to make very clear what is still wip/bad and can have issues from what is fully functional.
Yes I agree with what you say there Max and is something I could do with the communities help(probably via polls), as what tracks don't cause a core.exe crash for me might be causing core.exe crashes for someone else, so the decision of what tracks to put in what category folders would have to go to a community poll or I'm sure to get complaints that such and such a track should be in another category folder than it currently is. :-\
Personally I don't get many core.exe crash issues(Luckily, "Touch Wood!".), so to do this just on my experience and opinion would be wrong, I'd definitely need to put the tracks to a community poll to achieve this I feel. But a good idea Max! ;) 8)
Hawk.
I agree. I get core crashes as I am not so good yet and invariably run wide or crash where you good riders dont. Most cores are off the track itself so should not be a problem but we ALL go down lol.
One question, why is a track online not giving a core crash in they same spot as if offline???
Surely I am still using my data for the track so GPB SHOULD core on and off line at the same spot????
DD
Quote from: doubledragoncc on April 19, 2016, 01:07:51 PM
Hawk, SlovakiaRing is the best example of tracks needed. It has no core crash holes I can find and frame rates are great. What it lacks in prettiness it more than makes up for in rideability.
DD
I really appreciate the compliments DD, Thank you mate. ;) 8)
But this is just another example of the totally randomness of the core.exe problems, because the SlovakiaRing track is in more a state of WIP than say Snetterton 300 and Silverstone, and yet Slovakia is obviously working very well for you, and that's great!. :)
Another problem with working on tracks is the lack of feedback from most in the community. It seems when bikes are released they get SO much feedback and yet tracks get very little feedback, almost as if tracks are the backing group to the main star performer. Lol
I know 2 or 3 people do tend to provide me with feedback when a track is released or updated and I appreciate it very much, but guys in general, if you want to contribute to better MODS then you have to provide good and more importantly, HONEST, feedback.... Don't fear appearing disrespectful of the work already done - Any decent modder will welcome criticism so long as it's constructive, and anything that could be done better is probably more down to a lack of time available than their ability to do it. So say what you want from a track. ;) 8)
Hawk.
Just use Nick's events. If a track passes the Nick's test, it's good enough to go into the "perfect" category.
We could even add a score in terms of visuals for each track, as some are pretty good but others are plain terrible (which is OK for some users, but bad for others).
To me the perfect solution would be a sticky post managed by a single person with all the tracks referenced and the two ratings (usuability and visuals).
Of the two, the usuability one is the most urgent.
Quote from: doubledragoncc on April 19, 2016, 01:30:20 PM
I agree. I get core crashes as I am not so good yet and invariably run wide or crash where you good riders dont. Most cores are off the track itself so should not be a problem but we ALL go down lol.
One question, why is a track online not giving a core crash in they same spot as if offline???
Surely I am still using my data for the track so GPB SHOULD core on and off line at the same spot????
DD
To be honest I do not know why that is..... But you'll probably find that on another day it will core.exe offline at that same spot but not online..... This is the total randomness problem about the core.exe issue that is frustrating us all I think. Lol
Hawk.
OKay, so why if Nicks events are perfect do I get cores on ALL those tracks lol. Only through holes btw.
DD
Quote from: HornetMaX on April 19, 2016, 01:43:40 PM
Just use Nick's events. If a track passes the Nick's test, it's good enough to go into the "perfect" category.
Trouble is getting the feedback from all participants to make that decision, and also the fact that most will have no cores while a few will. Also a race event is only usually supported by 8 - 18 maybe 24 competitors on occasions, hardly a true representation of the majority who use GPB as a whole? :)
Quote from: HornetMaX on April 19, 2016, 01:43:40 PM
We could even add a score in terms of visuals for each track, as some are pretty good but others are plain terrible (which is OK for some users, but bad for others).
To me the perfect solution would be a sticky post managed by a single person with all the tracks referenced and the two ratings (usuability and visuals).
Of the two, the usuability one is the most urgent.
This would be great, but something for someone else in the community to organise because I'm involved in too much work already for the time I have available. ;)
Hawk.
Quote from: Hawk on April 19, 2016, 02:04:07 PM
Quote from: HornetMaX on April 19, 2016, 01:43:40 PM
Just use Nick's events. If a track passes the Nick's test, it's good enough to go into the "perfect" category.
Trouble is getting the feedback from all participants to make that decision, and also the fact that most will have no cores while a few will. Also a race event is only usually supported by 8 - 18 maybe 24 competitors on occasions, hardly a true representation of the majority who use GPB as a whole? :)
True, but better than nothing. Also, some tracks have very clear issues, so for these one it's an easy job.
You are the trackmeister, who better than you ? :P
Come on, just a sticky post, at least with the tracks we consider as good. Probably below 20.
And you'll have the power to give the notes for the visuals, as a compensation !
Quote from: doubledragoncc on April 19, 2016, 01:30:20 PM
I agree. I get core crashes as I am not so good yet and invariably run wide or crash where you good riders dont. Most cores are off the track itself so should not be a problem but we ALL go down lol.
One question, why is a track online not giving a core crash in they same spot as if offline???
Surely I am still using my data for the track so GPB SHOULD core on and off line at the same spot????
DD
I am wondering if 'approach angle' to the gap is a factor in the variance of core. Crossing a small gap seems much less sensitive than running along the length of a gap to core.
This is a very unscientific appraisal of what i have observed in game so far.
Quote from: h106frp on April 19, 2016, 03:21:25 PM
Quote from: doubledragoncc on April 19, 2016, 01:30:20 PM
I agree. I get core crashes as I am not so good yet and invariably run wide or crash where you good riders dont. Most cores are off the track itself so should not be a problem but we ALL go down lol.
One question, why is a track online not giving a core crash in they same spot as if offline???
Surely I am still using my data for the track so GPB SHOULD core on and off line at the same spot????
DD
I am wondering if 'approach angle' to the gap is a factor in the variance of core. Crossing a small gap seems much less sensitive than running along the length of a gap to core.
This is a very unscientific appraisal of what i have observed in game so far.
Your absolutely correct I feel H..... I've done similar tests in the past for just that, and it does seem that if you hit a gap at right angle then you have a good chance of getting away with it, but if you hit a gap along it's length then there's a good chance you'll core.exe crash..... But I think also that the speed you pass over the gap can make a big difference too to whether you get away with it or not. :)
Hawk.
+1 on that guys.
Also, if the bike is tumbling and the wheels dont hit that area it just carries on to the gravel etc with no core. its possible it flew over the gap but I have had slides with no cores at places it cores if I ride on it.
DD