Jump to content
  • Announcements

    • Erik

      2019 Drive   05/31/2019

      Can you lend a hand?  GET STARTED TODAY

Recommended Posts

LODViewer


This is the newest version of the LODViewer.

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.
 
Version 0.6.1
-added decal texture file loading fallback: If numbered texture file is not found, it’ll then look for unnumbered file.
-added option for using vertex buffer objects (Extra->Settings->Display->Use Vertex Buffer Objects)
 Maybe "Use Vertex Buffer Objects" helps with the performance problem some users have experienced with Version 0.6.0.
 Beware! Enabling this option while simultaneously "Write OSG log file" is enabled, writes A LOT to osg_logfile.txt.
-bugfix: "Write Info File" didn't work in Version 0.6.0
-bugfix: Couldn't save UV Mapping as jpg file
 
Version 0.6.0
-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 :biggrin:

Mue


 

Edited by mue
uploaded version 0.6.2
  • Like 3
  • Thanks 7

Share this post


Link to post
Share on other sites

Cool! Someone will be very happy...

Although some guys here might totally stop playing the game...

Thanks!

Have you considered an option where you could merge two or more lod files in one scene? useful at weapon positioning, fake piloting etc...

 

  • Like 3
  • Thanks 1

Share this post


Link to post
Share on other sites

Another breakthrough and making history!! Super bravo! Is there a way to read DecalLevel=0? Some roundels not shows up.

Share this post


Link to post
Share on other sites

I have an issue with the last version : when I open the ini file of the aircraft that I want to see on the LODViewer, systematically I have a CTD (the previous version works perfectly)

Thanks for you help.

 

Share this post


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

Another breakthrough and making history!! Super bravo! Is there a way to read DecalLevel=0? Some roundels not shows up.

Should work. Can you send me or give me a link of the aircraft, where it doesn't work?

35 minutes ago, ludo.m54 said:

I have an issue with the last version : when I open the ini file of the aircraft that I want to see on the LODViewer, systematically I have a CTD (the previous version works perfectly)

Thanks for you help.

 

Do you get the CTD with all aircrafts?

Share this post


Link to post
Share on other sites

I'm very happy with this update, the least I can do is to write a Thank You! :good:

But take this just as a Bug Report: me too I don't seem to be able to load decals with DecalLevel=0...

 

Share this post


Link to post
Share on other sites

Some aircrafts cause CTD and as I said everything set as DecalLevel=0, numbers, letters or roundels, does not shows. Even so, what a marvelous improvement!

Share this post


Link to post
Share on other sites
8 hours ago, mue said:

Should work. Can you send me or give me a link of the aircraft, where it doesn't work?

Do you get the CTD with all aircrafts?

I made several tests with different aircrafts (the Mirage F1EQ for example) and the result is always the same.

 

Share this post


Link to post
Share on other sites

I tested it with more then ten different stock aircraft. No CTDs. No problems with showing decals with DecalLevel=0. Until now, I can not reproduce the bugs :dunno:

Here, as an example the F-104A (marked with red circles are the decals with DecalLevel=0):
f-104a_decals.thumb.jpg.baa59e6717364b5c7bf94f46365cc4be.jpg

Could you please give me the name of the stock aircraft or the download link of the mod aircraft, that you have problems with.
Thanks!

Share this post


Link to post
Share on other sites

Regarding the DecalLevel=0 problem, can you please check if this is the cause of the problem:

The current version of the LODViewer expects as texture file name the "full" name including the nation ID (e.g. "INSIGNIA002.TGA"). The LODViewer currently does NOT look for "INSIGNIA.TGA" as fallback.

Edited by mue
typo

Share this post


Link to post
Share on other sites

I think this is ace but I'm only seeing my non-stock serial numbers (Decal Level 2) and not my other decals (Decal Level 0) despite them being in the same folder.

Stock Aircraft - All working fine.

Added Mods - only seeing serial numbers (Decal Level 2)

Edited by Spinners
Update

Share this post


Link to post
Share on other sites
20 minutes ago, Spinners said:

I think this is ace but I'm only seeing my non-stock serial numbers (Decal Level 2) and not my other decals (Decal Level 0) despite them being in the same folder.

Stock Aircraft - All working fine.

Added Mods - only seeing serial numbers (Decal Level 2)

Does your mod decal files (Decal Level 0) contain the nation number (e.g. INSIGNIA002.tga)? See my post above.

Share this post


Link to post
Share on other sites
5 minutes ago, mue said:

Does your mod decal files (Decal Level 0) contain the nation number (e.g. INSIGNIA002.tga)? See my post above.

No. These will all be decals made by me (Decal Level 0) but the serial numbers are also made by me and they show just fine.

Share this post


Link to post
Share on other sites
5 minutes ago, Spinners said:

No. These will all be decals made by me (Decal Level 0) but the serial numbers are also made by me and they show just fine.

I assume you serial number texture filenames have numbers at the end (e.g wingnum001.tga)?

Share this post


Link to post
Share on other sites
9 minutes ago, mue said:

I assume you serial number texture filenames have numbers at the end (e.g wingnum001.tga)?

Aye!

Share this post


Link to post
Share on other sites

My understanding of the decal system is as follows:

The texture file name is defined by Filenameformat. Depending on DecalLevel either the nation id (if DecalLevel=0) or squadron id (if DecalLevel=1) or serial number index (if DecalLevel=2) or kill number (if DecalLevel=3) is appended to the texture file name. The game (and the LODViewer) then tries to load this texture file. But the game has a fallback behavior, that the LODViewer has not (yet): if the game doesn't find the texture file with the numbers at the end, it then tries to load the texture file defined solely by Filenameformat (without the numbers at the end).
Therefore I think the modded decals (DecalLevel=0) doesn't show in the LODViewer, because they doesn't end with the nation id number and the LODViewer misses the fallback behavior of the game, that would load the texture file without the numbers at the end. I will add the fallback behavior in the next update.

