Jump to content
  • Announcements

    • Erik

      2019 Drive   05/31/2019

      Can you lend a hand?  GET STARTED TODAY

pvince

+PREMIER MEMBER
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

7 Neutral

About pvince

Profile Information

  • Gender
    Male
  • Location
    NESLES LA VALLEE
  1. 0.62 fixed both, just checked, and limit texture resolution even not needed. That's great. Thanks.
  2. 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.
  3. Super Etendard is modified (HitBoxes + CollisionPoints) There are also some older updates I already had done: fuel tank capacity, tail hook deflection... Super_Etendard_Data.ini
  4. The new version (0.6x) is not compatible with ANSI code (version 0.52 has not the issue). It is probably the combination ANSI + some special characters in the file. Typical problems then: - data file not loaded - numbers.lst : numbers not shown in individual markings dropdown list (detected because of '°' in the text file) - textures.ini : texture not loaded (suspected character is 'é' in 'Aéronavale' ) And for your info, unfortunately still very slow for me also with 0.61. Sometimes it improves after some time after the model is loaded.
  5. I remember I read formerly somewhere in the forum that the gun must always be at 0° in the LOD (hidden in the fuselage then).
  6. And here is mine. My PC does not freeze, but execution is very slow, and with delays on controls. osg_logfile.txt
  7. Mue, this logfile has been generated on a model with slow execution. There are warnings in it. Maybe it helps. osg_logfile.txt
  8. Mue, first a big thank for this wonderful tool. I also have the problem of very slow execution (menus, rotations, any interaction with the program ...), which is better after some time, or if program closed and immediately relaunched. I also had a windows memory error (not enough memory), one time. I also had a data file that could not be loaded (<no data file>), but the file was there (and loaded ok with version 0.5.2). By comparaison with a working file I have found that this was due to the character '°' (complete comment line : "// -60°, 100 meter level") that prevented the load. The data file was in ANSI (again no problem with 0.5.2). Conversion to Unicode also fixed the problem for 0.6.0. Hope this will help.
  9. AN11 in sfp1 section ? Where ? I've not found it.
  10. Nice job, thanks. I noticed with LOD viewer hitboxes were all wrong (also Fuselage nodename in data.ini). I've updated the data.ini to improve. File is attached. Feel free to reuse of course. A400M_DATA_updated.INI
  11. F-105B Thunderchief (Stand in)

    There's a typo mistake in the download : Directory is 'Pilot'. It should be 'Pilots'. Due to that there's pilot legs below the aircraft.
  12. Alternatively the wrong cockpit .LOD files can be corrected using a hex editor to rename the alt_digX, alt1_digX, alt2_digX nodes in reverse order. I've done it on my files.
  13. I confirm : I had the same issue (does not start) and disabling Avast solved it. However previous LOD viewer version (0.5.1) worked well even with Avast on.
  14. F4D-1 Skyray ULTIMATE PACK for SF2

    The 'NAV PAC' is not included. Where could we find it ?
×

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