i have found it´s not that easy. If you simply generate new lods and in the car folder is a "data" folder, they don´t get saved, you have to delete data folder, make new lods, and then it does get saved. then you can unpack the datavery simple with CM, you need to have simplygone installed, rename your actual lods (security first) then in CM click on "generate lods", dont forget to save, that' all. To modify lods i use 3dsimed but maybe other solution exists. Nice day, Mike
Thx for feedbackThe best A4 DTM in AC! Thank you for sharing!
Feedback:
The shifting animation is too fast. Try...
[SHIFT_ANIMATION]
BLEND_TIME=100
POSITIVE_TIME=290
STATIC_TIME=10
NEGATIVE_TIME=290
PRELOAD_RPM=7700
Steer Animation lock should be 360.
[STEER_ANIMATION]
NAME=steer.ksanim
LOCK=360
The Look Behind view is blocked by the rear wing.
When I tried 3dSimEd the resulting kn5 was always corrupted, with missing body, rims or other things, so I prefer not to use it.very simple with CM, you need to have simplygone installed, rename your actual lods (security first) then in CM click on "generate lods", dont forget to save, that' all. To modify lods i use 3dsimed but maybe other solution exists. Nice day, Mike
Blender adds a .nnn when one or more meshes with the same name already exist in a project. For example, if you have a mesh called "ciao" in your project and you import one with the same name, the imported one becomes "ciao.001". To avoid this problem, first delete the one you want to replace and then import the new one. Also remember one thing: blender doesn't recognize templates as unique. I mean that if you delete the car in a project and then re-import it, blender will recognize all the materials as duplicates and will add a .nnn to all the materials of the new 3D object you imported (for names, it only adds it if they are actually present in the project, even if hidden). So if you want to import new tires, delete the old ones first. Also remember another thing: when you divide a mesh into multiple parts (tab > P > by loose parts), X meshes will be created based on the number of subparts that compose it, renaming them with the .nnn method. When you go to merge them, if you want to do so, restore the name of the unified mesh because blender will give the name of the parent to the final mesh (the parent is the last selected mesh. If you merge A and B, first clicking B and then A, the final mesh will be called A). I think the problem of missing textures is due to what was said about the materials, or at least when it happens to me it's because of that. Blender adds a .001 to the imported mesh material and recognizes it as new material accordingly. When you import everything into the KsEditor the material is new and you will have to reset it. To avoid this problem either do as I said before or simply delete the new .001 material and restore the original.When I tried 3dSimEd the resulting kn5 was always corrupted, with missing body, rims or other things, so I prefer not to use it.
I've already created some LODs with Simplygon for other street cars, but this time I went for the long road using Blender, first removing the tires and rims of the 962 ST and applying the ones of the 962 LT (eventually fixing any mesh name, since Blender was adding a '.001' at its end) for every LOD, then I've loaded everything in ksEditor, loaded every persistence file and then corrected any missing textures.
I seriously don't know why is it changing the rims of an entirely different car. Maybe I'm doing something wrong in Blender?
The problem is, I've actually done what you're saying: import 962st in collection1, remove tires with rims, import 962lt in collection2, remove everything but tires and rims, put new tires and rims where the original were, using the DISK_XX as cursor and then moving the objects to that cursor, and then removing any '.001' in materials name. Then I've exported to fbx and loaded to ksEditor, loaded persistence of 962st and then persistence of 962lt, reload the textures so the editor finds them, and then readded the tires and rims textures. This, for all LODs (except LOD D for now). Have to say that I found some errors in some materials after finishing, like some transparency was gone and alpha modes reset.Blender adds a .nnn when one or more meshes with the same name already exist in a project. For example, if you have a mesh called "ciao" in your project and you import one with the same name, the imported one becomes "ciao.001". To avoid this problem, first delete the one you want to replace and then import the new one. Also remember one thing: blender doesn't recognize templates as unique. I mean that if you delete the car in a project and then re-import it, blender will recognize all the materials as duplicates and will add a .nnn to all the materials of the new 3D object you imported (for names, it only adds it if they are actually present in the project, even if hidden). So if you want to import new tires, delete the old ones first. Also remember another thing: when you divide a mesh into multiple parts (tab > P > by loose parts), X meshes will be created based on the number of subparts that compose it, renaming them with the .nnn method. When you go to merge them, if you want to do so, restore the name of the unified mesh because blender will give the name of the parent to the final mesh (the parent is the last selected mesh. If you merge A and B, first clicking B and then A, the final mesh will be called A). I think the problem of missing textures is due to what was said about the materials, or at least when it happens to me it's because of that. Blender adds a .001 to the imported mesh material and recognizes it as new material accordingly. When you import everything into the KsEditor the material is new and you will have to reset it. To avoid this problem either do as I said before or simply delete the new .001 material and restore the original.
I think the problem is at the beginning. They shouldn't be imported together, which is why you end up with a thousand .001 meshes. Try this: import the car you want to change rims on, delete its originals and save the .fbx file. Now open the car that has the rims you want and delete all the other 3D elements you don't need (select the rims, hide them and delete the rest, so you do it faster). Delete the material from the rims and save the fbx file. Reopen the first car file, import the rims you just saved and you should no longer have any problems. Even if you import them into two different collections, blender will consider each element with the same name as a duplicate. 😎The problem is, I've actually done what you're saying: import 962st in collection1, remove tires with rims, import 962lt in collection2, remove everything but tires and rims, put new tires and rims where the original were, using the DISK_XX as cursor and then moving the objects to that cursor, and then removing any '.001' in materials name. Then I've exported to fbx and loaded to ksEditor, loaded persistence of 962st and then persistence of 962lt, reload the textures so the editor finds them, and then readded the tires and rims textures. This, for all LODs (except LOD D for now). Have to say that I found some errors in some materials after finishing, like some transparency was gone and alpha modes reset.
This just because I hate those 6-spoke wheels![]()
The regular R14 is the 2008 car, and the R14+ is the 2009 car with different wing mounts, canards, etc. It's just two different years of the same car.Hi, for the Audi A4 DTM, I have 2 major concerns:
1) digital instr fonts are floating in front of the panel
2) part of the rollcage goes through my arm!
Also , what is the diff. between regular and "Plus" version ?
When I see those logs I feel like...... This is the final part of the latest crash log.
2023-11-21T13:45:52:344 [15344] | DEBUG | FSW: Monitoring: 'F:\Steam Games\SteamApps\common\assettocorsa\extension\weather\base', i.: 000001B8D04F9DC0...
Its not.you don't wanna play with the Ray-tracing effect and with the new DLSS3 support which I don't know if it is supported by the game itself or not
Sorry, but this is not true. I'm creating new LODs all the time, bc many cars dont have them. And prior of creating new LODs I always unpack data first.If you simply generate new lods and in the car folder is a "data" folder, they don´t get saved, you have to delete data folder, make new lods, and then it does get saved. then you can unpack the data
And keeping with your Egyptian theme... all this messing around trying to get a working stable setup just makes me want to lie down and fall asleep permamently like a mummified pharaoh and travel to the 'other world' which doesn't have sim racing at all. 😵💫When I see that logs I feel like...
View attachment 1305217
I wonder if anyone really knows what that unintelligible jargon means... 😶
I'll try this afternoon, thank you!🤞I think the problem is at the beginning. They shouldn't be imported together, which is why you end up with a thousand .001 meshes. Try this: import the car you want to change rims on, delete its originals and save the .fbx file. Now open the car that has the rims you want and delete all the other 3D elements you don't need (select the rims, hide them and delete the rest, so you do it faster). Delete the material from the rims and save the fbx file. Reopen the first car file, import the rims you just saved and you should no longer have any problems. Even if you import them into two different collections, blender will consider each element with the same name as a duplicate. 😎
'Chunking' might give a clue. Tried enabling/disabling 'chunks optimisation' in CSP settings? IDK.This is me right now.
Tracks that loaded just fine over recent days now crash while loading for no understandable reason. Some new tracks I've just installed, like Fenyr's Bahrain and Nukedrop's Las Vegas 2023 and Thermalito, won't load either.
This is the latest splash message I just saw, though I also get others at other times. It all seems so random!
View attachment 1305199
I'm running the latest full CSP and PURE. A few days ago, neither were causing any obvious issues. I've reinstalled both just to be sure, but that didn't solve anything.
If anyone has had recently had 'crashing during loading' issues and can suggest a fix or a good doctor who can sedate me, I'd be grateful to hear from you.
EDIT: This is the final part of the latest crash log.
2023-11-21T13:45:52:344 [15344] | DEBUG | FSW: Monitoring: 'F:\Steam Games\SteamApps\common\assettocorsa\extension\weather\base', i.: 000001B8D04F9DC0
2023-11-21T13:45:52:344 [15344] | DEBUG | FSW: Monitoring: 'F:\Steam Games\SteamApps\common\assettocorsa\extension\weather-controllers\pureCtrl static', i.: 000001B8E233A4A0
2023-11-21T13:45:52:344 [15344] | DEBUG | FSW: Monitoring: 'F:\Steam Games\SteamApps\common\assettocorsa\apps\lua', i.: 000001B8E233A3D0
2023-11-21T13:45:52:434 [16424] | WARN | No meshes found: material:garage_glass
2023-11-21T13:45:52:435 [16424] | DEBUG | Chunking meshes list: 130 meshes, out of which 35 are fixed (range is 1000 m)
2023-11-21T13:45:52:435 [16424] | DEBUG | Chunking meshes list: 35 meshes, out of which 35 are fixed (range is 1000 m)
2023-11-21T13:45:52:437 [16424] | DEBUG | Chunking meshes list: 3 meshes, out of which 3 are fixed (range is 1000 m)
2023-11-21T13:45:52:836 [16424] | ERROR | Crash! Trying to generate nice dump: 0000003FBB12D6B0
2023-11-21T13:45:52:836 [16424] | INFO | Create dump at: C:\Users\drive\AppData\Local\Temp\u3mw.0
![]()
In CM, disable the whole module where junks optimization is located and try again. If it loads, then enable it again and set everything to default. That´s the usual way of learning and solving the errors.This is me right now.
Tracks that loaded just fine over recent days now crash while loading for no understandable reason. Some new tracks I've just installed, like Fenyr's Bahrain and Nukedrop's Las Vegas 2023 and Thermalito, won't load either.
This is the latest splash message I just saw, though I also get others at other times. It all seems so random!
View attachment 1305199
I'm running the latest full CSP and PURE. A few days ago, neither were causing any obvious issues. I've reinstalled both just to be sure, but that didn't solve anything.
If anyone has had recently had 'crashing during loading' issues and can suggest a fix or a good doctor who can sedate me, I'd be grateful to hear from you.
EDIT: This is the final part of the latest crash log.
2023-11-21T13:45:52:344 [15344] | DEBUG | FSW: Monitoring: 'F:\Steam Games\SteamApps\common\assettocorsa\extension\weather\base', i.: 000001B8D04F9DC0
2023-11-21T13:45:52:344 [15344] | DEBUG | FSW: Monitoring: 'F:\Steam Games\SteamApps\common\assettocorsa\extension\weather-controllers\pureCtrl static', i.: 000001B8E233A4A0
2023-11-21T13:45:52:344 [15344] | DEBUG | FSW: Monitoring: 'F:\Steam Games\SteamApps\common\assettocorsa\apps\lua', i.: 000001B8E233A3D0
2023-11-21T13:45:52:434 [16424] | WARN | No meshes found: material:garage_glass
2023-11-21T13:45:52:435 [16424] | DEBUG | Chunking meshes list: 130 meshes, out of which 35 are fixed (range is 1000 m)
2023-11-21T13:45:52:435 [16424] | DEBUG | Chunking meshes list: 35 meshes, out of which 35 are fixed (range is 1000 m)
2023-11-21T13:45:52:437 [16424] | DEBUG | Chunking meshes list: 3 meshes, out of which 3 are fixed (range is 1000 m)
2023-11-21T13:45:52:836 [16424] | ERROR | Crash! Trying to generate nice dump: 0000003FBB12D6B0
2023-11-21T13:45:52:836 [16424] | INFO | Create dump at: C:\Users\drive\AppData\Local\Temp\u3mw.0
![]()
Thanks for the suggestion Masscot. Good tip. I'll give that a try when I get the PC out from the bottom of the swimming pool and dry it all off. 😁'Chunking' might give a clue. Tried enabling/disabling 'chunks optimisation' in CSP settings? IDK.
Probably worth reporting it on the CSP Discord, troubleshooting.
Upating Reynard Prototypes
LMP900 and LMP1's
Massive pack with nearly every Reynard-based LMP900 and LMP1
release Planned in mid to late January, after Lola B2k/10 Pack
Planned release in 2 or 3 parts
Cars
Protran RS06/H (Reynard) AER (previously Released another update, some model work)
Reynard 01Q Cosworth Nasamax Lemans (Near Complete)
Reynard 01Q Cosworth Nasamax ALMS (Not Started)
Reynard 01Q Ford Cosworth/Nicholson-McLaren (Mid Way through)
Nassamax DM139 (Reynard) Low Wing (Mid Way through)
Nassamax DM139 (Reynard) High Wing (Mid Way through)
Reynard 2KQ Chrysler (Near Complete)
Reynard 2KQ Judd (Near Complete)
Reynard 2KQ Lehmann HPT16 (Started)
Reynard 2KQ ALMS Maximum Downforce (Near Complete)
Here are the ones where the modeling is complete at least.
View attachment 1220621 View attachment 1220622
View attachment 1220623 View attachment 1220624
Just to clarify: SimTraxx have never built a single track. Ever.So we pay Simtraxx for a broken track and then pay you to fix it?
You say Simtraxx has nothing to do with it. So what is going to stop them coming after you for selling their tracks (fixed or not)?
Are you selling the whole track or just the fixes? Because if its the whole track, I can't see them taking kindly to you taking the money that they have earned by building the track.
We are still working on this. Some of the mods needs need final touches and they are good.Upating Reynard Prototypes
LMP900 and LMP1's
Massive pack with nearly every Reynard-based LMP900 and LMP1
release Planned in mid to late January, after Lola B2k/10 Pack
Planned release in 2 or 3 parts
Cars
Protran RS06/H (Reynard) AER (previously Released another update, some model work)
Reynard 01Q Cosworth Nasamax Lemans (Near Complete)
Reynard 01Q Cosworth Nasamax ALMS (Not Started)
Reynard 01Q Ford Cosworth/Nicholson-McLaren (Mid Way through)
Nassamax DM139 (Reynard) Low Wing (Mid Way through)
Nassamax DM139 (Reynard) High Wing (Mid Way through)
Reynard 2KQ Chrysler (Near Complete)
Reynard 2KQ Judd (Near Complete)
Reynard 2KQ Lehmann HPT16 (Started)
Reynard 2KQ ALMS Maximum Downforce (Near Complete)
Here are the ones where the modeling is complete at least.
View attachment 1220621 View attachment 1220622
View attachment 1220623 View attachment 1220624