VermelGen Bugs

Bugs

Many of the bugs that exist are due to the individual browser that you are using. Perhaps the most common that you will find is that the dialog for a node will appear, you press OK and no node appears in the editor window or the browser. Invariably this is because the browser is not capable of generating that node dynamically. When you do find cases like this, please let me know so I can add it to the list that I am keeping.

PixelTextures print out wierd results into the byte array and text printout.
Clipping of nodes in tree view. This is due to some problems during the last rewrite of the ScrollPanel stuff. We decided not to fix it because we will be moving to Java 1.1 for the next release and completely rewriting this part
Color Edit dialog box is not defaulting to the values set in the text field on open.
Extrusion is only creating a default value despite what is put into the setEventIns
Changing to the Cross section view of the extrusion editor the first time that it is loaded requires that you first click on the spine button before pressing the cross-section button.
Cross-section rotation in the spine edit window sometimes causes the cross-section to get scaled so that all points are located on the origin. Seems to be random.

Billbaord dialog popping up was inconsistent. This is due to assigning the created dialog to the wrong reference. A quick fix is to modify VrmlCheck and change the lines

	if(dialog_list[VrmlTypes.Anchor] == null)
		dialog_list[VrmlTypes.Billboard] =
			new BillboardDialog(parent, screen_data, vrml_data);

	if(dialog_list[VrmlTypes.Billboard] == null)
		dialog_list[VrmlTypes.Billboard] =
			new BillboardDialog(parent, screen_data, vrml_data);

Running Under Unix: There is problems dues to the Motif implementation of Java that will not let you create a dialog box without having first created the parent window. In the beta 2 code this is a very common occurence unfortunately. Unless you feel like going through and editing quite a number of files and doing dynamic dialog creation, there is not much to do except sit and wait for beta 3 which will have all this stuff fixed. :(

Notes

Performance is a real wierd thing with the editor. We have been developing the code on a P100 and P166. Things run very nicely, the pixel and extrusion editors work well. I take it to work to run on a dual PPro 200 and the thing runs like an absolute dog. We've got no idea about why this is happening.
One thing that you may want to make sure of is that you have plenty of memory. For some reason the Netscape JVM likes to chew very large amounts of it. I have seen it running in 32MB, but if you only have 16MB forget it.
PixelTexture Editor is slow while drawing in 1:1 zoom. Again, NFI why this is happening If it is too slow for you then try changing to 2:1 or 1:2 and drawing. This seems to be a _lot_ quicker.
Cosmo Player beta 4 and/or Netscape Communicator 4. There seems to be a number of problems running these with VermelGen. PR4 just straight out crashes when VermelGen is loaded and PR3 just chewed up memory until there was nothing left and then stopped working cold.

[ The Virtual Light Company ] [ Justin Couch ] [ Bug Report ]