x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Office Holiday

Epic Games' offices will be on holiday from June 22nd to July 7th. During this period support will be limited. Our offices will reopen on Monday, July 8th. 

Can't save map after building lighting

Hey,

The problem

After I build lighting for my level (and it imports fine) I can't save it. It stops at 57% and then - after a while - proceeds to crash.

The circumstances

I have about 200.000 grass objects as foliage. When I remove those, lighting builds fine (and is 15 times faster!). I can not tell lightmass to disregard the grass. When the grass is not deleted beforehand, lighting building takes way longer, the results are imported to the engine fine and I can look at them. However I can't save the map.

The symptoms

First things first. Here is the log:

 [2015.01.09-11.57.31:097][273]LogWindows: === Critical error: ===
 Assertion failed: NewPosition >= 0 [File:D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.6\Engine\Source\Runtime\Core\Private\Windows\WindowsPlatformFile.cpp] [Line: 59] 
 
 
 
 KERNELBASE.dll!UnknownFunction (0x00007ffc8f2b606c) + 0 bytes [UnknownFile:0]
 UE4Editor-Core.dll!UnknownFunction (0x00007ffc6ce12f7d) + 0 bytes [UnknownFile:0]
 UE4Editor-Core.dll!UnknownFunction (0x00007ffc6cca60f8) + 0 bytes [UnknownFile:0]
 UE4Editor-Core.dll!UnknownFunction (0x00007ffc6cc89192) + 0 bytes [UnknownFile:0]
 UE4Editor-Core.dll!UnknownFunction (0x00007ffc6cdf7fe4) + 0 bytes [UnknownFile:0]
 UE4Editor-Core.dll!UnknownFunction (0x00007ffc6cbdce94) + 0 bytes [UnknownFile:0]
 UE4Editor-Core.dll!UnknownFunction (0x00007ffc6cd40569) + 0 bytes [UnknownFile:0]
 UE4Editor-CoreUObject.dll!UnknownFunction (0x00007ffc6c8b89bc) + 0 bytes [UnknownFile:0]
 UE4Editor-CoreUObject.dll!UnknownFunction (0x00007ffc6c9884c7) + 0 bytes [UnknownFile:0]
 UE4Editor-UnrealEd.dll!UnknownFunction (0x00007ffc58342c69) + 0 bytes [UnknownFile:0]
 UE4Editor-UnrealEd.dll!UnknownFunction (0x00007ffc5841117b) + 0 bytes [UnknownFile:0]
 UE4Editor-UnrealEd.dll!UnknownFunction (0x00007ffc5840df78) + 0 bytes [UnknownFile:0]
 UE4Editor-UnrealEd.dll!UnknownFunction (0x00007ffc58796180) + 0 bytes [UnknownFile:0]
 UE4Editor-UnrealEd.dll!UnknownFunction (0x00007ffc584a8f02) + 0 bytes [UnknownFile:0]
 UE4Editor-UnrealEd.dll!UnknownFunction (0x00007ffc584a7c9a) + 0 bytes [UnknownFile:0]
 UE4Editor-UnrealEd.dll!UnknownFunction (0x00007ffc584a7374) + 0 bytes [UnknownFile:0]
 UE4Editor-LevelEditor.dll!UnknownFunction (0x00007ffc5047b637) + 0 bytes [UnknownFile:0]
 UE4Editor-Slate.dll!UnknownFunction (0x00007ffc6b8efbe6) + 0 bytes [UnknownFile:0]
 UE4Editor-Slate.dll!UnknownFunction (0x00007ffc6b9d6c9d) + 0 bytes [UnknownFile:0]
 UE4Editor-Slate.dll!UnknownFunction (0x00007ffc6b95ba47) + 0 bytes [UnknownFile:0]
 UE4Editor-Slate.dll!UnknownFunction (0x00007ffc6b95d2f9) + 0 bytes [UnknownFile:0]
 UE4Editor-Slate.dll!UnknownFunction (0x00007ffc6b9be7b9) + 0 bytes [UnknownFile:0]
 UE4Editor-Slate.dll!UnknownFunction (0x00007ffc6ba64b9a) + 0 bytes [UnknownFile:0]
 UE4Editor-Slate.dll!UnknownFunction (0x00007ffc6ba90a73) + 0 bytes [UnknownFile:0]
 UE4Editor-Slate.dll!UnknownFunction (0x00007ffc6b8c97bc) + 0 bytes [UnknownFile:0]
 UE4Editor-Slate.dll!UnknownFunction (0x00007ffc6b887347) + 0 bytes [UnknownFile:0]
 UE4Editor-Slate.dll!UnknownFunction (0x00007ffc6b92b2e0) + 0 bytes [UnknownFile:0]
 UE4Editor-Slate.dll!UnknownFunction (0x00007ffc6b91c226) + 0 bytes [UnknownFile:0]
 UE4Editor-Core.dll!UnknownFunction (0x00007ffc6cd7e9e9) + 0 bytes [UnknownFile:0]
 UE4Editor-Core.dll!UnknownFunction (0x00007ffc6cd6a1fb) + 0 bytes [UnknownFile:0]
 UE4Editor-Core.dll!UnknownFunction (0x00007ffc6cd7fbbb) + 0 bytes [UnknownFile:0]
 UE4Editor-Core.dll!UnknownFunction (0x00007ffc6cd66cf2) + 0 bytes [UnknownFile:0]
 USER32.dll!UnknownFunction (0x00007ffc8f602434) + 0 bytes [UnknownFile:0]
 USER32.dll!UnknownFunction (0x00007ffc8f602297) + 0 bytes [UnknownFile:0]
 UE4Editor-Core.dll!UnknownFunction (0x00007ffc6cd80076) + 0 bytes [UnknownFile:0]
 UE4Editor.exe!FEngineLoop::Tick() (0x00007ff7d541cbda) + 8 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.6\engine\source\runtime\launch\private\launchengineloop.cpp:2193]
 UE4Editor.exe!GuardedMain() (0x00007ff7d541089f) + 0 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.6\engine\source\runtime\launch\private\launch.cpp:131]
 UE4Editor.exe!GuardedMainWrapper() (0x00007ff7d541090a) + 5 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.6\engine\source\runtime\launch\private\windows\launchwindows.cpp:126]
 UE4Editor.exe!WinMain() (0x00007ff7d541e3d9) + 17 bytes [d:\buildfarm\buildmachine_++depot+ue4-releases+4.6\engine\source\runtime\launch\private\windows\launchwindows.cpp:202]
 UE4Editor.exe!__tmainCRTStartup() (0x00007ff7d541f319) + 21 bytes [f:\dd\vctools\crt\crtw32\dllstuff\crtexe.c:618]
 KERNEL32.DLL!UnknownFunction (0x00007ffc913616ad) + 0 bytes [UnknownFile:0]
 ntdll.dll!UnknownFunction (0x00007ffc91c34409) + 0 bytes [UnknownFile:0]
 ntdll.dll!UnknownFunction (0x00007ffc91c34409) + 0 bytes [UnknownFile:0]
 
 
 [2015.01.09-11.57.31:909][273]LogExit: Executing StaticShutdownAfterError
 [2015.01.09-11.57.32:445][273]LogWindows: FPlatformMisc::RequestExit(1)
 [2015.01.09-11.57.32:446][273]Log file closed, 01/09/15 12:57:32

