I am having a similar issue to a thread with a similar heading. I have a project with 11 levels and I am running a matinee in each. Not all the levels have landscape in them but many have some small scale landscape. When I make a level my current level and click on the landscape tab it recognises the tab but it acts as if there is no landscape to edit and my option is to create a new landscape (even though there is a landscape in the level). The other items like are greyed out (sculpt and paint). If I deselect and click back on the landscape tab it crashes. I was working in with landscape earlier and it was working fine.
As far as how these landscape was created, it was all created in Unreal 4 with the sculpt tools and no imported heightmaps. As for the level, it is a relatively simple in that we load a level and fly the matinee camera to the end of the level, load the next level and matinee camera and do this with all 11 levels with various animations made in matinee but nothing complex. This is a VR Oculus experience so there is an orientation reset for the player at each level but that is about as heavy of a blueprint there is at this point.
Update: This happens when I have my main persistent level open with all my 11 maps. If I select the level by itself and I want to edit the landscape with the tab it appears to work without a crash. This obviously makes the work flow difficult because I cannot see my lighting but it may work for now.
Can you post a copy of the callstack, crashlogs (\Unreal Projects\PROJECTNAME\saved\logs), and your dxdiag here so I can take a look at them? Additionally, does this occur on a clean, blank project with no additional content or is this limited to one project?
Thanks for the reply. I will try to get that for you this week if possible. We are on a tight turnaround for this project so had to work around this and been truck’in since. I want to say we didn’t set up anything crazy that any work flow would have in this situation but maybe the log will say otherwise
so having worked in game development over the past 15 years the classic “well it’s working now” comes into play. this is now working without crash when i do the same as above. i am in charge of working in the persistent level so i have other folks working on their levels so i’m going to try and see what changes or updates they have done since i noted the crashes. i have notices similar issues with my students that i teach so i am going to try and duplicate this in another non-work project and report back to you when i can.
I know exactly what you mean! I’m happy to hear that this is now working correctly for you. I’m going to mark this question for tracking purposes. If you manage to reproduce it and find a series of steps I can take to reproduce this, please post it here and I’ll be happy to take a look.
well i got it to happen again unfortunately today. i’ll work around it but i did capture the log. i cannot post that here due to the project file names being sensitive of the project. if you have a epic email i could send it along later or offline
Hi ,
I will need to get permission from my current team to do this since I am a contractor for this project. Didn’t want to give the impression that I was leaving this out to dry
That is perfectly understandable. For now I will mark this as answered for tracking purposes. If you are able to get permission and post the project I’ll be happy to take a look.
