z929669

Would you notify the author of the problem ... maybe in 'bugs' and point to your post?

Fixed all, thanks

This forum requires posting in English please (OP translated for reference). Also, use of pirated software is not tolerated.

Thanks, glad it worked out ;)

I removed the space and added a note about "SKSE" autocreation. Not sure how to stop that behavior, but it places it at bottom of the list, so not a bid deal to just leave the redundancy

I finally finished. Billboard2 looks good, but inferior to the optimized 3D statics (with 2x flat planes for trunks). However, with these trees, the specular of the trunks does not agree with the flat meshes, which do not render the specularity it seems. Using stripped-down versions of the full models as 3D statics fixed that. The full-model meshes were optimized out of the box, so no redundant triangles. This is the result (full-models are mixed with the LOD, so hopefully, it's tough to tell the diff). The only pop-in I see is the leaves and the trunks, due to the 'fixed' models of the LOD meshes I think. I do see movement of the sun on the LOD, but there is still a diff. LOD transitions are pretty damn good though.

@sheson Scoured the doc but was unable to find any explicit definitions for mesh rules Static LOD8 and Static LOD16. What happens if one sets Static LOD8 at LOD4 mesh rule for example? Seems invalid, but it's available from the context menu.

The UI font size is perfect for me, so I've never tried. I don't see an INI setting for font size, but it could be coded under [Geometry]

I never pack MO mods as archives. I just Create Empty Mod and move all files into that. Then it's just the uncompressed mod ... this is how most mods install as well, but maybe that's configurable to package into archives, IHDK. I suppose archiving is good for saving disk space, but does add another error factor

Thanks for the confirmations! I think I know what to tweak test now for billboards. Back to the 3D statics ...

I've stepped away from working on 3D statics, since I'm having mesh issues still. So I am testing Billboards now. I have defined both Billboard and Billboard2 in ..\textures\Terrain\LODGen\Skyrim.esm\ ... one TXT file defines all. Names like: TreeAspen01_0006A9E6.txt TreeAspen01_0006A9E6.dds (Billboard) - according to logs, mesh rules using 'Billboard' DO NOT use this texture but rather the next one TreeAspen01_0006A9E6_1.dds (Billboard2; front view; identical to #2) - according to logs, mesh rules using 'Billboard' use this texture and not the previous TreeAspen01_0006A9E6_1_n.dds (Billboard2; front view; created using xNormal as described in doc) - no idea if it's used TreeAspen01_0006A9E_2.dds (Billboard2; side view) - no idea if it's used TreeAspen01_0006A9E_2_n.dds (Billboard2; side view; created using xNormal as described in doc) - no idea if it's usedMesh rules defining 'Billboard' show in log (why not using #2 above?). When mesh rules define 'Billboard', I didn't think the following applies (assumed this applied only when Billboard2 is set): Log example from 'Billboard run: TreeAspen01 [TREE:0006A9E6] meshes\landscape\trees\treeaspen01.nif Billboard found LOD4: textures\terrain\lodgen\skyrim.esm\treeaspen01_0006a9e6_1.dds using internal LOD8: textures\terrain\lodgen\skyrim.esm\treeaspen01_0006a9e6_1.dds using internal LOD16: textures\terrain\lodgen\skyrim.esm\treeaspen01_0006a9e6_1.dds using internal Mesh rules defining 'Billboard2' for these trees, log shows (why nothing for #5 above? do I assume the above instruction applies, and the log just doesn't show that detail?): TreeAspen01 [TREE:0006A9E6] meshes\landscape\trees\treeaspen01.nif Billboard found LOD4: textures\terrain\lodgen\skyrim.esm\treeaspen01_0006a9e6_1.dds using dyndolod_flat_2x2_lod.nif LOD8: textures\terrain\lodgen\skyrim.esm\treeaspen01_0006a9e6_1.dds using dyndolod_flat_2x2_lod.nif LOD16: textures\terrain\lodgen\skyrim.esm\treeaspen01_0006a9e6_1.dds using dyndolod_flat_2x2_lod.nif... I assumed that mods could be packaged with all (coexisting) DynDOLOD resource types for the different billboards, meaning I thought I could include all assets in same location as described in the 1-6 list at top of this post ... ? Also, all billboards are too bright in game in all weathers with direct sunlight and look painted in foggy weather (look good in cloudy weathers). I know about the 'brightness' settings in the DynDOLOD INI, but I want to avoid changes to the default so that others can use it without special instructions. I suspect it's the 'super' normal maps made from 4x lighting angles in xNormal. Add transparency to normals or decrease opacity? Diffuse are already a tad darker overall than source.

Grrrr ... so simple and yet so elusive. Thanks!

@sheson There doesn't seem to be a way to do as instructed in ../DynDOLOD/Docs/trees.ultra/DynDOLOD-Trees.html#5: There is no way I can see to set a lighting direction on a model. It's always from 'top' it seems. Nor can I find any way to side-view models from angles necessary for screens of the 3x2 planes (0/60/120/180/240/300). Default front/side views only give me 0/90/180/270, which is fine for the 2x2 but not the 3x2. EDIT: Looks like I can manually type in rotation degrees for 'R' on the main branch (assuming yaw/pitch/rotation is set here and in degrees). Not sure if that's right. Must be a similar way to do lighting direction?

Thanks for the clarifications & confirmations!

OK, so it does use some generic mesh 'internally' defined in DynDOLOD? It can't just be a texture standing up in game, right? So I think I understand that the 2x2 & 3x2 meshes defined in the INI are 'external' defaults, correct? So using the 2x2 for billboard applies when setting 'Billboard2' in mesh rules? If so, how does one get two x/y planes set to the mesh planes with accurate L-W dimensions? By file name like: TreeName01_XXXXXXXX_#.dds, TreeName01_XXXXXXXX_#_n.dds vs TreeName01_#_XXXXXXXX.dds, TreeName01_#_XXXXXXXX_n.dds ... can two different, like-named TXT files be used to define coordinates for the two unique plane billboard shots? EDIT: disregard this last question. I see that the billboard example shows the naming convention and TXT 'Depth' spec in ..\DynDOLOD\Docs\trees.ultra\examples\2-textures-billboard-example\textures\terrain\LODGen\skyrim.esm\ ... but I'm not clear how ShiftX/Y are determined from the defined object bounds (ShiftZ is straight forward as simply the Z1 value): [LOD] Width=434 Depth=358 Height=635 ShiftX=17 ShiftY=1 ShiftZ=-273 Scale=1 Model=Landscape\Trees\TundraDriftWoodTree01.nif

OK, so "Billboard(1)" must use some mesh, and I assume it is the 2x2 mesh provided, whose vertices are modified by the TXT file. Billboard2 must be an explicitly-created external mesh then, and the default INI just refers to the 2x2, since it's a good starting point? The automation sounds great, but the manual effort is appreciated, since it helps me to understand what's going on (If I can understand it :P). I'll keep messing around with it and let you know where I go. Thanks for the continued support.

So I'm a bit confused by use of internal vs external billboard NIF models. It looks like the INI defines what to use: Billboard2=DynDOLOD_flat_2x2_lod.nif Billboard3=DynDOLOD_flat_3x2_lod.nif Billboard4=Internal Billboard5=Internal Billboard6=Internal... and these values can point to 'eternal' NIFs ... is DynDOLOD_flat_2x2_lod.nif 'external' or 'internal'? The "optimized" tree models I created as described in my earlier post are named like TreeAspen01_D10688CApassthru_lod.nif. Now these models are used along with the billboard textures as indicated by the log, fe: TreeAspen02 [TREE:0006C9D5] meshes\landscape\trees\treeaspen02.nif Billboard found <-- unclear on the meshes used for these or how to create them (see below) LOD4: textures\terrain\lodgen\skyrim.esm\treeaspen02_0006c9d5.dds using internal <-- mesh rule set to use "Billboard" for this one ... I didn't create a mesh for this LOD8: textures\terrain\lodgen\skyrim.esm\treeaspen02_0006c9d5.dds using internal LOD16: textures\terrain\lodgen\skyrim.esm\treeaspen02_0006c9d5.dds using internal TreeAspen03 [TREE:0006C9D4] meshes\landscape\trees\treeaspen03.nif Billboard found, 3D LOD found LOD4: meshes\dyndolod\lod\trees\treeaspen03_4e860f19passthru_lod.nif <-- set mesh rule to "3D Static", so my optimized 3D mesh was used LOD8: textures\terrain\lodgen\skyrim.esm\treeaspen03_0006c9d4.dds using internal LOD16: textures\terrain\lodgen\skyrim.esm\treeaspen03_0006c9d4.dds using internal ... I set mesh rules differently for TreeAspen02 and 03 for testing purposes and comparing results in game (I still need to make adjustments to billboard textures and 3D LOD meshes to better align with full models). I created the optimized 3D LOD meshes using DynDOLOD_flat_2x2_lod.nif as a base by making adjustments to the vertices in NiTriShapeData and copying over the BSLitingShaterProperty and NiTriShape blocks from the full model, editing strings, etc. The log tells me that my TreeAspen LOD objects are using this optimized 3D model, so my question is about the models used by the billboards and how to customize those to use my billboard textures (requires baked normals, or can they be separate?). Does "using internal" mean that a billboard is using DynDOLOD_flat_2x2_lod.nif as it's model and that either the Object Bounds (vanilla tree) or the LOD TXT file (custom tree) modify this NIF vertices? So if I am understanding this correctly, I need to make billboard textures with baked normals, one for each plane and named accordingly (_1, _2), and DynDOLOD will use the accompanying TXT and DynDOLOD_flat_2x2_lod.nif as the model? If true, then why the need to point to an 'external' billboard model? I have read these sections a few times and am not sure that I am interpreting correctly.

Ahhh ... subtle but effective. Thanks EDIT: turns out this is of no use in my case, since I am using custom models. I thought that the like-named vanilla replacements would be referenced. Bummer.

Thanks for the tips & direction ... I think I'm getting results now but may need to revise billboards diffuse a bit as well. Will post back once I have made the changes. Also, under SSEEdit (xEdit), I don't get the option to "Split Atlas" when holding shift key on clicking "Generate LOD" for SSE. I don't see this mentioned in DynDOLOD_Manual_SSE.html so wondering about it. I just found the sizes manually, but it may be helpful to get this working if I make revisions to all billboards.

Thanks ... I am currently playing with vertex lighting, but not sure how to impact direct vs ambient lighting in NifScope. Lots of settings ... is that on the BSLightingShader blocks or the NiTriShapeData blocks?

Question: Hybrid trees meshes use CRC32 in the file name, but billboards seem to use the FormID instead ... is this OK, or do I need to use the CRC32 in the billboards as well? If this is simply a way to get a guaranteed unique file name, then I guess it doesn't matter. EDIT: Here is the result ... I did them all since there are only 6 trees. I also did the billboards from scratch. Using default DynDOLOD "High" settings for 3D trees, it seems that it worked; however, the distant trunks are very bright compared to full. Leaves seem fine. For billboards (LOD4-16), I used Tree LOD Billboard Creator to gen the DDS from NifScope (adjusted the lighting before creating the DDS) and manually created the TXT files. The hybrid trees (LOD4) were all done as in my previous post. Is this a lighting thing, or maybe I need to make adjustments to the mesh shader properties? I did create the LOD normals for the hybrid trees using Photoshop (day light setting), so it could be the lighting in the normals I suppose. Any suggestions?

The source meshes didn't include "Double Sided" shader effect, but did include parallax. I thought I read somewhere that parallax and certain other settings are not valid for DynDOLOD. I posted the screen so that you could tell me if you see anything that will break. Example: Texture Clamp Mode of the source was different than the 2x2.nif you provide. If this mesh looks compatible with DynDOLOD, I will finish the other trees models and test.

@sheson I followed the provided instructions with some deviations as required by sources I am working with. (e.g., I had to add "Double Sided" as a "shader effect 2" attribute). Hoping that you can validate an example of a 3D static tree NIF ... I assume that this is a "hybrid tree"? I have named as "TreeAspen01_passthru_lod.nif" and will place into "DynDOLOD-Source" to generate my CRC file names. Does this look and sound correct? ... trunks are 2x flat planes, and leaves are copied from the full model (I found they were already optimized in the blender steps outlined by the supplemental instructions, so I guess this means that I don't need to "re-uv")

It must be your IP. Works fine for me. Maybe disable VPN if you are using one.

Thanks, I will give it a go