Another thing I noticed is this: alt text This is a screenshot taken in the "Saved" folder.

While saving the map, those files are created. One file is created, filled up until it reaches about 2GB in size and then the next begins. Once the fourth file is "full", the engine crashes. Whenever I save the map without lighting built or with lighting build, but without grass, the map takes up a size of 100MB, so maybe the issue has to do with this.

Any help is much appreciated!

Product Version: Not Selected
Tags:
temp_files.png (11.6 kB)
more ▼

asked Jan 09 '15 at 02:44 PM in Using UE4

avatar image

Deventico
209 19 20 30

avatar image Adam Davis STAFF Jan 12 '15 at 05:04 PM

Hi Deventico,

Can you post your dxdiag here so I can take a look? This can be found by going to your pc start menu and type cmd in the searchbar. Start the command prompt program and type in dxdiag. You can save this as a .txt and upload it here. Additionally do you have any distance culling set up on your foliage?

avatar image Deventico Jan 12 '15 at 06:21 PM

Hi Adam, I uploaded the DxDiag.txt as an attachment. However it caught my eye that "Intel HD Graphics 4000" is specified as Display Device. However, I have to graphics cards and the one I use for UE4 (GTX 660M) is mentioned much further down.

As for foliage: Yes, distance culling is set up for every type of foliage (trees, bushes, grass).

dxdiag.txt (92.2 kB)
avatar image Deventico Jan 12 '15 at 06:23 PM

more info:

alt text

avatar image Adam Davis STAFF Jan 12 '15 at 07:39 PM

Do you have LODs set up for all of your foliage? We added static lighting for foliage meshes in 4.6, which saw an expected spike in rendering time when foliage was used. Additionally, it would be good to double check and make sure that the engine is not using the HD 4000 and is definitely pulling its resources from the GTX 660M. I doubt this is the root cause, however it is best to double check and be certain.

avatar image Deventico Jan 12 '15 at 08:40 PM

Double checked, it is (and was) definitely running on GTX 660M.

I don't know if LOD was set up for the trees at the time. But for grass - which seems to be causing the problem - LOD is not set up.

Does Lightmass bake shadowmaps for each LOD?

avatar image Adam Davis STAFF Jan 12 '15 at 08:46 PM

