Weird glitches in 1.1 unreal editor
I've finished setting up the tools for 1.1 mod dev, but when I open the .uproject (after integrating wwise, and compiling the project on VS) I get a small warning and no matter what I do the editor then goes crazy (see screenshots)
Solution:
Caused by an nvidia option (MFAA)
see: https://forums.unrealengine.com/t/black-screen-weird-acting-of-ue-5-flickering/569292/5...
Setting up dependencies errors
I get this error while building the engine, if i skip i get the same error with another file and so on.
Can't add Widget Blueprint Hooks in SML3.11 dev
Since the recent
dev branch update to SML 3.11, I can't seem to select "Widget Blueprint Hook Data" when adding a new Widget Blueprint Hook to my Game Instance. The only option shown is None. Editing existing ones also seems to only show None, although all hooks are still working if I don't edit them.
I didn't think the new Hook changes affected Widget Hooks, and I can't find any mention of them changing in the upgrade docs (other than the note about Inline templates)....Solution:
Locally changing line 107 of
WidgetBlueprintHookManager.h back to:
...and it's showing in the editor again. I'll populate it and see if it works....
first mod help
Need help how I can make the mod from the model
As I can now say this is input gas output and power connection and so on...
Example for a custom Particle System VFX?
I'm trying to add a new rifle ammo type. I based it off a Shatter Rebar (inherited from it) and put it inside of a Rifle. It works, but there's a visual issue: pellet traces are being drawn not from a rifle's muzzle but from a pioneer's right ear. I can enable my rifle ammo for the rebar gun too and there it draws traces from the muzzle. So the issue is with the weapon model then? But what could it be? Both the Rebar Gun and the Rifle have
muzzle socket in their meshes. Traces VFX doesn't use that socket, apparently.
Then i tried to bind to Event Play Effects, which receives an array of hit results for each of the pellets. Hit results have fields (among others) Location, TraceStart and TraceEnd. I had an idea to edit TraceStart before calling the parent function, but i discovered that the parent function doesn't use TraceStart. It uses TraceEnd for the end point of a trace VFX and Location for the dust VFX at the impact point, but not TraceStart (or any other field from the hit result). So i have no idea what it uses as a start point and i can't control it because it doesn't take it from the input array.
So then i decided to create my own VFX and play that in EventPlayEffects instead of calling the parent function. But that's where i'm stuck currently. I watched a couple of Niagara tutorials and made a test particle system, but i don't see any visuals when i spawn it in the game. Muzzle flash VFX isn't even a Niagara particle system, it's a legacy Cascade system, so i'm not sure if i should use Cascade too or if i should use Niagara....Solution:
I'm cooked, nevermind. Niagara works, just like cascade. I was trying to use the wrong variable.
FGBuildable Lightweight
Most of my FGBuildable are Lightweight.
But I couldn't figure out which AccessTransformer to use to access the BuildingMeshProxy, so I added a FGColoredInstanceMeshProxy, and it works fine.
Except it generates warning and error lines in debug mode.
How can I fix this?
...
