Jump to content

Recommended Posts

On ‎17‎.‎06‎.‎2019 at 12:52 PM, KJakker said:

The "T" tab in the upper left corner or using the R key on the keyboard does it now.

Thank you! :good:

Share this post


Link to post
Share on other sites

Version 0.6.2 was uploaded.

Changelog:

Version 0.6.2
-corrected reading of ANSI files with non-ASCII characters
-caseinsensitive handling of node names (e.g. for showing collision, pivot points or bounding boxes of selected nodes)
-disabled mip maps. I hope this resolves the performance issues with hires (4K and above) textures. If not you can use the new option Settings->Display->"Limit Texture Resolution" to limit the (internal) texture resolution.

  • Like 3
  • Thanks 3

Share this post


Link to post
Share on other sites

Awesome Mue, really appreciate your continuing support on this.  How hard would it be to make a 32-bit compatible version though - just want to understand if that's a possibility or not?  I might be in the minority on this, but if not think it's a fair question (I use 32-bit for older support programs including 3DS MAX, PS, and a slew of older games, etc.)

Share this post


Link to post
Share on other sites
On 17/06/2019 at 7:51 PM, pvince said:

No the option does not help but yes they are 4k, however, in 0.52 the same with 4k textures is not slow (only loading is longer).

Another remark from later use, version 0.6x is case sensitive for node names. If case is not exactly the same in the .LOD and in the data.ini, hitboxes and CollisionPoints will not show up when node is selected.

0.62 fixed both, just checked, and limit texture resolution even not needed. That's great. Thanks.

Share this post


Link to post
Share on other sites

I really like the "Limit Texture resolution" feature, as a precaution against system difficulties, thanks Mue, and all decal options are now showing perfectly for me.

This is a great utility, made even greater by your attention to detail. I wish some of the commercial software companies I deal with had your attention to feedback and commitment to customer service. :biggrin:

 

 

  • Like 3

Share this post


Link to post
Share on other sites

AND..

we do all out stuff for FREE!!!

I'm always proud to see the level of dedication that this community puts into their work, wiether it's a skin/decal set, an add on ship or plane, or a utility like this one, and the others Mue's created for us.

My hat is off! :drinks:

  • Like 11

Share this post


Link to post
Share on other sites

