Jump to content

NRG-Vampire

Members
  • Posts

    3948
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by NRG-Vampire

  1. It's not as easy as it looks like ? Yes, the problem is exactly like that: how it looks. IMHO it's starting to be awkward seeing very old (and ugly) 3D models (Vaz car, Ikarus bus, Trucks, Barge-ships etc.) while the "updated/facelifted" 3D models already in the game as landscape-reference-file but ED did not imported/converted into EDM (for using in the ME by clients). Those old F-14A and Mirage 2000-5 models came from Flanker2 what is 20 yeras old. In LOMAC (17 years ago) those models got some nozzle and afterburner 3D facelift and appeared the newer F-18A 3D model in LOM format. So it is easy: it's only a matter of determination (by ED) and an agreement: (if the proprietor of the 3D model is a 3rd party). I hope they will change/update all those old Flanker2 and LOMAC-era 3D models.
  2. I meant the AI unit. They mentioned some units already in the newsletter. AFAIK M-2000-5 differ externally (for AI) only in the pitot tube/probe and some antennas/sensors on the tail and fuselage. So, it would be only a few 3D-parts-visibility-cosmetics on the current 3D model and should be easily used (the same 3D model) with changing parts in the liveries-description.lua by the custom_args = function/feature.
  3. Bingo ! I meant the AI unit. They mentioned some units (see below) in the newsletter. The same should be true for the old F-14, F-16 and F-18 models. Those 3D models need facelift and replace: F-14A, F-16A, F-16MLU, F-16 bl.50, F-16 bl.52, F-18A - what are already in the game/sim as AI units. CF-18A/C and other two-seater 3D models also can be easily updated/adopted from current models: F-18B/D, F-16B/D, Mirage-2000D etc. as new AI units. AFAIK M-2000-5 differ externally (for AI) only in the pitot tube/probe and some antennas/sensors on the tail and fuselage. So, it would be only a few 3D-parts-visibility-cosmetics on the current 3D model and should be easily used (same3D model) with changing parts in the liveries-description.lua by the custom_args = function/feature. Same would be true for the F-15C model to get proper Japanese, Israeli, Saudi or older F-15A external model to use in the ME as AI units.
  4. IRL the airframe is not shiny (except: shiny when wet) so... Looks so REAL Nice job
  5. Gotcha, but it's not a problem to export into another game-3D format/extension a DCS-ready "Merged-with-visibility-parts-3D model". MAX can handle those arg-based-visibilities. It's only a hide/unhide/reveal thingy. (a 3D modeller can do it manually as well: without visibilities) So, He can export both: seperated F-104G and F-104S models to FSX, FSXX, SF2, XP etc. formats I am RDY 2 help
  6. Mirage 2000-5 3D model should need minor changes/updates only on the current M-2000 3D model. Same post on Razbam sub-forum:
  7. Well, I have some suggestions to those F-104G/S model(s). As I see there are differences only at the under fuselage twin pilons/launchers and the vental fin(s). So, you (Kobra?) should merge the two model into one where arg70 or other non-dedicated arg# (visibility) will be able to change/visualize those parts through the livery-decription.lua: custom_args = (number/value). Moreover you can build the TF-104G on the model too. Merge all models and add visibility to the different parts and you will save a lot of work and resources.
  8. Yes madam but there is only one F-105 pic what I posted previously. https://www.lockonforum.de/community/thread/1850-eure-schönsten-shots/?postID=84951#post84951
  9. Nice nose-art Jocko: I love that Snoopy Sniper ▲It's from VSN-nice-screenshots pages: (a week old shot) probably another VSN project/mod of CDP-Kobra
  10. AIC: Thud(s) is coming as well, hopefully:
  11. Nice job Jocko ! ...btw: there are a minor problem with the USAF 570914: on the pitot tube the red-white painting should be 4-4 stripes intead of spiral. ...and please make those early/Vietnam/Puerto Rico USAF camos with wavy demarcations as well Thank You
  12. For turning off default markings you should use the official empty.dds (invisible) texture at : nomera, c130-fon+flag and USAF lines - with true "syntax" 4xmpl: {"texture USAF.tga f2 g0", DIFFUSE , "empty", true}; {"texture c130-fon+flag.bmp f2 g0", DIFFUSE , "empty", true}; {"texture nomera.tga f2 g0", DIFFUSE , "empty", true};
  13. Any progress news about that plum blossom eagle skin by Isoko ?
  14. Don't worry, best whiskies are old as well BTW: that movie (Blade Runner) is also one from the best of the best. ...and Sean Young...she is beautiful as always HNY
  15. Awesome: yeah, bigger texture files are causing more and more headaches to people. Common folder usage is the easiest and best way for decreasing memory and storage size: as Megalax posted: those two dots and a solidus do the magic Moreover: as I always said: using textures with mipmaps usually pointless: game/gfx engine starts to use too "early" the half sized mip-textures: fine lines will be invisible too close to the camera (when the camera is moving away from the 3D subject): best/worst example for the Starfighter model is with the italian skins: with those slim and white side/bort numbers. white numbers will be invisible too early/close because of the mipmaps (you can check in the ingame-encyclopedia) +Moreover: ( I do lots of tests over the years: with the current big F-16 and F-14 textures as well) with the current powerful GFX cards the "non-friendly" JPG usage (textures without alpha maps) makes more sense then using 4-8 times bigger DDS files. (especially with small SSDs)
  16. BTW: i guess the underwing fuel tanks are droppable. ..but what about the wingtip tanks ? Are those also jettisonable IRL ? ...and what if the wingtips got rails with sidewinders ? TY
  17. Thanks, ...but I think i spotted another small error. Fuselage-rear-bottom-luminaries should be rotated by 180 deg. AFAIK those lit backwards, so the frontal-half-parts of the lamps should be covered...now on the textures those are reversed.
  18. I did not checked the roughmet but I saw some pics with aircafts that warning arrow point to the lower-rear-fuselage-lamp while on others the arrow point downward near/next to that fuselage-lamp.
  19. About the rear navigation lights: i am confused. Some source mentioning that the rear fuselage lower NAV lights are red on both side and white on both side above. While other source tells both rear-high are yellow and as usual lower-left is red, lower-right is green. Do you know what is the truth ?
  20. OMG, it's xmas time I can't wait , so plz don't wait for the user file section approval (not just because the 3D model is not official but they can be busy ...), ...so, IMHO you should shoot up your amazing skins to google-drive, mediafire etc. if you are ready TY & Happy Holidays 2U
  21. OMG, this will be a ***king extremely detailed livery
×
×
  • Create New...