Edited by mue
  • Like 1
  • Thanks 2

Share this post


Link to post
Share on other sites

Thanks Mue. I've used this on an almost daily basis since coming back to the community after taking an 18-month break. The time saving on identifying mesh names and also getting precise co-ordinates for decal placement has been a huge factor in getting the most out of my time so a big thank you :clapping:

Share this post


Link to post
Share on other sites

I forgot to say: I have to thank you guys for the bug reports. It's really helpful. Because of lack of time (and maybe motivation :biggrin:) I don't test all possible cases. Therefore I'm really grateful to you for testing my (buggy) software. :good:

Share this post


Link to post
Share on other sites

Thanks a lot, Mue. I particularly like the transparency and decal support, and the user-defined controls and background menus are very useful.

Share this post


Link to post
Share on other sites

Mue, I'm getting quite a few system freezes using this latest V0.60 LODViewer - the hard sort which requires a power-off and then power-on PC reset, not the soft Cntrl-Alt-Del sort.

It happens two or three times in a row, immediately I try to rotate or move the LOD, then after reset I can use the Viewer for a while. Sometimes it happens again, after a few minutes of use.

I use  the Alt and mouse keys for movement and rotation.

It seems to happen more readily  with more complex aircraft models. The little A5M Claude (6000 polys), for example, gives no problems, but Veltro2k's B-26 Marauder or the A-Team's new B-26 Marauder (both 42,000 polys) freeze every time, usually at the very first attempt to rotate or shift the model.

Any ideas on this?

Edited by Gatling20

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 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
    • By sophocles
      Hello all, I was wondering If you can have more than 5 (five) LOD models for aircraft.  It sure would be convenient as I want to separate the initial LODs quite close together (1 at 50m, 2 at 125m, 3 at 250m .. and then 4,5,6,7 at much greater distances out to 10000m)
      Thanks for your help.
    • By mue
      Maybe some of the flight model guys find this useful for creating, analyzing or checking flight models.
      Last year I had the idea for a tool that extracts the data of the debug hud and writes them into a text file:
      (from this post: https://combatace.com/forums/topic/91675-how-to-develop-test-flight-models/?do=findComment&comment=741238):
       
      The process steps are illustrated in the following figure:

       
      The tool "DebugHUDExtractor" I came up with is written in python and uses the optical character recognition (OCR) software tesseract. Thus to use the DebugHudExtractor you have to install python, some python packages and the tesseract software.
      For those who want to try this tool, here are the installation, configuration and usage instructions:
       
      1.) Download and install tesseract: https://digi.bib.uni-mannheim.de/tesseract/tesseract-ocr-w64-setup-v4.1.0.20190314.exe
      Copy lucidaconsole.traineddata into tessdata directory (e.g. C:\Program Files\Tesseract-OCR\tessdata). Needs admin rights.
      This file contains the trained data for the lucida console font. I use this font as it gave me the best results with the character recognition. This font has to be configured for the debug hud output in the game (see. step 4 below)
      2.a) Download and install python: https://www.python.org/ftp/python/3.7.3/python-3.7.3-amd64.exe
          While installing select "Customize installation":
          -optional: change the installation directory (e.g I use C:\Python37)
          -enable "Add Python to environment variables"
      2.b) Install needed python packages.
      On the windows command line execute the following commands:
      pip install pillow pip install numpy pip install opencv-python pip install pytesseract 3.) Setting the path to the tesseract executable:
      In <Python_install_directory>\Lib\site-packages\pytesseract\pytesseract.py (line 35) set tesseract_cmd to the file path of the tesseract executable. Use double backslashes or normal slashes.
      E.g.:
      tesseract_cmd = 'C:\\Program Files\\Tesseract-OCR\\tesseract'  
      4.) Configure the game.
      In SF2/FE2 game set Option Hud = Normal and configure the Huddata.ini.
      It enables the debug hud, set the font to lucida console, sets a bigger font size (the bigger the better, but all relevant debug info should still be displayed in the screen,e.g. for my 1920x1080 resolution I use TextSize = 24)
      ,the normal font color is changed to red (required for text filtering), the default right info box is disabled and the default left aircraft info box is moved to the right (that gives more space for the debug info box on the left)
      [Debug] DisplayDebug=true [Font] TextFontName=Lucida Console TextSize=24 [InfoDisplay] //BackgroundImage=TextBackground.tga BottomLeftPosition=0.8,1.0 //BottomRightPosition=0.99,0.985 NormalColor=1.0,0.0,0.0,1.0
      5.) Configure the python script debughudextractor.py :
      Depending on the values you want to extract from the debug hud the variables extractPitch, extractAlpha, ... have to be set to True or False,
      The leftRect and rightRect variables have to be configured depending on where the debug info box and aircraft info box is located on your screen (depending on your screen resolution and the entries in your huddate.ini)
      The format is as follows:
      leftRect = (top-left-x, top-left-y, bottom-right-x, bottom-right-y)
      The top left corner of the screen is the origin (0,0).
      E.g. with a resolution of 1920x1080 and the above huddata.ini, I use the following:
      leftRect = (56,236,1450,1080) rightRect = (1528,968,1920,1080)  
      See this picture:


      6.) Start the script from windows command line:
      python debughudextractor.py video_file_path time_step_in_s start_time_in_s end_time_in_s <video_file_name>.txt and <video_file_name>_error.txt will be written into the directory of the video file.
      <video_file_name>.txt contains the extracted data.
      <video_file_name>_error.txt contains what values at what time couldn't be recognized. If a value couldn't be recognized, then the very next video frame is used and analyzed.
×

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..