A great asset to the community, Mue!  I haven't had any significant problems with using it over the last couple days, but I've found a model ( https://combatace.com/files/file/12642-sh-3d-seaking-for-sf2/ ) where the data populates but the map doesn't appear (see below) on one of the three LOD's in the package.  The other two LOD's seem to work fine.  It's likely a self-inflicted wound - do I have a setting (or something else) wrong or am I completely missing something?

image.thumb.jpeg.16574e36f5412078740e310669a40ec5.jpeg

 

Share this post


Link to post
Share on other sites
3 hours ago, Silberpfeil said:

A great asset to the community, Mue!  I haven't had any significant problems with using it over the last couple days, but I've found a model ( https://combatace.com/files/file/12642-sh-3d-seaking-for-sf2/ ) where the data populates but the map doesn't appear (see below) on one of the three LOD's in the package.  The other two LOD's seem to work fine.  It's likely a self-inflicted wound - do I have a setting (or something else) wrong or am I completely missing something?

Yes, that model is special. It contains nodes (meshes) that are located 44000 and 100000 meters from the main part:

sh-3d_1.jpg.e468feab79f6b7c8b347fd56ce309b36.jpg

The LODViewer tries to show all nodes at once and therefore zooms way out.

If you want to see the helicopter you have to hide those "special" nodes and then click "Fit View":

sh-3d_2.jpg.e89b9019c671e1d44cddb6f453b1514d.jpg

If you want to see the "RescuedGuy" node you have to select that node, hide the unselected nodes and then click "Fit View".

  • Thanks 2

Share this post


Link to post
Share on other sites
22 hours ago, swambast said:

Awesome Mue, really appreciate your continuing support on this.  How hard would it be to make a 32-bit compatible version though - just want to understand if that's a possibility or not?  I might be in the minority on this, but if not think it's a fair question (I use 32-bit for older support programs including 3DS MAX, PS, and a slew of older games, etc.)

Of course is a 32-bit version possible. But as I wrote I have to find the prebuilt dependency library package for 32-bit (unless I build those libraries myself). Maybe I can find them somewhere.
BTW. Do you know that you can run most 32-bit programs without problems on 64-bit Windows? Most likely you don't need a 32-bit Windows to run your old 32-bit programs.

Share this post


Link to post
Share on other sites

Thanks, Mue, for both the explanation and the excellent tutorial - even I could follow it and it works great!  I'm not looking to add to your workload and I don't have much of an idea on how common this situation is with these model remote nodes/meshes installed so far away from the primary's map, but could this be automated in a future version?  

Share this post


Link to post
Share on other sites

I finally tried out the new LOD viewer this morning (its been a rough time lately) and am very impressed. This was excellent for skins and making adjustments without having to fire the game up every time, now thats extended to tga. Especially useful to me and others that work tga based skins (see my airliners or Gepards MiGs for what i mean).

it is hard for me to get a spot on view on the nose arts i am working on, however i blame this on the size of the aircraft im working on not the viewer itself. also despite my joke to the contrary, i think i will still fire up the game every serials completed for a true in game look (ok including weapons too), but this gives a good view of the placement (even on far out ends!) and saves a good chunk of time.

a huge thank you sir for the work you've done

Share this post


Link to post
Share on other sites
16 hours ago, daddyairplanes said:

it is hard for me to get a spot on view on the nose arts i am working on, however i blame this on the size of the aircraft im working on not the viewer itself.

Maybe it helps to switch to orthographic projection by switching off the perspective projection. Have you tried the side (left/right) views. And then to pan the view either with mouse (shift + left mouse) or keybord (shift + arrow keys)? You can also set the view control "sensitivity" in Extras->Settings->Control.

Share this post


Link to post
Share on other sites

@mue I found an issue with LODViewer_v0.6.2. When viewing some of WhiteBoySamurai's ships when I click upon certain meshes used as pivot points for VLS missile and SBROC launchers it causes LODViewer to crash. I believe it is related to a "Material ID" issues as these are intended to not be visible in game.

Below are screen captures of WhiteBoySamurai's DDG-72 variant of his DDG-51 shown in LODViewer v0.5.2, which has no problem with the related meshes and then contrasted with LODViewer v0.6.2 which crashes.

LODViewer v0.5.2 pivot point meshes highlighted, note the "Material ID" listed...

2019-08-30_104232_LODViewer_v0.5.2.thumb.JPG.7cda4aaf394247381e2975fe83634769.JPG

2019-08-30_105035_LODViewer_v0.5.2.thumb.JPG.6780c2009f62d913f15a8212c9d98296.JPG

...Vs. LODViewer v0.6.2, note the difference in the "Material ID" number contrasted with above...

2019-08-30_105550_LODViewer_v0.6.2.thumb.JPG.616c572c6fde5e6e19a624535104acb9.JPG

2019-08-30_110017_LODViewer_v0.6.2.thumb.JPG.286ee05903799e5f1c80b418e3195076.JPG

...Crashed when pivot point mesh clicked upon.

2019-08-30_110109_LODViewer_v0.6.2.thumb.JPG.e0a96a9d8582f111d0246944d5f6eabd.JPG

Share this post


Link to post
Share on other sites
1 hour ago, KJakker said:

@mue I found an issue with LODViewer_v0.6.2. When viewing some of WhiteBoySamurai's ships when I click upon certain meshes used as pivot points for VLS missile and SBROC launchers it causes LODViewer to crash. I believe it is related to a "Material ID" issues as these are intended to not be visible in game.

Bug confirmed!

Share this post


Link to post
Share on other sites

Version 0.6.3 was uploaded.

Changelog:

Version 0.6.3
-bugfix: selection of nodes without material crashed the program

  • Thanks 4

Share this post


Link to post
Share on other sites

it no workee rite for me. it does start to a blank window. But, i discorered i can access the menu functions by clicking whee the menu or too bar would be. I tried to open a LOD and it crashed.  Oh, i did install the redistributables. (I believe have visual c++ on here anyway...maybe that's code blocks anyway...no luck.

Am running windows 7 pro, and will use the compatibility feature to see if it will work that way.

Thanks tho, will be useful.

Share this post


Link to post
Share on other sites

OK, the addition of being able to load decals....so awesome.  Biggest thing since this tool came to light.

 

Requests -

1.  Add a button like reload decals to reload the skin.

2.  If you can pull the decals in, can you get the pilots to show?  (not a big thing)

Share this post


Link to post
Share on other sites
4 hours ago, 10107 said:

OK, the addition of being able to load decals....so awesome.  Biggest thing since this tool came to light.

 

Requests -

1.  Add a button like reload decals to reload the skin.

2.  If you can pull the decals in, can you get the pilots to show?  (not a big thing)

Reload skin reloads decals too ...why need another button ?...lol   I use it to fine tune mine..or change them...easier than in 3dsmax then in game then max again

Share this post


Link to post
Share on other sites

Pilots and seats would be useful for positionning them and adjusting hitboxes. Following the same idea, also the weapons could be great. In a first step, only one weapon on only one station could be good enough. With one list to define the station, and another one to select the weapon.

  • Like 1

Share this post


Link to post
Share on other sites

never had ANY problems adjusting pilot hit boxes. Weapons? Why would that even be necessary?

Share this post


Link to post
Share on other sites
25 minutes ago, Wrench said:

Weapons? Why would that even be necessary?

Because some weapons have non-standart 3d files, made for specific plane (for example including racks) and it could be cool to see weapon position in LODviewer.

Also some weapons have many versions, so again you can choose the best looking one ;-)

Finally it can be good addon for setting weapon stations and loadouts.

Share this post


Link to post
Share on other sites

this could be a very useful tool. For setting positions, angles of weapons, pilots fake pilots, etc.... but in that case, lodviewer should read data ini file ? for coordinates?

 

edit:

 

of course, no sweat...we can do this old way...

Edited by yakarov79

Share this post


Link to post
Share on other sites
1 hour ago, Wrench said:

never had ANY problems adjusting pilot hit boxes. Weapons? Why would that even be necessary?

For adjusting attachment position and angles in data.ini, for example, for external stations but also internal (interferences or weapons seen outside of the closed bay).

 

1 hour ago, guuruu said:

Because some weapons have non-standart 3d files, made for specific plane (for example including racks) and it could be cool to see weapon position in LODviewer.

Also some weapons have many versions, so again you can choose the best looking one ;-)

Finally it can be good addon for setting weapon stations and loadouts.

Exactly

 

39 minutes ago, yakarov79 said:

this could be a very useful tool. For setting positions, angles of weapons, pilots fake pilots, etc.... but in that case, lodviewer should read data ini file ? for coordinates?

 

edit:

 

of course, no sweat...we can do this old way...

LODviewer does already read data.ini (hitboxes, collisionpoints, component names and maybe other things I forget).

Share this post


Link to post
Share on other sites

Yeah, not skins data.inis I meant.

A lot of stuff I take on as a project has some bad  min max boxes (old files).  The button would be great vice file - select last loaded ini.  Then sometimes in my install on how I load the ini, it doesn't add it to the list. So Reload Data.ini button.  :)

Question about decals.  It displays level 0 decals but not the rest.  Level 2 where the serials live.    I don'ty know what I'm missing as I see serial numbers showing in other screenshots.  If I change the serials decal level to 0 in the ini and reload, they show.

 

image.thumb.png.01edb31256c786884846a9ee55a61248.png

 

 

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By crisisloaner
      Hello to all you super modders out there, I have no idea what I'm doing  but have managed to obtain a free 3d model from Turbo_Squid and have managed to use Blender to turn it into a Lod file. Problem is I have no idea what to do next regarding the ini's and skins ...I do not have 3ds and am a complete novice with blender (to be honest,I haven't even read the guidance on it yet !). Any help ion trying to create a viable game object much appreciated !
    • By mue


      View File LOD Exporter for Blender
      I tried to implement the exporter only based on the information I found by investigating LOD files. I'm not a 3D Modeler myself. I only tested the exporter with rather simple object (hierarchies).
      The bottom line is that I have no idea if the exporter works for you. So please give feedback.
      Note: This plugin requires blender version 2.78 or 2.79. It is not compatible with blender versions 2.8+.
      1.) Installation
      Open the Blender User Preferences - Add-ons Tab
      (File -> User Preferences... -> Add-Ons)
      Click "Install from File..."
      Browse to and select the exporter python script "io_export_sf2_lod.py"
      Click "Install from File..." (or double click on the script name)
      In the Add-Ons Tab under Supported Level select Testing and enable "Import-Export: Strike Fighters 2 LOD Exporter"
      The LOD exporter is now installed and enabled. Under File -> Export you should see the menu item "Strike Fighters 2 LOD (.lod)". It's greyed out until an exportable object is selected.
      2.) Usage
      Select the object you want to export and click File -> Export -> Strike Fighters 2 LOD (.lod)
      The file browser opens. In the lower left area you see the LOD exporter options:
      -enable/disable writing the out file (text file with information about the exported object(s)).
      -enable/disable animation export
      -allow decals:
          This option is similar to the option in the original TW-Exporter: "Exporting using AllowDecals=0 causes the vertex to be shared, so it can reduce the size of the .LOD but also causes decals to "bleed" along the edges."
          This dialog setting is used as default for all objects to be exported. However, it can be overwritten by each individual object via the custom object property "AllowDecals" = 0(false) or 1(true)
      The selected object and all child objects are exported.
      Two custom object properties are supported by the exporter:
          -AllowDecals = 0 or 1, This option is similar to the option in the original TW-Exporter: "Exporting using AllowDecals=0 causes the vertex to be shared, so it can reduce the size of the .LOD but also causes decals to "bleed" along the edges."
          -UseFlatNormal = 0 or 1, if set to 1 then all vertex normals are pointing straight up (normal = (0,0,1)) in the objects local coordinate system.
      Please note!
       
      The objects must meet the following requirements:
      -No scaling in the Transform Properties allowed (that means: scale x = y = z = 1.0). If your object has scaling, it should be applied to the mesh (Ctrl-A)
       Scaling is only allowed for animations.
      -A material must be assigned to the object. Only the first material of an object is exported.
      The following material parameters are exported:
          -Diffuse Color (the lod file format also contains ambient color. Currently the exporter set ambient color = diffuse color)
          -Specular Color
          -Specular Intensity
          -Specular Hardness (I think in 3ds Max it's called glossiness)
          -if "Shading -> Emit" > 0.0 then self illumination is enabled
          -Transparency (if transparency is enabled, then the object doesn't cast and doesn't catch shadow. if transparency is disabled, then the object cast and catch shadow. The specific LOD format version the exporter writes, doesn't support arbitrary cast/catch shadow combinations. The other LOD formats I don't understand enough (yet). Sorry!)
          -Alpha
          -Mirror Reflectivity
          -Diffuse texture image name (as diffuse texture the exporter uses the texture where "Influence -> Diffuse -> Color" is enabled)
          -Normal map texture image name("Influence -> Geometry -> Normal" is enabled and the Normal value is also exported)
          -Specular map texture image name("Influence -> Specular -> Intensity" is enabled)
          -Normal and specular map can only be used together with a diffuse map. (If I exported a normal or specular map without diffuse map, then the LOD wasn't shown in the game or the game crashed. I don't know why...)
          
      Animation Export:
          
          This exporter supports the following object animation types: location, rotation and scaling.
          Frames 10, 20, 30, ..., 100 are exported as animation 1
          Frames 110, 120, 130, ..., 200 are exported as animation 2, ...

      3.)Credits:
      Thanks to logan4 and angelp who provided me with specific lod files that helped me to understand the lod file format better.

      4.)Changelog:
      Version 0.1:
      -initial release
      Version 0.2:
      -bugfix: didn't work in blender version 0.79
      Version 0.3:
      -animation support
      -added custom object properties: "AllowDecals" and "UseFlatNormal"
      Submitter mue Submitted 04/30/2018 Category Utilities / Editors  
    • By mue
      I tried to implement the exporter only based on the information I found by investigating LOD files. I'm not a 3D Modeler myself. I only tested the exporter with rather simple object (hierarchies).
      The bottom line is that I have no idea if the exporter works for you. So please give feedback.
      Note: This plugin requires blender version 2.78 or 2.79. It is not compatible with blender versions 2.8+.
      1.) Installation
      Open the Blender User Preferences - Add-ons Tab
      (File -> User Preferences... -> Add-Ons)
      Click "Install from File..."
      Browse to and select the exporter python script "io_export_sf2_lod.py"
      Click "Install from File..." (or double click on the script name)
      In the Add-Ons Tab under Supported Level select Testing and enable "Import-Export: Strike Fighters 2 LOD Exporter"
      The LOD exporter is now installed and enabled. Under File -> Export you should see the menu item "Strike Fighters 2 LOD (.lod)". It's greyed out until an exportable object is selected.
      2.) Usage
      Select the object you want to export and click File -> Export -> Strike Fighters 2 LOD (.lod)
      The file browser opens. In the lower left area you see the LOD exporter options:
      -enable/disable writing the out file (text file with information about the exported object(s)).
      -enable/disable animation export
      -allow decals:
          This option is similar to the option in the original TW-Exporter: "Exporting using AllowDecals=0 causes the vertex to be shared, so it can reduce the size of the .LOD but also causes decals to "bleed" along the edges."
          This dialog setting is used as default for all objects to be exported. However, it can be overwritten by each individual object via the custom object property "AllowDecals" = 0(false) or 1(true)
      The selected object and all child objects are exported.
      Two custom object properties are supported by the exporter:
          -AllowDecals = 0 or 1, This option is similar to the option in the original TW-Exporter: "Exporting using AllowDecals=0 causes the vertex to be shared, so it can reduce the size of the .LOD but also causes decals to "bleed" along the edges."
          -UseFlatNormal = 0 or 1, if set to 1 then all vertex normals are pointing straight up (normal = (0,0,1)) in the objects local coordinate system.
      Please note!
       
      The objects must meet the following requirements:
      -No scaling in the Transform Properties allowed (that means: scale x = y = z = 1.0). If your object has scaling, it should be applied to the mesh (Ctrl-A)
       Scaling is only allowed for animations.
      -A material must be assigned to the object. Only the first material of an object is exported.
      The following material parameters are exported:
          -Diffuse Color (the lod file format also contains ambient color. Currently the exporter set ambient color = diffuse color)
          -Specular Color
          -Specular Intensity
          -Specular Hardness (I think in 3ds Max it's called glossiness)
          -if "Shading -> Emit" > 0.0 then self illumination is enabled
          -Transparency (if transparency is enabled, then the object doesn't cast and doesn't catch shadow. if transparency is disabled, then the object cast and catch shadow. The specific LOD format version the exporter writes, doesn't support arbitrary cast/catch shadow combinations. The other LOD formats I don't understand enough (yet). Sorry!)
          -Alpha
          -Mirror Reflectivity
          -Diffuse texture image name (as diffuse texture the exporter uses the texture where "Influence -> Diffuse -> Color" is enabled)
          -Normal map texture image name("Influence -> Geometry -> Normal" is enabled and the Normal value is also exported)
          -Specular map texture image name("Influence -> Specular -> Intensity" is enabled)
          -Normal and specular map can only be used together with a diffuse map. (If I exported a normal or specular map without diffuse map, then the LOD wasn't shown in the game or the game crashed. I don't know why...)
          
      Animation Export:
          
          This exporter supports the following object animation types: location, rotation and scaling.
          Frames 10, 20, 30, ..., 100 are exported as animation 1
          Frames 110, 120, 130, ..., 200 are exported as animation 2, ...

      3.)Credits:
      Thanks to logan4 and angelp who provided me with specific lod files that helped me to understand the lod file format better.

      4.)Changelog:
      Version 0.1:
      -initial release
      Version 0.2:
      -bugfix: didn't work in blender version 0.79
      Version 0.3:
      -animation support
      -added custom object properties: "AllowDecals" and "UseFlatNormal"
    • By mue
      This is the newest version of the LODViewer.
      New features:
      -decal support
      -display of collision and pivot points
      -added transparency and wireframe display mode
      -user definable background color
      -view manipulation via keyboard
      -64 bit application
      -uses the OpenSceneGraph library and Qt 5.9.5
       
      Install instructions:
      Extract the content of the zip package to a convenient location.
      The LODViewer depends on the Microsoft Visual Studio 2017 C++ libraries. If not already installed on the computer (e.g. by other applications) it has to be installed by running vcredist_x64.exe (you can find it in the redist subfolder of this package).
       
      Have fun! And report bugs
      Mue
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..