No it does not, however one of my coworkers just brought up an interesting thought. Can you check your disk space on your harddrive to determine how much is available to you. We've had some users in the past who ran into a similar error and the problem was a lack of harddrive space available.

avatar image Deventico Jan 12 '15 at 08:56 PM

Ha! I thought of that as well!

My main drive has about 13GB left. So when I built the lightmaps I closely watched the status of the drive. When it crashed, the drive had about 5GB left.

While I doubt this is the cause, I'll clone the project and try building it on my other drive with more than enough space. Could take some time, however.

avatar image Deventico Jan 12 '15 at 11:59 PM

Reporting back after building lighting again:

No it is not a disk space problem. Engine crashed with 489GB free.

avatar image Adam Davis STAFF Jan 13 '15 at 04:14 PM

Ok, well that rules out the easy option!

Try opening a blank project, then adding just a few instances of foliage and build lighting, does it crash at this point or is it only when you have a large amount of foliage present?

avatar image Deventico Jan 13 '15 at 09:45 PM

I experimented a little and it only happens with large amounts of foliage. In my specific experiment: 1 landscape and about 130.000 instances of grass foliage.

I built the lightmap a few times now and it seems like the problem is connected to the .tmp-files in the "Saved" folder I mentioned in the beginning.

When I try to save the map, I can watch the file growing in size. If it stays under 2GB, it gets deleted after saving is done and everything works fine. If it keeps growing and surpasses the 2GB limit, the engine crashes and neither deletes the .tmp file nor saves the map.

avatar image Adam Davis STAFF Jan 14 '15 at 04:19 PM

Are you using 4.6.1? If so, can you try to do this on 4.7 preview. There have been some significant updates to foliage and foliage lighting in the preview.

avatar image Deventico Jan 14 '15 at 04:43 PM

Yes, I'm using 4.6.1.

I'm a student and - after three months of subscription - signed up for the student developer pack on GitHub on Dec 1st. Sadly, they've been taking their time to process the request.

Since I've still hopes for GitHub to get to my request, I'd rather avoid re-subscribing at the moment.

avatar image Adam Davis STAFF Jan 14 '15 at 08:00 PM

Have you asked one of your professors to contact github, if it is having trouble verifying your account it may help to have a professor contact them.

avatar image Deventico Jan 14 '15 at 08:25 PM

I asked GitHub the day before yesterday:

"Right now we're a bit backed up with Student Developer Pack requests so it may take some time before your educational discount request will be seen to. Have patience and we'll get to yours as soon as we can."

But back on topic: Can you reproduce the problem? Maybe if you could reproduce it, it'd make bugfinding and -fixing easier for you?

Otherwise I'm happy to test any more suggestions.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

Hi Deventico,

Ok, I tested it on 4.7 preview 3 to see if this crash occurs. Given the specs of my pc I determined to increase the amount of foliage to 560,000 to ensure that, if a crash would occur that it absolutely would happen. The machine did not crash, though it did end up using all 32gb of ram and slowed my computer to a grinding halt for long periods of time (I just got it to a point where I could move about again), but it did not crash. Given that you are working on a laptop with 12gb of RAM, I believe that the reason it is crashing is simply too much data for the machine to handle with the current foliage lighting that is in engine. My computer only lasted through the process I put it through because it has 32 gb and a gtx 750 video card, any less and it probably would have crashed from sheer data being transferred through lightmass. I would recommend drastically reducing the amount of foliage you are using to less than 130,000. If anything less than that works that is simply the physical limit of your current machine. If you absolutely must have 130,000+ foliage in your level, I would highly recommend reverting to 4.5.1 (if you have a version of your project available pre-4.6.0, as projects worked on in later builds are not backwards compatible with earlier engine versions) as static lighting did not build on foliage pre 4.6.

I did a double check and found that it was mentioned in the 4.6 release notes that the new lighting is ideal for small to medium levels, however it does not scale well with larger levels due to memory requirements, you can find more information on this here:

https://forums.unrealengine.com/showthread.php?53230-Unreal-Engine-4-6-Released!

more ▼

answered Jan 14 '15 at 09:09 PM

avatar image AlexW88 Feb 21 '15 at 12:24 PM

Hi Adam,

you mention to downgrade to a previous engine version to disallow the baking of foliage. But how does it look for the future? The current situation is definitely unacceptable for larger Projects. As mentioned in this Thread https://answers.unrealengine.com/questions/153924/turning-off-static-shadow-receiving-for-foliage.html , we need a Solution to tell lightmass to ignore specific kinds of foliage etc. Does Epic already have some internal task for this, or could you open one?

avatar image Adam Davis STAFF Feb 21 '15 at 03:04 PM

Hi AlexW88,

While I don't have any additional info currently, that is a fantastic idea and I have entered a feature request, UE-10390, to be considered by our development staff. Thank you for your request!

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question