[WIP] CART Factor
- Thread starter zerocool
- Start date
Corti
Registered
send PM Matt21
DiggerHawk
Registered
hi
any advancements on this? I was just watching the graphic update videos and wondered the state this is inthanks anyway for trying to update these beasts
Things are still progressing; it's just taking time. Hopefully the end is now in sight. I will try to share some more progress soon.
David Short
Registered
Hi Mark
I've been following your awesome graphical updates from the start as this CART mod is by far my favorite mod. Was just wondering if you would consider releasing the cars that you have already completed and add the rest once their done. I use a reduced amount of AI to help with FPS so even having a couple of updated cars to race against would be awesome.
Of course if you want to finish them all before you release anything is totally up to you as your the one doing all the hard work. Just thought I'd ask and am very thankful that your working on it, what you have so far looks great. Thanks again.
Cheers
Dave
DiggerHawk
Registered
Hi Dave,
Thank you for your appreciation of the work so far. It may be possible to release one of the cars first, but for that to happen I would need to finish one first. At different points over the last year or so each chassis has been worked on and I am now at a point where most of the work is done on all of them but not all of the work has been done on any of them. So to put it another way, none of them are at a stage I am happy to call them completed, just yet.
I am also waiting of Traveller's updated scripts for Blender to hopefully allow the usage of normal maps, as this really adds to the aesthetics. I also keep on learning new things that then have to be implemented on all the other chassis, but in the end I think the extra work will be worth it.
Here is something just to keep you going (work in progress, Reynard liveries still original)
Storm Gang Simulation
Registered
Are you not using the Carbody IBL shader on these? I didn't think there were normal maps available in the carbody shader other than for damage. Are you using something else instead?
DiggerHawk
Registered
You are correct the only normal maps that can be used with the IBL carbody shader are for damage. The normal maps I was talking about are for the other models that make up a car. Items like the steering wheel and cockpit tub that use the IBL standard shader, which can use a normal map for extra detailing.
vava74
Registered
This looks absolutely STUNNING!!!Hi Dave,
Thank you for your appreciation of the work so far. It may be possible to release one of the cars first, but for that to happen I would need to finish one first. At different points over the last year or so each chassis has been worked on and I am now at a point where most of the work is done on all of them but not all of the work has been done on any of them. So to put it another way, none of them are at a stage I am happy to call them completed, just yet.
I am also waiting of Traveller's updated scripts for Blender to hopefully allow the usage of normal maps, as this really adds to the aesthetics. I also keep on learning new things that then have to be implemented on all the other chassis, but in the end I think the extra work will be worth it.
Here is something just to keep you going (work in progress, Reynard liveries still original)
Mitch9
Registered
isn't it possible to use s397's material editor after exporting the gmts?
DiggerHawk
Registered
I have been using the material editor to create the json material overrides, which work great. The issue is with how Traveller's scripts export the gmt's, as currently the normal map appears patchy. This is something Traveller is aware of and is looking into. His older script worked fine in this regard, so hopefully it is something that he can fix.
Mitch9
Registered
You can override the shader in the material editor too, so you dont need to export anything but a simple map at first then assign the other textures in the material editor later.
DiggerHawk
Registered
Unfortunately if you use the basic "L2DIFFUSET0" preset it will not allow the normal map to work. You need to export from blender using either the "L2BUMPT0" or "L2BUMPCMAPSPECMAPT0" presets, otherwise the necessary information is missing at the mesh level. I know this because I tried just using the "L2DIFFUSET0" preset for all my models and they all lacked working normal/bump maps in rF2, even when added using the material editor. But with the "L2BUMPT0" preset they work although currently not fully. Traveller explained "it is in the bump map support values calculation on export" that is the cause of the patchy normal maps.
This is with the latest export scripts, it may be the case in future that Traveller will make the exported GMT's support normal maps even if the most basic of shader presets are used.
DiggerHawk
Registered
The issue is definitely with the scripts and Traveller is aware of it. I think with the latest scripts he streamlined the code which stopped it working correctly. If you take the GMT exported from Blender and open and re-export it with 3dsimED3 the normal maps will work correctly. Problem is I am past my 20 day trial of 3dsimED3.
DiggerHawk
Registered
I realised I hadn't posted an update in a while, so here is a little something.
DiggerHawk
Registered
It appears to be an issue with the rF1 format engine files according to a post in another thread. It has been reported and apparently it will be looked at by S397.
vava74
Registered
Not sure if S397 will actually do anything about this, aside from confirming that this is the case.
Personally I don't think it's reasonable to expect that the rF2 code will accommodate mods which have ultra-legacy parameters on the HDV file when we all want rF2 to be come better optimised and stable...
It's a bummer, BUT, if there are clear instructions on what has to be corrected, I am sure that the community will be able to address this on a case to case scenario.
Nonetheless, I did ask on Discord if it would be possible to incorporate a new function on the MAS app to review components, parsing through the HDV files and apply an automatic correction (which I assume could be achievable).
