Hey i need some advice or input if this issue happens to others:
i try to paint a landscape with Speedtree Models, which works pretty good. But when selecting lasso and marking a mesh it crashes the Graphicscard and therfor the Engine. Anyone having the same issues with a gtx 680 and win7?
Is there any advice out there?
Thank you in advance!
Update: If i have an empty level and only 1 tree painted by foliage painting tool, it will be selected by the lasso. If there is a second tree the Engine drops to 10 fps and does not select it. With 3 trees painted, the engine and graphics card driver crashes immediately.
Thanks for getting me the link via the forums! I’ll start looking into this in a bit. In the mean time since you’re getting the crash can you post your DxDiag and post the crash log here?
If you are experiencing a crash, then
please provide us with the .LOG and
.DMP files from your
[project]\Saved\Logs folder.
Additionally, you can please send us
the CrashReportClient.log file located
in C:\Program Files\Unreal
Engine\4.0\Engine\Programs\CrashReportClient\Saved\Logs.
Sorry for the delay in getting back to you on this. I have in fact be able to reproduce this in 4.3 and our latest internal build.
I see where the fps drops to ~10fps when selecting or lassoing one tree object. I have a fairly powerful system so it took a few more than 3 for me to crash my video driver but I was able to reproduce this!
I’m submitting the report in the next few for this!
I’m not sure when this issue will be resolve but I will update as soon as I know anything further.
Same issue here.
UnrealEngine4.3 on: Intel i5, nVidia gForce GTX 780, 8GB Ram.
When selecting speed tree meshes placed as foliage ive got framedrop to ~2 FPS. After few seconds my video driver crashing (fresh video drivers).
I can reproduce that bug on all my computers.
For now - there is only one way to select SpeedTree static meshes on foliage using lasso from foliage editor: You have to switch view mode to Wireframe.
Then You can select as many object as You want. It works for me and for my colleague.
As a matter of fact I just got the notice today in my email that this issue has been fixed. I’ve not been able to verify it as of yet since the build it’s fixed in has not been synced up for me to test. I’ll be able to look at this on Monday morning and verify that it has in-fact been fixed!
