User Tools

Site Tools


faq

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
faq [2024/12/11 11:45] gaetanfaq [2025/05/24 15:49] (current) barley1965
Line 7: Line 7:
 **StackOverFlow error when opening a model** **StackOverFlow error when opening a model**
  
-For big project the XL compiler requires a lot of memory. If it doesn't have enough it will throw a StackOverFlow error. Check [[:user-manual:ch01#Additional_Options|here]] to see how allocate more memory to groimp.+For big projects the XL compiler requires a lot of memory. If it doesn't have enough it will throw a StackOverFlow error. Check [[:user-manual:ch01#Additional_Options|here]] to see how allocate more memory to GroIMP.
  
  
Line 13: Line 13:
  
 During the migration from java 8 (groimp 1.5) to java 11, some packages in de.grogra.imp3d.io/ .shading/ .spectral/ .object where moved to de.grogra.gpuflux.imp3d.io/ .shading/ .spectral/ .object. During the migration from java 8 (groimp 1.5) to java 11, some packages in de.grogra.imp3d.io/ .shading/ .spectral/ .object where moved to de.grogra.gpuflux.imp3d.io/ .shading/ .spectral/ .object.
-If a project cannot be open because of this error, you should open the graph.xml file of your project with a text editor and changed the packages names. (Shouldn't happen anymore - see #18)+If a project cannot be opened because of this error, you should open the graph.xml file of your project with a text editor and changed the package names. (Shouldn't happen anymore - see #18)
  
 **Access of a final field from another method** **Access of a final field from another method**
Line 19: Line 19:
 Example: Unexpected Exception IllegalAccessError: Update to static final field <NAME OF FIELD> attempted from a different method (<NAME OF METHOD>) than the initializer method <clinit> Example: Unexpected Exception IllegalAccessError: Update to static final field <NAME OF FIELD> attempted from a different method (<NAME OF METHOD>) than the initializer method <clinit>
  
-The field (parameters) used in rgg field should follow the java encapsulation rights. +The field (parameters) used in an rgg field should follow the java encapsulation rights. 
  
 **ClassNotFound: java.utils.*** **ClassNotFound: java.utils.***
  
 Bug that happens when starting GroIMP from eclipse with a JRE 17+. Bug that happens when starting GroIMP from eclipse with a JRE 17+.
-When opening a rgg model, GroIMP load all classes required for the XL compiler to work. It is possible that some basic jdk classes are not found, especially when using newer versions of jdk (17+).  +When opening a rgg model, GroIMP loads all classes required for the XL compiler to work. It is possible that some basic jdk classes are not found, especially when using newer versions of jdk (17+).  
-You can solve this issue by selecting the "useJRT" option in groimp preferences, under RGG>Compilation options.+You can solve this issue by selecting the "useJRT" option in GroIMP preferences, under RGG>Compilation options.
faq.1733913909.txt.gz · Last modified: 2024/12/11 11:45 by gaetan