Having a problem with the rain effect - Using the rain effect variation 4 (if that matters), and I'm having it follow the rider using the object position event (because nobody wants to place effects everywhere, right?), but at different camera angles the rain doesn't appear, such as the default camera angle, so now I'm having to place the effect under the rider in order for it to work. However if I do this, when the camera points downwards the rain effect will disappear again. Pretty annoying. :/
you should be able to use the glue object(manual centerpoint, glued to the effect) to create an offset so the effect always stay infront of the rider or glue a few effects together to cover a bigger area around your ridder that it followsOriginally Posted by WARTHOGSZ Go to original post
or you can use two-input datasources to create an offset
Followed one of your steps and it works now. Thanks.Originally Posted by sparkierjonesz Go to original post
Hi guys not dead sure if this should go in here but anyway
When it says you have to many physics objects in one area and things might be driven through. How does that work exactly ? does that include the already built in buildings and objects that are in the editor or do they not have physics attatched. Also what ways can you cheat this , does putting things on decorations help to reduce this or is that just a performance thing. It has said it to me before and sometimes i dont even have that many physics objects about. I was thinking if it includes objects already placed within the editor can they be hidden in the ground.
They have extended the compelxity in the last patch which is great , can they do the same for the physics objects on and a nice big moutian would be great to use , those rocks when building a face of a mountian so to speak dont look to real when huddled together..lol dont want much do i![]()
in general this error isn't a big deal, it is just a warning that things might go wrong because while in the editor the engine is struggling with giving everything a physics body (everything has one here so you could select things and the physics bubble is also bigger than normal while editing
if its just a regular track with no excesive physics going on and a regular physics bubble you shouldn't have any issues
and you have to always test properly anyway
i was once working on a mini game and got this error from just the sheer ammount of yellow coding tiles i had in the area
so its really nothing to worry about, unless you wanna do alot of physics stuff in the area
since update 3.5 there is a texture loading problem with this object:
Seed Building Parts -> Chain (Variation 1, 2, 3, 4, 5)
if i change the variation to 6 or turn the object on 180° the texture is loading. i also got some texture loading problems on ruins objects, but after a few seconds they are loading. the chain texture isnt even loading after 30 minutes.
yesterday i worked 6 hours straight on my track, the game crashed for no reason and i lost all my work ... again! (xbox one)
probably i should save more often, but 6 months after release and this important bug is still not fixed?? i dont even know why the game crashed. makes me angry.
tbh i dont care about multiplayer, teams or whatever - please just fix that and give us an auto-save option in the editor.
Dear Core2TOM, with all respect that unfortunately doesn't help much. The most important thing in the game for me is working editor. But sometimes when I encounter a crash (and the developer versions do crash quite often too, but mostly for different reasons (yours is actually more stable)) I can't see the reason for crash straight away on my screen. I need to spend sometimes many hours trying to get the crash to reproduce with certain steps 100% of the time and sometimes even debug and dig the code to find the exact cause. Otherwise there's no point reporting crashes if you have no clue how to reproduce it and even if you're 100% sure, everything is priorized and some fixes may be too risky if there's a possibility of something else breaking. Nonetheless, every reported issue is read and weighed, but hopefully you understand that the new core game and editor features are top priority now to keep the game growing.