Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom effek not working #25

Closed
DadamaldaDad opened this issue Sep 17, 2024 · 9 comments
Closed

Custom effek not working #25

DadamaldaDad opened this issue Sep 17, 2024 · 9 comments

Comments

@DadamaldaDad
Copy link

DadamaldaDad commented Sep 17, 2024

I have made my own smoke particles, but can't get them to work.
KubeJS assets folder:
assets.zip
KubeJS call:

AAAParticles.addParticle(ctx.block.level, 128, new ParticleEmitterInfo("aaa_particles:crucible_smoke").position(ctx.block.x+0.5, ctx.block.y+1, ctx.block.z+0.5))

This works completely fine with the aaa_particles:fire. I don't know if the fire effect has some different settings, but I created the project from scratch in Effekseer 1.70e.
I'm using mod version 1.2.2 on Forge.

I'm unsure if I have to do the ReloadListenerRegistry thing, since I use the aaa_particles namespace. I don't know how I would do that with KubeJS.

@ChloePrime
Copy link
Owner

ChloePrime commented Sep 17, 2024

new ParticleEmitterInfo() is unstable, try use ParticleEmitterInfo#create
btw can you provide latest.log?

@ChloePrime
Copy link
Owner

I have made my own smoke particles, but can't get them to work. KubeJS assets folder: assets.zip KubeJS call:

AAAParticles.addParticle(ctx.block.level, 128, new ParticleEmitterInfo("aaa_particles:crucible_smoke").position(ctx.block.x+0.5, ctx.block.y+1, ctx.block.z+0.5))

This works completely fine with the aaa_particles:fire. I don't know if the fire effect has some different settings, but I created the project from scratch in Effekseer 1.70e. I'm using mod version 1.2.2 on Forge.

I'm unsure if I have to do the ReloadListenerRegistry thing, since I use the aaa_particles namespace. I don't know how I would do that with KubeJS.

The native library version is 1.6, particles created with 1.7 will likely not work :(

@DadamaldaDad
Copy link
Author

I tried copying the fire particle as fire2, but it also didn't work. It's most likely something to do with registration. The logs don't contain anything useful and I'm currently a bit busy.

@DadamaldaDad
Copy link
Author

DadamaldaDad commented Sep 17, 2024

https://mclo.gs/89PsnEj
Works fine with lightning and fire, but doesn't work with fire2.
There is a problem with textures.

Also, please tell me which version is used specifically. I don't want to be redoing all particles.

@ChloePrime
Copy link
Owner

image
It's likely a fault of the asset loading or your asset setup.
The Effekseer core version is 1.6

@ChloePrime
Copy link
Owner

ChloePrime commented Sep 17, 2024

According to my investigation, KubeJS does not support arbitrary asset filenames.
Try use OpenLoader ?

@ChloePrime
Copy link
Owner

You can change your folder name from Texture to texture in effekseer editor and actual asset folder :)

@DadamaldaDad
Copy link
Author

DadamaldaDad commented Sep 17, 2024

Tried with Open Loader:
[16:08:20] [Render thread/ERROR] [minecraft/PathPackResources]: Invalid path aaa_particles:effeks/Texture/double-shockwave.png: Invalid segment 'Texture' in path 'effeks/Texture/double-shockwave.png'
This error message is appearing for textures of fire and lightning, not the custom ones. Otherwise same problem.

modpack_resources.zip

fire2 is just an exact copy of fire. I also want to know if Effekseer 1.62e would work or if you used an older version.

@DadamaldaDad
Copy link
Author

I zipped the pack and it started working. Weird.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants