Jump to content

mue

+MODDER
 View Profile  See their activity

  • Content count

    397

  • Joined

  • Last visited

  • Days Won

    8

Everything posted by mue

  1. Yes, currently only 64-bit support: Even though I compile the OpenSceneGraph library myself, I rely on the prebuild dependency packages for OSG. Those I only found as x64 version. And to compile the dependency packages myself, I didn't find the time and motivation yet. I need the 64-bit OpenSceneGraph library anyway for a FlightGear related project. I didn't thought, that 32-bit Desktop-OS is still a thing.
  2. Will be fixed in the next version. That means the "Use Vertex buffer objects" option doesn't help? Does the slowdown happen also with stock objects? Do you use 4K textures?
  3. I didn't know that there is also a decal system for ground objects. After a first glance, it seems it only works with ships? It uses the *_names.ini (that contains [ShipXXX) entries) instead of numbers.lst. Is this correct? Are there other types besides ships? Until I implement the ground object decal system, you can view the hull numbers with this workaround: copy a NUMBERS.LST file that contains sufficient numbers, e.g. I used F-4B\USMCGREY1\NUMBERS.LST (contains numbers 0 - 99) into the texture folder. Then you can select the hull number via Individual Markings.
  4. Version 0.6.1 was uploaded. Changelog: 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
  5. For modeling you can also use blender (open source). There is an LOD exporter for blender: https://combatace.com/files/file/16747-lod-exporter-for-blender/
  6. Could both of you please (re)create log files with the "write osg log file" option already enabled at program start (just restart LODViewer with this option enabled). Some information will only be written to the log file at program start. If the log option is enabled only after the program start, then that information are missing in the logfile.
  7. I don't think "it's just your PC", since other users also have problems with the LODViewer. Unfortunatelly, I have no clue what the cause of the problems is, because I don't see it on my computers. I have a request: please enable OSG logging (Extras->Settings->Debugging->Write OSG log file). It writes a logfile "osg_logfile.txt" in the lodviewer.exes directory. restart the LODViewer load the Marauder if the "osg_logfile.txt" is written, please send it to me. Thank you! Maybe the logfile gives me some pointers.
  8. I tested this package. I don't see any freezes or crashes
  9. I downloaded and tested this Mirage F-1EQ . Because of the 4K Textures my development system (Windows 7 with an old 8800 GTS 512) struggles. It gives me a slide show. But it doesn't crashed. On another computer with a GTX 660 I have no problem.
  10. 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 ) I don't test all possible cases. Therefore I'm really grateful to you for testing my (buggy) software.
  11. 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.
  12. I assume you serial number texture filenames have numbers at the end (e.g wingnum001.tga)?
  13. Does your mod decal files (Decal Level 0) contain the nation number (e.g. INSIGNIA002.tga)? See my post above.
  14. 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.
  15. 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 Here, as an example the F-104A (marked with red circles are the decals with DecalLevel=0): 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!
  16. 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?
  17. I created and added the "reversed" LOD files. The reversed LOD files are named *_Rev.lod Italian Euro Pilot +Rev.7z RAF Euro Pilot Oxy +Rev.7z
  18. I assume it's only possible to define the pilot position and not the orientation in the ini file. Is this correct? Then of course the orientation within the lod file must be changed. But it's not that difficult if one knows a little bit about the lod format . Can you send me the lod file?
  19. I concur with what Gunrunner wrote. BTW, for those who didn't already know: One can easily search all .cat/.dlc files at once with the catextractor from Mues Toolbox. In this post: https://combatace.com/forums/topic/88951-some-newbie-questions/?do=findComment&comment=724535 it's shown exemplarily for shader files.
  20. To clear things up regarding stock object scale in FE1/FE2 I measured exemplarely the length of the BeutepanzerIVF from FE2 with the lodviewer: In the node list window you can see that the selected node "RightSide" has an extension along the y-axis from -3.942 m to 3.973 m. That yields a length of 7.915 m. (One can also move the mouse cursor over the object to get the coordinates in the status bar.) Wikipedia: https://en.wikipedia.org/wiki/Mark_IV_tank specifies a length for the tank mark iv (in game the beuterpanzerIVF) of 8.05 m. Therefore I assume the stock objects in FE2 have real life size and are not scaled down. Since I don't own FE1: Can someone please measure the BeutepanzerIVF from FE1. Thanks!
  21. @Geezer...are you really serious? You seem to be a talented 3D artist, but your ability for discussion is...how should I say..."improvable". You not only insulted me, but the whole SF community. Why do you make it a FE vs. SF thing? As Gatling20 wrote, it really makes you look simple-minded. Maybe you didn't know that the game engines of both games are nearly identical. E.g. this very thread has shown that the stock objects of ALL TW games (FE and SF) are the same big 100% size. So IMHO the TW community should not be grouped in "FE fanboyz" vs. "SF fanboyz", but rather should be seen as one big family ! But maybe you need this "us vs them" scheme? I don't know. It's a pitty. This thread, from my point of view as thread opener, was never about your intellectual property. This thread is, as I already explained to you multiple times, about the scale of stock objects. Last point: What makes you think you can decide who are allowed to post in what (sub) forums. Are you a moderator?
  22. Oops ... it seems I should have a closer look at the knowledge base. The information (non-support of RLE-compressed tgas) I found out through trial and error, was already there, even repeated.
  23. I use GIMP. When exporting the tgas I had to disable the option "RLE compression", otherwise the decals wouldn't show up in the game.
  24. @Geezer, please don't imply that I want to be in charge or that I'm on an ego trip. I have never written something like that. Because of your mention of "the best modders work in FE" and your insulting posts in the past, one could rather think that you are on an ego trip. I really only wanted to correct the flawed assumption that FE objects have to be of 63% size. I want to help (new) modders by giving them correct information. As this thread shows, a lot of people were under the false impression that FE object have to be scaled down and then they wonder why the new created objects don't match the size of the stock objects. I only stated this fact and proofed it with measurement. But you, however were angry for whatever reasons, what I really don't get. If you don't want this information, fine. But maybe other modders find them useful.
  25. Ok, it seems nothing new is coming in this thread. So it's a good time to summerize the facts given in this thread: Fact 1.) All measurements of stock objects in all games (SF1/SF2/FE1/FE2) have shown that the stock objects are of 100% size. Fact 2.) No proof was given for the claim, that there exist 63% size stock objects. Not a single 63% size stock object was shown. Based on fact 1. and 2. it can be assumed all stock objects in all games are of 100% size. Fact 3.) You can create objects at any scale you like (e.g. 10%, 50%, 63%, 100%, 200%,...). Nobody is stopping you. Fact 3.a) If you create an object with a different scale than 100%, you maybe get problems if you want to mix it with 100% (stock) objects. Fact 3.b) No reasons were given why it is beneficial to scale objects 63%, besides the flawed assumption of the existence of 63% sized stock objects (see fact 1. and 2.)
×

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

  I accept