yakarov79

View File F-4D Phantom II in ANG Service. This is a skin/decal set for Phabulous Phantom. Basic modding skills are required to run this mod. (copy/paste, mod folder structure etc.) Pack contains skins and decals representing all F-4D users amid Air National Guard units. Skins are made for stock F-4D_78. F-4D was used between 1977 -1990 in ANG and these skins are fitting in 13 years of service. Mostly all serial numbers are correct for specific dates and units. If you will find some errors please feel free to send correction notes. No ini files for this as this is only skin sets. Just simply add skin folders to your favorite F-4D_78. Or create a new, specific one for ANG use. You will find that some aircraft wear kill marks as in real life. If you want to have your own kill marks you have to modify decal.ini file. To fully enjoy this skin set you need to have ThirdWire F-4D_78. All skins are done in 2048x2048 based on Sundowners and Ravenclaw's work. Brand new Bump files in 2048x2048. All decals made by me. Enjoy. Regards. Jarek Hereda Submitter yakarov79 Submitted 05/16/2020 Category F-4  

it is on my long to-do list.

Use sundowners templates - works better for C/D. I am using for D Sundowners with chopped Ravenclaw's bits from E. ANG research is a pain in the ass especially the late 70s early 80s....I did recently all Phantom D ANG squadrons. Some years show usage of 2-3 schemes at the same time. are you doing Hawaiian 199th ? As far as I remember they were using standard SEA, SEA wraparound and ADC grey at the same time. Even if it was TFS its main role was air defense may be a reason for keeping ADC grey on many aircraft. I found a picture from 1984 still with standard SEA. But haven't seen (or do not recall) seeing Hawaiians in Hill grey.

the white top of the pilots cabin would be more royal-transport-commandish. Transport command didn't recognize this pattern as a specific desert pattern..as it was the only pattern they used until the mid-70s.

all ways are good. One way or another... But If you will clone and rotate, your 'new' object will have rotated pivot points...(not important in this particular object but still) yes you can rotate via element but if your object has few elements..then rotating this way is futile. if you will clone and mirror... your new object will have rotated pivot points also...plus fliped polys. - of course, you are flipping it..but still...(again not important here) If you will use symmetry pivot points remain the same all the time. Not important here...but in some other model might be useful.

For some time already I have been working on KC-10 tanker. I think I have started this project in 2017. But as expected I can easily find interest in other projects, so this one was not so top priority. Recently - accidentally I have opened a folder named DC/KC-10. And I faced a dilemma to do or not to do...now. So I decided to put it on another hiatus. But hey...there might be some other option. The model is not 100% finished. I still need to model front gear (on the picture below there is front gear visible - but this is just resized copy of central gear.) and crew cockpit and some small bits. The overall model is animated and mostly UVW mapped. I think only the refueling boom needs to be mapped. What I am looking for? Someone - person or team of CA users who will do some skinning work. I can provide with lod and UVW layout. Of course, lod viewer might be helpful. From my own experience, I know that sometimes UVW mapping needs to be changed during the process of creating a skin. This is not an issue. Even if for now I have no intention to focus on this model I might still have a chance to do some changes if necessary. As you can imagine model is quite big, but not huge. Model is UVW mapped on 6 bitmap sheets. SO we can expect some quite reasonable and decent level of detail. If you know my previous work you should know what to expect (and what I expect) from the skin. Generally, this is a tedious job to paint panel lines, rivets, details, etc. But we are not gonna count rivets. But a decent level of detail is possible. We do not need to create skins for countries, air forces and all that stuff. First good base skin needs to be created. All colorful work, decals, users, etc is a song of the future. Time here is not an essence so time schedule is quite flexible. No need to hurry. But If you want new KC-10 in-game..then some work needs to be done. Somehow, someday. Maybe skin will be done while I will not have a chance to work on the model...but still, this is progress. I do not expect that crazy mob will run toward this project...as this is just a useless tanker. But maybe someone would like to gain some skills - as I point this message mostly to young users here at CA. Here is your chance to start to do some modding. Of course, you will need to have gimp, photoshop or similar graphic editor. And of course, the will to participate in this project is needed. I do not want to force someone to do that or put pressure. I can provide reference photos, tips and general support. Perhaps some other reference would need to be researched. Another thing is that I never (yet) exported this model into the game - so some data.ini work is needed also. And here is a sample of layouts. I know that you old farts CA modders are quite busy with your own projects. But as I said before I am hoping that some new users will have a will to participate. Anyway. We will see.

