Skip to content

VectorEffects#2577

Open
yaRnMcDonuts wants to merge 16 commits intomasterfrom
yaRnMcDonuts-vectoreffects
Open

VectorEffects#2577
yaRnMcDonuts wants to merge 16 commits intomasterfrom
yaRnMcDonuts-vectoreffects

Conversation

@yaRnMcDonuts
Copy link
Member

@yaRnMcDonuts yaRnMcDonuts commented Dec 27, 2025

Adds a simple but highly reusable AppState that runs effects directly on a valid Vector type object (being Vector2f, Vector3f, Vector4f, and ColorRGBA).

Useful for lights, particle effects, and essentially every Color or Vector based MaterialParamater that shaders and special effects rely on.

The most useful functionality of this system will be the ability to quickly deploy an EaseVectorEffect on colors to smoothly fade in/out things like lights and special effects, as to avoid the sudden and unsightly impact of removing something from the scene instantaneously in one single frame. This type of smooth fading is a very important aspect of polishing a game. And while the code to fade out colors can be simple, it is something that is used over and over again for a variety of different effects in a project and can sometimes requires some not-so-simple extra bells and whistles (like a delay timer or chaining), thus a versatile system like this becomes necessary to handle this in an efficient way.

In addition to smooth fading, this library also enables a variety of other compound loopable effects by using the SequencedVectorEffect class (such as flickering, pulsing, oscillating, etc), and I also will be adding a NoiseVectorEffect class soon as well.

@yaRnMcDonuts yaRnMcDonuts added the Feature Request / Proposal Request a feature or propose an idea label Dec 27, 2025
@yaRnMcDonuts yaRnMcDonuts added this to the v3.10.0 milestone Dec 27, 2025
@yaRnMcDonuts
Copy link
Member Author

yaRnMcDonuts commented Jan 4, 2026

In order to add the NoiseVectorEffect, I also will have to add a procedural noise library to the engine.

The best choice for a fully-fledged noise library in java would appear to be the JNoise library, however I believe that would be overkill for basic noise functions that are needed for this PR, so instead I am choosing to implement the java FastNoiseLite library into the engine. This is a very light weight single class noise library that should be more suited to include in the engine than something like JNoise. Let me know if anyone disagrees or prefers a different noise library, otherwise I will move forward with this plan to include FastNoiseLite.java in the engine's math package. I also will update this PR to include javadoc before merging.

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

🖼️ Screenshot tests have failed.

The purpose of these tests is to ensure that changes introduced in this PR don't break visual features. They are visual unit tests.

📄 Where to find the report:

  • Go to the (failed run) > Summary > Artifacts > screenshot-test-report
  • Download the zip and open jme3-screenshot-tests/build/reports/ScreenshotDiffReport.html

⚠️ If you didn't expect to change anything visual:
Fix your changes so the screenshot tests pass.

If you did mean to change things:
Review the replacement images in jme3-screenshot-tests/build/changed-images to make sure they really are improvements and then replace and commit the replacement images at jme3-screenshot-tests/src/test/resources.

If you are creating entirely new tests:
Find the new images in jme3-screenshot-tests/build/changed-images and commit the new images at jme3-screenshot-tests/src/test/resources.

Note; it is very important that the committed reference images are created on the build pipeline, locally created images are not reliable. Similarly tests will fail locally but you can look at the report to check they are "visually similar".

See https://github.com/jMonkeyEngine/jmonkeyengine/blob/master/jme3-screenshot-tests/README.md for more information

Contact @richardTingle (aka richtea) for guidance if required

@yaRnMcDonuts
Copy link
Member Author

yaRnMcDonuts commented Jan 5, 2026

I re-ran the jobs and this time the screenshot tests passed. I guess something must have bugged out during the first run.

@richardTingle
Copy link
Member

Yeah, that's decidedly weird. I can't see why it decided to post that (especially not 2 hours ago). Hopefully just something bugging out as you say

@yaRnMcDonuts
Copy link
Member Author

yaRnMcDonuts commented Jan 26, 2026

I just need to upload the final example for the noise effect and then I'll merge this PR. I will wait atleast another day since no one else reviewed.

However, I've done some thorough self-review, also using AI analysis tools to critique my code and the approach. And I'm very confident that this is the best way to handle these types of effects, as opposed to hard coding things like fading and flickering into the shaders or java classes for lights, emitters, and custom shader effects.

Copy link
Member

@riccardobl riccardobl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did an initial review, there are few issues, and effects have a bit too many internal clones and allocations.
I suggest to use TempVars with the try-with-resource statement

@yaRnMcDonuts
Copy link
Member Author

I believe I've addressed all of the requests brought up in the previous review. But I'll wait another few days just in case anyone still sees any issues or anything I missed.

Then (once I'm sure there are no more changes) I will do a final update to this PR to fix all of the formatting and add javadoc, and then I'll also wait another few days after that before merging.

*/
public class VectorEffectManagerState extends BaseAppState {

private final ArrayList<VectorEffect> activeVectorEffects = new ArrayList();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
private final ArrayList<VectorEffect> activeVectorEffects = new ArrayList();
private final ArrayList<VectorEffect> activeVectorEffects = new ArrayList<>();

Copy link
Member Author

@yaRnMcDonuts yaRnMcDonuts Feb 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll be sure to fix this along with a few other remaining formatting issues in my final edit for formatting and javadoc.

vectorEffectManagerState.registerVectorEffect(this);
}
}
}
Copy link
Member

@riccardobl riccardobl Feb 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

convenienceRegister is never used, let's remove it,maybe, since it adds confusion.
The dev can just keep the VectorEffectManagerState around

Copy link
Member Author

@yaRnMcDonuts yaRnMcDonuts Feb 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do use this method in my own project, but I avoided it in the examples so that they can show the full way to fetch an appState for users who may be using the examples to learn from, and since I also want the examples to show that the effects rely on a manager state.

But this convenience method does reduce appstate-fetching boiler plate code in a project that registers lots of vector effects (and prevents having to keep a reference to the VectorEffectManagerState or repeatedly fetch it in classes that make multiple registries) so I'm opting to keep it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok then, lets call this registerTo and maybe make it append the VectorEffectManagerState if its not present in the stateManager

for(Runnable r : onFinishedCallbacks) {
r.run();
}
onFinishedCallbacks.clear();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it really expected that the finished callbacks are fired only once and then cleared?

Copy link
Member Author

@yaRnMcDonuts yaRnMcDonuts Feb 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll remove the clear() call in case someone wants to reuse a VectorEffect. And, in hindsight, the clear() method shouldn't even needed for cleanup since the class will automatically clean up the references when the VectorEffectManagerState cleans up the effect (assuming the user isn't holding a reference to it themselves if they are intending to reuse it)

}


public void registerRunnableOnFinish(Runnable runnable) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If clearing callbacks once they fire is the way to go, maybe this should be called differently.
Usually when you register something it fires every time the conditions are met, maybe we should call this runOnFinish(Runnable), like we have enqueue instead of eg. registerTask

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good, I'll rename the method.


}

public void registerVectorEffect(VectorEffect vectorEffect){
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
public void registerVectorEffect(VectorEffect vectorEffect){
public void playVectorEffect(VectorEffect vectorEffect){

}
}

public void cancelEffects(VectorGroup vectorObject) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we add a cancelEffect(VectorEffect) for completion?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature Request / Proposal Request a feature or propose an idea

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants