Forum Replies Created
-
AuthorPosts
-
webCustomer
Was a bit too early with writing here. Setting the outline color is working the way I described above. There was just a browser caching issue.
So for everyone who is interested in setting outline effects via JavaScript, these are the commands:
appInstance.postprocessing.outlinePass.visibleEdgeColor = new v3d.Vector4(0,0,1,1); appInstance.postprocessing.outlinePass.hiddenEdgeColor = new v3d.Vector4(0,1,0,1); appInstance.postprocessing.outlinePass.edgeStrength = 3; appInstance.postprocessing.outlinePass.edgeGlow = 0; appInstance.postprocessing.outlinePass.edgeThickness = 4; appInstance.postprocessing.outlinePass.pulsePeriod = 0;
The only thing I could figure out, is how to set “Render Hidden Edge”. Tried it this way, but doesnt seem to have any effect:
appInstance.postprocessing.outlinePass.renderHiddenEdge = false;
webCustomerThx you very much for this release. Can confirm that all material issues are gone
webCustomerAwesome
That worked! Thx heaps
webCustomer@web
Thanks, we just fixed this issue. There will be a bugfix release soon!Great
Can you give an estimate when the bugfixed version will be released?webCustomerI think there is no need to, cause its even not working with a super simple setColor puzzle
webCustomerIts the same project I’m working on as mentioned in the pre version, which I sadly cant share in public.
But I made a test scene.
There is a material called “Test”. When change the Diffuse Color of that material on runtime, you can see that the object renders white when diffuse color is higher than “#000”.
webCustomerThx for the release.
I can confirm that the last mentioned material and spline object issues are gone.
But now I got another bug, which maybe is related to exposure/light:
In my current app I’m changing the diffuse color of some objects at runtime. After re-exporting the 3d data, the object is pure white.
I tested a little bit further and could see that when the color diffuse color is set to “#000” the object renders black. But when the value is anything higher than “#000” for example “#111”. The object renders white.Also a tiny thing which should maybe mentioned in the changelog. The naming of the setColor values changed. Before the update it was “Material Diffuse Color” now it is “Material_Diffuse_Color”. Which is a good thing (underscore instead of whitespace), but I wondered why my app wasnt working in the first place after the update.
webCustomerNo problem. Glad to help out.
I already suspected that these issues relate to the new export plugin for max2021.
webCustomerThx for the new release. Can confirm that the export of my current scene with VRay is working again
Sadly there are some glitches which prevents me from updating my app to new newer version (which was working with 3.1 pre1 for 3dsMax).
– Pure spline objects gets converted into Mesh objects
– It seems that controllers/colors for materials are no longer getting exported. All my values for the materials are gone, and therefor my application doesnt work correctly anymoreEDIT:
I prepared a test scene, to see the unexpected spline conversion. And the material issue.webCustomerFor the moment I created a new material for each object. Works so far.
Just not sure if this will make the scene slow at some point, when this function is executed several times.webCustomerHere you can find an almost empty scene.
Thanks, we were able to reproduce and resolve this issue!
Great
Can’t wait to test the new release with all the improvements on my current app.Also great to see the improvements for the html events. Can you tell me if you are also working on a “proper” onclick event? Which doesnt fire when you just try to move/navigate in the scene?
webCustomerHere you can find an almost empty scene.
webCustomerSadly cant share the scene in public. I could maybe do an save with just the lights in the scene and a cube.
There are only 2 lights in the scene one VRaySun and a Standard Directional Light.
Maybe there is an issue because I’m not using the lights directly. I’m using a Daylight System. See attached screenshot:webCustomerStill cant export my scene
V3D-INFO: Exporting glTF 2.0 asset (ASCII) V3D-WARNING: Unsupported material type: VRayMtl V3D-WARNING: Unsupported map type: VRaySky -- Error occurred in anonymous codeblock; filename: C:\Users\user\Documents\verge3d\max_plugin\verge3d.ms; position: 17572; line: 460 -- MAXScript MacroScript Error Exception: -- Runtime error: Traceback (most recent call last): File "C:\Users\user\Documents\verge3d\max_plugin\__init__.py", line 94, in <exportGLTF> File "C:\Users\user\Documents\verge3d\max_plugin\__init__.py", line 141, in <exportGLTFPath> File "C:\Users\user\Documents\verge3d\max_plugin\generate.py", line 1500, in <generate> File "C:\Users\user\Documents\verge3d\max_plugin\generate.py", line 548, in <generateLights> File "C:\Users\user\Documents\verge3d\max_plugin\generate.py", line 409, in <generateLight> AttributeError: 'pymxs.MXSWrapperBase' object has no attribute 'type' -- MAXScript callstack: -- thread data: threadID:16212 -- ------------------------------------------------------ -- [stack level: 0] -- In exportGLTF(); filename: C:\Users\user\Documents\verge3d\max_plugin\verge3d.ms; position: 17573; line: 460 -- member of: StructDef:V3DManagerStruct -- Locals: -- Externals: -- owner: (V3DManagerStruct V3D_MENU_CONTEXT:1905594901 autoAssignAttrs:false settingsFile:"$userscripts/Verge3D/settings.ini" debug:false hasInitiated:true smeClock:dotNetObject:System.Windows.Forms.Timer) -- importPython: Struct member:importPython : V3DManagerStruct.importPython() -- ------------------------------------------------------ -- [stack level: 1] -- called from codeblock macroScript: Verge3D_exportGLTF; filename: C:\Users\user\Documents\verge3d\max_plugin\verge3d.ms; position: 277; line: 11 -- Locals: -- Externals: -- ------------------------------------------------------ -- [stack level: 2] -- called from top-level
webCustomerJust installed pre3 but MaxScript Export Error is still present in Max2019:
V3D-INFO: Initialize Verge3D plugin V3D-INFO: Exporting glTF 2.0 asset (ASCII) V3D-WARNING: Unsupported material type: VRayMtl V3D-WARNING: Unsupported map type: VRaySky -- Error occurred in anonymous codeblock; filename: C:\Users\user\Documents\verge3d\max_plugin\verge3d.ms; position: 16823; line: 445 -- MAXScript MacroScript Error Exception: -- Runtime error: Traceback (most recent call last): File "C:\Users\user\Documents\verge3d\max_plugin\__init__.py", line 94, in <exportGLTF> File "C:\Users\user\Documents\verge3d\max_plugin\__init__.py", line 141, in <exportGLTFPath> File "C:\Users\user\Documents\verge3d\max_plugin\generate.py", line 1498, in <generate> File "C:\Users\user\Documents\verge3d\max_plugin\generate.py", line 548, in <generateLights> File "C:\Users\user\Documents\verge3d\max_plugin\generate.py", line 409, in <generateLight> AttributeError: 'pymxs.MXSWrapperBase' object has no attribute 'type' -- MAXScript callstack: -- thread data: threadID:21512 -- ------------------------------------------------------ -- [stack level: 0] -- In exportGLTF(); filename: C:\Users\user\Documents\verge3d\max_plugin\verge3d.ms; position: 16824; line: 445 -- member of: StructDef:V3DManagerStruct -- Locals: -- Externals: -- importPython: Struct member:importPython : V3DManagerStruct.importPython() -- owner: (V3DManagerStruct V3D_MENU_CONTEXT:1905594901 autoAssignAttrs:false settingsFile:"$userscripts/Verge3D/settings.ini" debug:false hasInitiated:true smeClock:dotNetObject:System.Windows.Forms.Timer) -- ------------------------------------------------------ -- [stack level: 1] -- called from codeblock macroScript: Verge3D_exportGLTF; filename: C:\Users\user\Documents\verge3d\max_plugin\verge3d.ms; position: 277; line: 11 -- Locals: -- Externals: -- ------------------------------------------------------ -- [stack level: 2] -- called from top-level
-
AuthorPosts