As soulfreak said this pod TIALD is only for left LID station in British Harrier GR.7 and 9. The model is intended to use only on that station, not on wings. Modder should limit that weapon and weapon stations by specific station code...but it was a long time ago and many things happened since then. Another thing is Marine Harrier can not carry TIALD. But this applies only to fetish and orthodox players. AN/AAQ-28 should be more appropriate.

Nope. or you can add lights via effect emitter. In this case, the effect is quite cool but it does not really give illumination ahead...rather than glowing bulb ...but looks better than those tgas shaped into light cones. (or maybe someone can work on emitter effect that will give proper light effect) I am using one of the aircraft carriers emitter effects. during the day... and night...

better to use symmetry. make a wheel , resetxform, uvmapp, set pivot point to X=0, apply symmetry on x axis. then again symmetry on y axis. You have 4 wheels. fast and easy.

Nope. It is already in the freezer. Not gonna bother me now...one day perhaps.

must be part of model...no animation, only movement via pitch and yaw of mesh... no as far as i know...it drift left or right but no steering as we know it... only animation for a ground object is reload animation I think...(not even sure if it works) Nope. You can add 'tga lights' like me or killerbee added to flightline objects...but the thing is it will appear 24h .....so no point really.

does not matter. assign a different material to wheels only. if you clone and then mirror etc...and then resetXform..you have to flip polys.

did you try to assign different material for wheels ? wheels are editable poly or mesh?

exactly. was about to say the same thing. SF1 ini

I am lost .. those are just normal pilots from a pilot folder? the maybe create new aircraft component in data ini [AircraftData] EmptyMass=10900.0 EmptyInertia=197413.39,30260.70,203674.09 ReferenceArea=38.00 ReferenceSpan=11.10 ReferenceChord=3.71 ReferenceLength=17.32 CGPosition=0.00,-1.20,0.15 UseMetricUnit=TRUE Component[001]=Fuselage Component[002]=Nose Component[003]=LeftWing Component[004]=RightWing Component[005]=LeftStab Component[006]=RightStab Component[007]=LeftVertTail Component[008]=RightVertTail Component[009]=LeftOuterWing Component[010]=RightOuterWing Component[011]=placeforpilots then that component... [placefor pilots] ModelNodeName= ShowFromCockpit=FALSE MassFraction= HasAeroCoefficients=FALSE CLa=0 DamageRating=DISABLED SystemName[001]=pilot SystemName[002]=copilot

yes and for example 4 dig counter in cokcpit ini. [RadarAltimeter] Type=RADAR_ALTIMETER CounterNodeFormat=RADalt_dig%d MovementType=ANALOG_COUNTER ValueUnit=FEET represent those 4 nodes linked to one parent mesh. Altimeter_box [144 polys, 160 verts] '03' RADalt_dig1 [20 polys, 40 verts] '21b- Default' RADalt_dig2 [20 polys, 40 verts] '21b- Default' RADalt_dig3 [20 polys, 40 verts] '21b- Default' RADalt_dig4 [20 polys, 40 verts] '21b- Default' important is meshes should have names ended by dig1, dig2 dig3, dig4 last number on counter is dig1 where a higher dig(4/5/6) is the first number on the counter

good idea... It all also depends on the damage model of particular aircraft.

One of the most common missiles launched at me. Somehow easy to avoid if you are fast...but if few appear in area...It is getting harder. Very effective against slower aircraft. The only issue is that often fires at targets at maximum range...so effective shots decrease as it is easy to avoid.