Forum
Questions, builds, help and the odd argument. The mods and guides are out front.
I feel like there's a problem with the reshade where i can't get reflections like other people's pictures. Can someone explain to me what i may need to do lol. I'm using BB's setup in this picture.
Can you post the settings for Reflections from your ReshadeConfig.ini?
It is the block that starts with [ReflectionSettings.fx]
# pixelgalaxy :
I feel like there's a problem with the reshade where i can't get reflections like other people's pictures. Can someone explain to me what i may need to do lol. I'm using BB's setup in this picture.
I think you're using matte envs just download hq envs from download section
Added 1 second later:
# pixelgalaxy :
I feel like there's a problem with the reshade where i can't get reflections like other people's pictures. Can someone explain to me what i may need to do lol. I'm using BB's setup in this picture.
I think you're using matte envs just download hq envs from download section
N3r0 wroteI think you're using matte envs
That is irrelevant in the given scenario.
The whole point of the dynamic reflections is that it replaces the environment maps used in game to a half drawn scene (missing the cars (potentially) to avoid self reflection)
I still think there is a setting that is not set properly.
Or this model has no reflection map defined in the scxs but that seems unlikely.
# amilmand :
Yes the parent of the particle source should be the map (which is in turn the parent of any car visible on the map so you should be able to get the map reference from the cars code with a getParent call).
You should only create the particle source once and keep a reference to it in the cars code, the car is notified of the map change through a setParent() call
you should override this function and recreate the particle system, and the particle effect if the car is put to another map.
On the animate block or whatever other thread you can update the previously created particle effect by its name if you have created it with a callparticleRef.setSource("particle1", new Vector3(0,1.0,0), 0.01, 0.3, new Vector3(0,4.0,0), 0.0, 1.5, 1000.0, null);subsequent calls with that name (particle1) will not create a new source but will update the properties of the already present one.
If you'd like (or you think you are stuck on something) post the vehicle code or what you created and I'm sure we can figure it out.
here is the java so you can give a look Link
Just to know that it won't work in your game because there is some codes I've created just for my game version
And I've created it on a track to test because I've tried to create it on Vehicle.java and didn't worked
Why not try into track.java instead of testtrack? so it would probably work in all of the tracks?!
Actually, thinking about it, scene should be the perfect java, as it also controls the time
making it on a track java is easier to test and my chances to corrupt all tracks are none xD
once fixed it I'm going to add it to Track.java
You need to save the name of the particle you want to update this functionality is complex enough to warrant a separate class the most basic one can be this:
public class ParticleWrapper
{
Vector particleSystems = new Vector();
Vector particleNames = new Vector();
RenderRef particleRender = null;
ParticleSystem particleRef = null;
public void AddParticle(String name,ResourceRef map, int ParticleTypeID
, Vector3 p, float rmin, float rmax, Vector3 vel,
float vmin, float vmax, float freq, float globalFreq)
{
particleRender = new RenderRef(ParticleTypeID);
particleRender.load();
particleRef = new ParticleSystem(map,particleRender,"scriptParticle");
particleRef.setSource(name, p, rmin, rmax, vel, vmin, vmax, freq, null);
particleRef.setFreq(globalFreq);
particleSystems.addElement(particleRef);
particleNames.addElement(name);
}
public void UpdateParticle(String name, Vector3 p, float rmin, float rmax,
Vector3 vel, float vmin, float vmax, float freq, float globalFreq)
{
for(int i = 0; i != particleNames.size(); i++)
{
if(particleNames.elementAt(i) == name)
{
particleSystems.elementAt(i).setSource(name, p, rmin, rmax, vel, vmin, vmax, freq, null);
particleSystems.elementAt(i).setFreq(globalFreq);
}
}
}
public void CreateOrUpdateParticle(String name,ResourceRef map, int ParticleTypeID
, Vector3 p, float rmin, float rmax, Vector3 vel,
float vmin, float vmax, float freq, float globalFreq)
{
for(int i = 0; i != particleNames.size(); i++)
{
if(particleNames.elementAt(i) == name)
{
UpdateParticle(name, p, rmin, rmax, vel, vmin, vmax, freq, globalFreq);
return;
}
}
AddParticle(name,map, ParticleTypeID, p, rmin, rmax, vel, vmin, vmax, freq, globalFreq);
}
public void CleanParticles()
{
for(int i = 0; i != particleSystems.size();++i)
{
particleSystems.elementAt(i).destroy();
}
particleSystems = new Vector();
particleNames = new Vector();
}
}
With this you can call the CreateOrUpdateParticle(..) function every time in the animate block and if you call it with a name already defined it wont create a new particle but instead move it but if the name does not belong to any particle yet it will create a new one.
This crashes for me all the time, am I the only one that's got this issue?
Well RinKK how does it crash do you have something in the error.log?
What are you doing when it crashes?
Do you have the latest patch? (LINK)
Is the crash reproducible? If so what are the steps that result in a consistent crash?
If the crash is not directly reproducible is there at least some kind of consistency? (like always in the catalogue or always when starting a race, something like this)
Did you mod it further?
Are you talking about SlrrExhaustive or the reshade modification? (I assumed SlrrExhaustive)
# amilmand :
Well RinKK how does it crash do you have something in the error.log?
What are you doing when it crashes?
Do you have the latest patch? (LINK)
Is the crash reproducible? If so what are the steps that result in a consistent crash?
If the crash is not directly reproducible is there at least some kind of consistency? (like always in the catalogue or always when starting a race, something like this)
Did you mod it further?
Are you talking about SlrrExhaustive or the reshade modification? (I assumed SlrrExhaustive)
Doesn't show anything.
Completly random.
Yes
Not really, apart from 1 crash that always happens when I try to buy full cars.
Yeah it's pretty consistent
No
Exhaustive.
There you go!
Which full car?
I'm trying to pry out info so I can reproduce the crash and fix it (or at least identify it as one of the known ones)
If you have the patch and using reshade you may have additional info in the d3d9.log (reshade dumps the last 100 script calls made (with some luck)) can you tell me the last 10 if they are there after a crash?
To be sure that the next crash will produce the log in d3d9.log please use the d3d9.dll from the current update I just uploaded a new one (the only difference is the d3d9.dll (same link as before))
How long do you play on avarege before crashing (you may run out of memory because of the extensive amount of scripts in the current version I'm working on a large patch that will mitigate that (the game only uses 4Gb so it doesnt really matter how much ram you actually have))
But it may be the newly discovered rpk slot reservation of unknown rpk references in effect :/ if it is so (we will see in the d3d9.log that the last call will be an init on a ResourceRef or a set() on a ResourceRef) that will also be fixed in the next update (though this next update will be difficult I dont really know how to push it I think I will just reupload the whole thing again because some files need to be removed, there were a lot of changes and it will brake compatibility with previous savefiles :/ and this could be discouraging (the car-save files will be incompatible but they can be made compatible only the mufflers and the wheels need to be removed and the car resaved but this is far too complicated to add as a general patch-note))
But before this patch there is still a potential crash on the followSpline() and one on system.currentTime() I didnt get to yet.
# amilmand :
Which full car?
I'm trying to pry out info so I can reproduce the crash and fix it (or at least identify it as one of the known ones)
If you have the patch and using reshade you may have additional info in the d3d9.log (reshade dumps the last 100 script calls made (with some luck)) can you tell me the last 10 if they are there after a crash?
To be sure that the next crash will produce the log in d3d9.log please use the d3d9.dll from the current update I just uploaded a new one (the only difference is the d3d9.dll (same link as before))
How long do you play on avarege before crashing (you may run out of memory because of the extensive amount of scripts in the current version I'm working on a large patch that will mitigate that (the game only uses 4Gb so it doesnt really matter how much ram you actually have))
But it may be the newly discovered rpk slot reservation of unknown rpk references in effect :/ if it is so (we will see in the d3d9.log that the last call will be an init on a ResourceRef or a set() on a ResourceRef) that will also be fixed in the next update (though this next update will be difficult I dont really know how to push it I think I will just reupload the whole thing again because some files need to be removed, there were a lot of changes and it will brake compatibility with previous savefiles :/ and this could be discouraging (the car-save files will be incompatible but they can be made compatible only the mufflers and the wheels need to be removed and the car resaved but this is far too complicated to add as a general patch-note))
But before this patch there is still a potential crash on the followSpline() and one on system.currentTime() I didnt get to yet.
Like 2 minutes and any car spawned fully that I tried in the catalog will crash my game. One I can remember for sure is the Escort. The saves are new and also the used car dealership crashes all the time aswell.
Hmm that really should not happen :/
I would be interested to know why it does.
If you have time can you try the new d3d9.dll and give me some (10 last lines) of the d3d9.log if you crash every two minutes it should not be that much of a hassle
Hey, do you think it'd be possible to make an "hammer" tool?
I mean, i think it is possible but probably it will require some fairly complex scripting.
Basically something that allows choosing the size/shape/weight of an object and energy used to dent a car with a few sliders/buttons, and would allow, by clicking on any part of the car, to dent it. Kinda like the painter tool, but instead of applying a decal, bumping the car.