Verge3D 4.0 for Blender is out!

Excellent!

Hi,

One thing I’m noticing with the new update is that the names of puzzles (above the actual puzzle in the menu) when using dark mode are all in black text now so it’s very hard to read them. They used to be white.

I think this should be put back to white in order to read them.

Hi GLiFTeK,

GLiFTeK wrote:

final lesson from this post is that in init.plug files’ in the xml any <field> tags need a name now

We will fix this issue in the next minor update this or next week. Unnamed fields won’t crash your plugin blocks anymore. Still you need to correctly specify the field name, because otherwise the puzzles editor won’t understand which field to modify and will simply ignore it (will also print a relevant warning in the browser console).

In case you didn’t know that yet you can check out the xml tree for a puzzle block via the “Print Puzzle XML Tree” context menu option. More info here: https://www.soft8soft.com/docs/manual/en/puzzles/Plugins.html#init_plug_available_puzzles

GLiFTeK wrote:

One thing I’m noticing with the new update is that the names of puzzles (above the actual puzzle in the menu) when using dark mode are all in black text now so it’s very hard to read them. They used to be white.

Thanks for reporting! We’ll fix this bug in the next minor update too.

Hi Ivan,
One thing however, using my solution is causing all the other shadow fields to be ignored.
It’s happening in some plugins and not happening in some others.
take for instance this one.
everything below the first objectList is empty without a shadow field now (thus missing recommended settings for users)

<block type="GLIFTEK_GEOMETRY_Extrude_Geometry">
        <value name="objInput">
            <shadow type="objectList">
                <field name="FIELDNAME1<none></field>
            </shadow>
        </value>
        <value name="nameInput">
            <shadow type="text">
                <field name="TEXT1">_myExtrudedObject</field>
            </shadow>
        </value>
        <value name="segmentInput">
            <shadow type="math_number">
                <field name="NUM1">4</field>
            </shadow>
        </value>
        <value name="depthScaleInput">
            <shadow type="math_number">
                <field name="NUM2">50</field>
            </shadow>
        </value>
        <value name="sideMatInput">
            <shadow type="materialList">
                <field name="FIELDNAME2"><none></field>
            </shadow>
        </value>
        <value name="frontAndBackMatInput">
            <shadow type="materialList">
                <field name="FIELDNAME3"><none></field>
            </shadow>
        </value>
        <value name="bevelThicknessInput">
            <shadow type="math_number">
                <field name="NUM3">5</field>
            </shadow>
        </value>
        <value name="bevelSizeInput">
            <shadow type="math_number">
                <field name="NUM4">5</field>
            </shadow>
        </value>
        <value name="bevelOffsetInput">
            <shadow type="math_number">
                <field name="NUM5">0</field>
            </shadow>
        </value>
        <value name="bevelSegmentsInput">
            <shadow type="math_number">
                <field name="NUM6">5</field>
            </shadow>
        </value>
    </block>

any ideas? will this be fixed with the update as well? same problem maybe?

thanks

Ciao a Tutti
volevo segnalare che in console vengono visualizzati errori riferiti a procedure che però sono disattivate

Yuri Kovelenov wrote:

Texture compression is intended to reduce video memory footprint

agree, it works
.ktx2 vs .jpg

one more problem: the picture in 4.0.0 looks foggy and faded. in 3.9.1 colors looked more rich (just compare two pictures below)… is it really necessary to activate ToneMapping when activating MSAA x16?

visually it seems that the HDR rendering is active by default (AA "Auto") regardless of the option "Use HDR rendering" and colors look normal, but when any of post-processing methods turns active (AA "MSAA x16", for example), the HDR rendering turns on/off according to this option

p.s. ToneMapping can be deactivated and the colors will be nearly the same they were in 3.9.1…
app.postprocessing.toneMapPass.material.toneMapped = false;
or the app should be re-exported with “Use HDR Rendering” option. this also helps…

switching between rendering off/rendering on looks strange )))
https://v3d.net/8ll
re-exporting with “Use HDR Rendering” checked removes this flickering effect…