daddyairplanes

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!

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?

Sunday night folks, whats your choice of music hard blues or smooth jazz?

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

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

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?

fro reference, this is with the patch entry removed

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)

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

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

how does one say "hey Boeing, bite my shiny metal ass" in Russian?

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

sorry to hear about the headache, it is looking awesome

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

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

i just thought of something, given whois askin..... youre not thinking of something like a HA-1262 are you?

you know i liked the idea, although i always thought more in terms of a set of tooling for the Schwalbe was "found" allowing West Germany to build its air force back up quickly. found or maybe bought from Avia, who knows. not advanced like you propose other than using English or American engines as the Jumo were garbage politically, it would have never happened, at least not when the Me262 was a viable airframe. the Aillies were reluctant at first to allow the Germans to equip more than a police force let alone even an obsolete air force. once it became more convienent to allow them to rearm, better still to have them buy English or American than to have the industrial base to go making war again. so if youre going to move forward with a Schwalbe Fenix, scale back some. same airframe, but with say with J33s (should have fit in the engine pods fine being smaller in diameter and length than the Jumos) and Hispano 20mms in place of the original 30mm (ok,s in agreement there). to keep it fairly realistic, the changes to the basic aircraft should be minimal and this should probably be taking place in 1948-49, right after the airlift. the tech and airframe design was too advanced by the time of the Luftwaffes rebirth in 1955 to consider the 262. just my zwei pfenning, love alt history but hate the alien space bats so i try to keep it realistic (what one small thing changed or why did they go the other route?) just to get mind racing sideways, i also always thought about Avia selling Paran the tooling for their C92s, and Paran using them for some years as fighter bombers! edit: yes i know the Jumos wer garbage due to wartime conditions and material restrictions. but once a piece of equipment has a reputation, it take a long time to shake.

reading up this morning, its only supporting 8th gen and higher Intel, similar vintages AMD (didnt pay AMD specs as much mind as i have a personal irrational preference to intel).

where are you reading? what i've read is that MS isnt supporting 32 bit systems anymore not programs. and this has started with Win10 back last year in any fashion, dont upgrade for free and we still got 4 years supported (Win10 end of support slated for Oct 2025), but i think we have longer than that yes, one hopes TK is biding time until 11 is done, then upgrading to that. if not, are you really suprised? if so, damn it'll be time to buy the White album again

the two things i could say are (in reverse order that they popped into my mind) dont save the mission that kills you, replay it or bigger still dont get killed. this is StrikeFighters, not The Edge of Tommorow.

good catch Nyghtfall. my response was my first thought, hadnt looked as deep in the ini yet

did you uncheck RLE compression when you exported the tga? when exporting, make sure that box DOES NOT have an "x" in it. happens all the time if the file size for the affected tga is way smaller than the others, open it, reexport without RLE compression, then close it back out. this issue will do as youre saying, be visible in lod viewer but not in game

FANGs out