CookAll=True but no cooking?

uced · November 13, 2015, 7:58pm

Hey,

I seem to get troubles with the CookAll option again, see this one:

All was working fine in 4.9 after the resolution of this problem, but i just migrated in 4.10, tried to cook, and no cooking again.

This time, the CookAll option seems to be set to true correctly, but no cooking is done. This happens both with “file/package project” and “file/cook content”.

Is there some new option that i should be aware of, or is that a comeback of the 4.9 problem ?

Thanks

MrFred · November 18, 2015, 3:46pm

Hi mate,

I don’t think this has regressed the same changes are in 4.10 as in 4.9. Could you provide a log file?

Thanks

Stephen_Ellis · November 24, 2015, 7:10pm

Hi

We haven’t heard back from you in a few days, so we are going to mark this post as ‘Resolved’ for tracking purposes. If you follow up by providing a log file, we will continue our investigation.

Thanks

uced · November 25, 2015, 4:24pm

Hey MrFred, hey Stephen,

I am sorry, i missed the mail telling me about MrFred’s update, and as a workaround i moved my content into specific directories that i declared manually for cooking. This works so no emergency on my side anymore.

Anyway, for this test i deleted all cooked content (actually i deleted the whole “saved” directory) and suppressed all manually added directories in the packaging options and only checked “cook all content” with nothing else.

Here is the log, it looks correct as far as i can say (which just means: CookAll is correctly set to true), but nothing is cooked. No possible mistake about that: my project when fully cooked is about 4 Go, and after this test it’s about 400 Mo.

[link text][1]

Again, apologies for the delayed answer, please let me know if you need anything else for this issue.

Cheers

68139-yag.zip (25.6 KB)

MrFred · December 1, 2015, 10:21pm

Hi ,
It seems as though this is unrelated to the original cookall bug. The flags are there and look like they are being respected.
It should be cooking all the things in the yag/Content/ directory.
Easiest way to see what’s going on here is to step through the
UCookOnTHeFlyServer::CollectFilesToCook function
This section should return all the files in the “content” directory.

if ((FilesInPath.Num() == 0) || bCookAll)
	{
		TArray<FString> Tokens;
		Tokens.Empty(2);
		Tokens.Add(FString("*") + FPackageName::GetAssetPackageExtension());
		Tokens.Add(FString("*") + FPackageName::GetMapPackageExtension());

		uint8 PackageFilter = NORMALIZE_DefaultFlags | NORMALIZE_ExcludeEnginePackages;
		if ( bMapsOnly )
		{
			PackageFilter |= NORMALIZE_ExcludeContentPackages;
		}

		if ( bNoDev )
		{
			PackageFilter |= NORMALIZE_ExcludeDeveloperPackages;
		}

		// assume the first token is the map wildcard/pathname
		TArray<FString> Unused;
		for ( int32 TokenIndex = 0; TokenIndex < Tokens.Num(); TokenIndex++ )
		{
			TArray<FString> TokenFiles;
			if ( !NormalizePackageNames( Unused, TokenFiles, Tokens[TokenIndex], PackageFilter) )
			{
				UE_LOG(LogCook, Display, TEXT("No packages found for parameter %i: '%s'"), TokenIndex, *Tokens[TokenIndex]);
				continue;
			}

			for (int32 TokenFileIndex = 0; TokenFileIndex < TokenFiles.Num(); ++TokenFileIndex)
			{
				AddFileToCook( FilesInPath, TokenFiles[TokenFileIndex]);
			}
		}
	}

uced · December 2, 2015, 6:30am

Hey MrFred !

I put a stop point in the section (line 3459 in CookOnTheFlyServer.cpp) but when i package or cook, the cooking/packaging process goes on until the end without stopping.

So if i understood what you asked and if i did things correctly, it looks like we’re never entering this section.

Cheers

MrFred · December 2, 2015, 8:51pm

Hi ,

Are you using the launch on button to test this?

uced · December 3, 2015, 4:47pm

Hey MrFred,

I made you a short video here:

That way you know exactly what i am doing.

Please let me know if i do anything wrong or if you need anything else.

Cheers

MrFred · December 4, 2015, 3:52pm

Hey mate,

The breakpoint will not hit in this situation because when File → Package is selected it will spawn a new process to do the cooking.
Using the Launch On button will use the main UE4Editor to do the cooking.
It’s probably easier just to get the commandline from the log and put that in your UE4Editor commandline in visual studio.
It will look something like
.exe -run=cook
Copy and paste that into the commandline options of your editor in visual studio then run :).
Sorry I didn’t explain this properly the first time.

Thanks

uced · December 6, 2015, 8:11am

Hey !

I found the line in the and copy-pasted the arguments in VS (project/properties/debugging/command lines) but it did nothing.

Then i started thinking (at last !!). I am using the launcher editor, which i never recompiled and hence can’t insert any breakpoint in.

So just to be sure, are you implying from the beginning that i am using the github version of the editor or recompiling it somehow ? Because i’m not

Should i ? If yes, i’ll do it but i’ll need more time to answer your question because i have to learn how to use github.

Sorry for being the ignorant baby here, i’m learning^^

Cheers

anonymous_user_a08c0bf2 · December 10, 2015, 9:59pm

,

Yes, you will need to debug the Development Editor project. However, if your project is a code project, you will need to debug your code projects editor.