hi all, i'm in trouble again in mod dev when i try to start the track some times it starts well, other times it doesn't start and other times it starts but it's like in the photos. I then tried to bring in game but it's the same thing(rfcmp) it could be a corrupt file or some texture, how can I intervene to understand where the problem is? is there a diagnostic system or not? thanks in advance to those who can give me some advice
ok guys, I don't want to sing victory too soon but I did several tests and now it "seems" to work both in moddev and in game, the problem "seems" the probe, maybe it is badly positioned?, the fact is that if I disable the probe "seems" to work, what do you think?
Andrea, i dont see a lot wrong with your Probe, my versions look the same. I have no spaces after comma , in probe positions I assume the // in front of IRRADIANCE_PROBE=IRRAD_GLOBAL is you disabling it. I dont believe AmbientColour is needed anymore. just my 2Ps worth, not much i know but best i can offer.
This could be because these tracks aren't adapted to DX11. We stopped publishing the updated tracks for some reasons.
yes // they are used to disable the instruction, however I can confirm that (at least after many tests) that it is the probe that gives this problem, I will try to position it in other coordinates and see what happens
Are you disabling the global probe though? It is mandatory to have a global probe Also have you converted the textures from AC to be used in rf2? With PBR the color textures need to be albedo
Have you tried it with a different car? The probe shouldn't cause that, it should just give things a different tint, unless it's placed next to something very bright maybe.
in fact with some machines it works a little better but it still freezes, the textures combined with the PBR materials have been transformed with the map converter as I have always done, I tried to move the position of the probe even in less bright areas, but at the startup keeps crashing returning to the STEAM screen, if I disable the probe everything works properly, I have no idea what's wrong
yes, I really believe that I can confirm that the probe is in conflict with this instruction: Light=Direct00 { Type=Directional Color=(210, 210, 210) Dir=(0.5, -0.9, 0.6) } if someone knows technically what it means can you explain it? however, by deactivating this instruction the probe works perfectly
I rhink that this thread is related to this https://forum.studio-397.com/index.php?threads/sun-too-bright-turning-down-possible.49735/
Andrea those settings are used in RF1 from memory. They are not used in RF2, Try just these: GroupMethod=Dynamic MaxShadowRange=(750.00) ReflectPlane=(0.000, -1.000, 0.000, 1.0) these are just examples you can adjust shadow range to your track.
