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"

Instanced static mesh building lighting issue

Hi, as stated in the title I have an issue with instanced static meshes and lighting build. I know that the thread has been opened several times but I've read all I could find without finding out anything.

Basically I've build a little actor blueprint that allows me to procedurally place some instanced meshes in the scene using a spline and controlling some basic stuff like random scale\rotation\position etc.

alt text

This blueprints creates the static mesh components via construction script, since there's no fixed number of smc that I have to use: the variety of static meshes used for actor may change based on my needs. The static mesh used, the number of instances and their transform are of course also chosen via construction script.

The actor itself only contains the spline by default. That and the Default Scene Root are both set to static, and the instanced static meshes created by the blueprint are too. Nonetheless when I build the lighting it doesn't get built for these meshes, who just retain the same lighting as a movable mesh. They cast and get only cascade shadows and therefore weight on the fpss way more than I'd like them to. Does anybody knows what the problem is? I think that maybe is the fact that I'm adding the components via blueprint so the engine in some way considers the actor to be empty. I hope so, because in that way I could just set myself a limit of say 5 different geo types per asset and then just add the components in the blueprint by myself and make the construption script only handle the instancing. But if the problem was in the instancing side i really wouldn't know what to do.

Thank you in advice and sorry for my bad english :D

Product Version: UE 4.21
domanda1.png (1.3 MB)
more ▼

asked Mar 12 '19 at 11:34 PM in Rendering

avatar image

8 2 4 4

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

1 answer: sort voted first

Ok, for anyone having the same problem. Unfortunately the only solution was to create the instanced mesh components directly by hand and not with the construction script. I also needed to move the procedural building from construction script to an in editor called function (actually I still have the CS version of the script, I'm just disabling it when I'm ok with the result). Later I will see if i may be able to destroy the unused components just to avoid having random empty components laying around.

more ▼

answered Mar 15 '19 at 07:30 PM

avatar image

8 2 4 4

avatar image RotemS Jun 20 '19 at 03:04 AM

Thanks, this solved my problem!

(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