Jump to content

daddyairplanes

+MODDER
 View Profile  See their activity

  • Content count

    8,632

  • Joined

  • Last visited

  • Days Won

    154

Everything posted by daddyairplanes

  1. great progress next tip: when working without a preset template, do your panel lines first. if you are starting from someone elses skin, it is easier to trace the panel lines first, then have it be the uppermost layer and adjust opacity as needed. where it gets really fun is when you are making the very first skin and place the first panel lines
  2. that is simply awesome
  3. damn, and i just saw an info graphic somewhere today breaking down USAF losses in Vietnam. i remember MiGs being 4%, AAA being 73% and SAMs not being the remaining 23% (it was somewhere in the high teens)
  4. well we have soldiers. and if requested one of our active modelers might be willing to create one if you explain the mission set make a large hit box, low armor, and maybe you could set down "on" the pilot to destroy/pick them up right up the lane of yakarov's Jolly Greens......... would have to be tailor made missions so you dont take off expecting a downed pilot and get a convoy of ZSU-23s instead!
  5. shoot why not just do another install then? customize with things taken out (or placed in) for your tests as needed
  6. much as you wont like hearing it, yes: uninstall it. the pack was made to add missing assets to the game and to set difficulties to be between more realistic (air defenses arent gone in one mission) to criminally insane (the Russian brochure performance for the systems, where you are both super skilled and damn lucky if you survive one mission) many of our mods are not set for making the game easier; rather many modders on here either seek to be historically accurate, add things not available in stock, and make it more challenging besides, if you want to take em all out in one mission, use theold SAC method
  7. aaaand the latest ANG Eagle Guardians
  8. funny thing about TISEO, was developed for a2a work but most utilized for a2g work by the Phantom units that had them. would have been for visual target ID in any case not so much for targeting (you had to get the camera on target for it to be effective, not the camera got pilot eyes on target)
  9. well arent you just the little sarcastic Easter Bunny mandatory screenie, or as said on FB, MiG killer
  10. well complex shape vs regular shape does seem reasonable. still very odd, but as noted before problem solved by shifting tga location. might be showing up inside the model (have seen that plenty too over the years, esp. on transports) but anyone zooming that far in to see the inner walls of the model gets a bucket of rivets and yes, its the C-141B thank you for the input logan!
  11. so i'm working with the FastCargo F-15C from teh superpack. putting wing, squadron and ANG markings on as appropriate to RL. then i notice the intake decals are carrying through to the otherside this is the better version of the problem, i made a patch.tga to put over like i have a few times before. the decals do not smear like when discovered but rather chop off neat and somewhat recessed the patch is solid (100% opacity) and covers the offending tga in LOD viewer grey spot in red highlight near intak openings is the patch decal finally, the patch decal is the last one in the decal.ini, yet doesnt totally cover the offending parts. [Decal016] MeshName=Fuselage DecalLevel=2 DecalFacing=RIGHT FilenameFormat=F15C\110\d\131TFW Position=0.85,-0.175 Scale=0.40 DecalMaxLOD=3 [Decal017] MeshName=Fuselage DecalLevel=2 DecalFacing=LEFT FilenameFormat=F15C\110\d\110tfs Position=0.85,-0.175 Scale=0.45 DecalMaxLOD=3 ...... [Decal024] MeshName=Fuselage DecalLevel=2 DecalFacing=BOTTOM FilenameFormat=F15C\110\d\patch Position=0.0,0.90 Rotation=0.0 Scale=1.75 //DecalMaxLOD=4 already tried playing with decalLevel and DecalMaxLOD levels (thats why its commented out here, best result so far). its odd, but not too bad so far. same lods, same results but i did try this on FC's original F-15C_85 and the F-15C_91 from viper63a's pack. just to see. same result due to arrangements and including Wing Kings, no i cant just put the marking on skin. not to mention those that know me know i dont usually anyhow any ideas on whats up?
  12. Sunday night folks, whats your choice of music hard blues or smooth jazz?
  14. logan, figured as much for the why two sets popped up. seen it all the time in some models in the past, i have dealt with similar issues by using a solid tga to cover what i didnt want seen, what baffles me this time is how that "patch" does not cover the other tga, and how it actually tidies it up. again compare the very first pic (with a patch tga applied) with the third pic (entry for patch removed from ini) yes the issue is resolved my a location change. but for future reference, why didnt a old solution work this time around? example on old solution, without looked like a crazy ex taking a knife to the couches. by comparison this looks like some sheet metal work and new paint over it
  15. decal bleeding im familiar with. a normal fix for me is to throw a patch on, listed further down in the decal.ini. the C-141B in ODS has this issue, each camo skin has a patch laid on to cover up bleed from teh other side (it was only the right side bleeding to left iirc) it stands out, but not too badly if done right and certainly less so than a smearing, bleeding tga however, this is the first time i have seen the patch not work, when made more solid than the other tga and called out after the other tga. also the patch does make the offending tga neater in the affected areas ( third pic in this thread vs first ), which adds to my curiousity
  16. UPDATE: further ini editing has gotten the offending doubles out of sight at least, moving them further back and up. [Decal016] MeshName=Fuselage DecalLevel=2 DecalFacing=RIGHT FilenameFormat=F15C\110\d\131TFW Position=0.375,-0.05 <------------------------------- moved back and up from original Scale=0.5 DecalMaxLOD=3 [Decal017] MeshName=Fuselage DecalLevel=2 DecalFacing=LEFT FilenameFormat=F15C\110\d\110tfs Position=0.375,-0.05 Scale=0.5 DecalMaxLOD=3 while this solves (ish) the issue with the current work, the questoin remains why did it do that?
  17. fro reference, this is with the patch entry removed
  18. i reject your skin and substitute my own as said in the post at the top of this page, doing it abit different (closer but not exact to 3W layout). plus my HANG tail marks are scratch ish made, "HAWAII being typed out and the other marks traced over a blown up decal image (couldnt find one sharp enough to use on its own)
  19. ok other Kevin, Midwest might be looking a little old. ST Louis needs a repainted Arch, some stadiums and alot more liquor stores (at least as i recall driving thru in April) this little $#!% was supposed to be in the Arch photo. friggin wingmen
  20. so, i was today years old when i found out the Hawaii ANG flew A and C models together from 91 until changing for teh Raptor in 09.... explains why C serials were so damn hard to find for them
  21. how does one say "hey Boeing, bite my shiny metal ass" in Russian?
  22. flash back to the infantry Sergeant doing lane trainng at Fort Dix, 2011 "we arent going to show you THE way, we're just going to show you A way. this is your show, we are just sharing our experience to help you all get more gooder."
  23. sorry to hear about the headache, it is looking awesome
  24. i remember having a heart attack at the file size on the first template you sent me to assist with yakarov . but draw big then scale down is an excellent way to go if youre really concerned about space. you lose way less detail shrinking something huge but detailed than trying to upscale somthing small. and if you worry about losing detail, you can go mid way; i've been shrinking alot of files lately from 1024 to either 512 when its simple or 768 when more intricate. but thats not the way, its just a way. you'll find theres many ways to skin a mod Eagle
  25. doesnt have to be. im working a ANG project right now, skin folders are just named teh number of the squadron (110, 159, 199 etc), the textureset.ini (which always stays named just that) opens up to reveal "Name = 131 FW, 110th FS Missouri ANG" etc, its the aircraft that the "whatever_aircraft" folder needs to match "whatever_aircraft.ini" and causes issue in game. the rest of the ini's just need to match whats in that first one and be present in the folder never recall a misnamed folder disappearing a skin. much more common for me is to set up the first skin how i want, then duplicate with intent to open inis and edit. for whatever reason (forgetfulness, have to leave computer for more than 15 minutes whatever) i often go to work on something to discover i might have two "some_skin"s in the dropdown! nothing devastating, just annoying
×

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