Search results for query: *

I think you're all way too "blinded" by your own experience on VAM haha. Timeline is kind of complex. "Automatic stuffs" well, are automatic, you're not "making" the animations. The best way to make "not complicated animations" if we're only talking about simply the thrust part would be...

I'd had two things : Written rules are nice, but since 98% of internet does not read anymore. This is probably pointless for most people as they will not go through that sort of content (from beginning to end). Knowing that you're talking about "bump", you could have that inside of that post...

Just a pose preset?

Let's take this the other way: Epic is marketing those fancy features as "console compatible" and production ready. If, your game dies upon using those features that are demoed like being able to run billions of polys... but without being even close to the demos shown. You know there's a...

hazmhox updated Studio Maestro with a new update entry: LUT Update Hotfix Read the rest of this update entry...

LUT Update Hotfix Fixed a critical bug where set loading was duplicating the subscenes Refer to the previous update post for the change list. (sorry!)

hazmhox updated Studio Maestro with a new update entry: LUT Update Read the rest of this update entry...

LUT Update Added LUT feature (handled through @MacGruber's Post Magic, thank you buddy as usual!). LUT settings are saved with the lights preset. Added new preview system featuring quality setting and overlay options Changed the right UI layout to be nicer and more in line with the new preview...

Put it at 50% speed, no sound, subtitles ;)

But if you're interested about technical jibber jabber.

Simply: Game state at release Player feedback Studios/devs feedback Internal discussions and everyday job experience + friends at other studios who are in the same deep shit trying to make that engine spew more than 30 fps on consoles when you have these features enabled :3

There's an excellent way of using VAM (and I'm doing that all the time), and it's sadly not very documented: always hard reset VAM after a scene. Don't load scenes back to back.

Stap using that old obj :p Yes fbx is fine.

I can come up with all sorts of glitchs and materials : ) I have just a lot on my plate right now lol I'll check what I can do.

Plugins that have assetbundles inside of them ( a bunch of my plugin do ). But that's hard for you to know that without checking the plugin unless you have some technical background. But the important thing is, never two different versions of the same plugin inside a single scene.

<3

Yup. Ask the creator, or give us more details. A crash like this on vammoan can imply an incorrect authoring (multiple versions of the plugin). Or your session was broken (you should have hard resetted). Any critical crash during scene load could potentially block the scene completely (and...

That's a rule of thumb: never ever mixed versions of plugins in your scenes ;)

The best "shortcut" for that is to select something and hit "F", it's the default "Focus" button of Unity (and a lot of engines editors).

The usual drill ;) Always use method one if you know a plugin handles legacy content: download, delete old versions, then hard reset. Never EVER, try to change a plugin that potentially has an assetbundle within the same scene with two different versions.