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

Lightprobe process fails to complete quite often. #175

Closed
mitm001 opened this issue Nov 7, 2018 · 4 comments
Closed

Lightprobe process fails to complete quite often. #175

mitm001 opened this issue Nov 7, 2018 · 4 comments
Assignees

Comments

@mitm001
Copy link
Contributor

mitm001 commented Nov 7, 2018

Been trying out light probes lately and I keep having an issue where the light probe process will not complete past 73%.

Can hit refresh and the next process will complete, however, the original attachment process remains stuck at 73%.

Testing is on a 2mx2m cube with one pbr material so it shouldn't even have a problem.

@grizeldi
Copy link
Member

grizeldi commented Nov 9, 2018

Never had a problem with that, but atm light probes are a bit of a mess in the sdk. The fact that their code changes with every engine release doesn't help either.

The actual issue here could do with multithreading, since light probes create the env maps in a separate thread and maybe that thread somehow crashes or just fails to update the indicators?

@mitm001
Copy link
Contributor Author

mitm001 commented Nov 12, 2018

I am not sure at all what's going on since it just stops at 73% every time it happens. Would seem to be something other than a crash since the process requires killing to stop it. Maybe its stuck in an infinite loop.

@neph1 neph1 self-assigned this May 23, 2022
@neph1
Copy link
Contributor

neph1 commented May 26, 2022

Editor says: "Generating environment maps. Prefiltered env map face 5 generated."

java.lang.IllegalArgumentException: Cannot decrease processed workunit count (2) to lower value than before (4)
at org.netbeans.modules.progress.spi.InternalHandle.progress(InternalHandle.java:322)
at org.netbeans.api.progress.ProgressHandle.progress(ProgressHandle.java:264)
at org.netbeans.api.progress.ProgressHandle.progress(ProgressHandle.java:242)
at com.jme3.gde.core.sceneexplorer.nodes.JmeLightProbeProgressHandler.progress(JmeLightProbeProgressHandler.java:58)
at com.jme3.environment.LightProbeFactory$JobListener.progress(LightProbeFactory.java:299)
at com.jme3.environment.generation.RunnableWithProgress.progress(RunnableWithProgress.java:78)
at com.jme3.environment.generation.PrefilteredEnvMapFaceGenerator.generatePrefilteredEnvMap(PrefilteredEnvMapFaceGenerator.java:195)

@neph1
Copy link
Contributor

neph1 commented May 26, 2022

It doesn't seem to be a problem with the generation per se, rather the reporting. I have a potential fix for this, but will test a bit more.

neph1 added a commit that referenced this issue Sep 12, 2022
@neph1 neph1 closed this as completed Jan 2, 2023
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

3 participants