Shader missings and vegetation additions

[eX Software]

1. I get different shader misses. I install the latest testing version, check the cache in Steam and create a new project in another folder (not in Documents, but in C:\Games), but the "Shaders" folder doesn't appear in the editor folder at all. Very strange. I have the standard Ultra version, not Pro.

Additional requests that are terrain specific and critical to a proper workflow:

1) Fluttering vegetation shaders should be assignable in branch, bush, and grass materials, along with dynamic shadow shaders for them (like it was in Leadwerks 4.x);
2) Allow decimal values in the Density setting for vegetation layers (that was possible in Leadwerks 4.x).

[Josh]

Shaders are not stored in the program folder. They are stored in Templates/Common/Shaders. These get copied when you create a new project. Shaders are loaded from the project folder, not from the application folder.

42 minutes ago, eX Software said:

Allow decimal values in the Density setting for vegetation layers (that was possible in Leadwerks 4.x).

This is already implemented.

[Josh]

1 hour ago, eX Software said:

1. I get different shader misses. I install the latest testing version, check the cache in Steam and create a new project in another folder (not in Documents, but in C:\Games), but the "Shaders" folder doesn't appear in the editor folder at all. Very strange. I have the standard Ultra version, not Pro.

I am getting the same result if I delete the settings file before I start the program, and am creating a new project.

It is strange that you keep seeing this, though. It sounds like maybe the settings are not being saved. Does the file C:\ProgramData\Leadwerks\settings.json exist on your computer?

[Josh]

I uploaded a fix that will eliminate the missing file errors, which were caused by a world render that was being performed before any project was loaded, on the Steam version only.

The first time you start the editor it will open in the project manager, with no projects listed. Once you have created and loaded a project, when you start the editor again, it will start in the last project you had open, with the full window and four viewports.

Some of your descriptions make it sound like the settings file is not being saved, the the editor starts in the project manager each run. Is this happening?

[eX Software]

16 minutes ago, Josh said:

I am getting the same result if I delete the settings file before I start the program, and am creating a new project.

It is strange that you keep seeing this, though. It sounds like maybe the settings are not being saved. Does the file C:\ProgramData\Leadwerks\settings.json exist on your computer?

Just tried with a clean session. Yes, after updating the engine to the latest testing version and creating a new project, the settings.json file is created in ProgramDatasettings.json

[eX Software]

Strange, I restart the editor after that, and on the second launch of the editor there are no misses, everything works just fine. It seems that restarting the editor after the first launch is some kind of fix for this problem.

[Josh]

And when you start the editor, it starts with the main window with four viewports, with your last project loaded?

[eX Software]

1 minute ago, Josh said:

And when you start the editor, it starts with the main window with four viewports, with your last project loaded?

No, it opens the latest project right away. I have the latest testing version.

[Josh]

It looks like this when it starts, right?

[eX Software]

 

Just now, Josh said:

It looks like this when it starts, right?

Yes

[Josh]

Okay, if you delete your setting.json file, it should be impossible to produce the error you reported now, if you have editor build 2301 on Steam.

[Josh]

1 hour ago, eX Software said:

1) Fluttering vegetation shaders should be assignable in branch, bush, and grass materials, along with dynamic shadow shaders for them (like it was in Leadwerks 4.x);

I will probably be able to get this in soon, but this is not a bug. All other issues are resolved, I think.