Leaderboard
Popular Content
Showing most liked content on 06/07/2024 in all areas
-
6 pointsMiG-21F-13 External job is done, now let's go to the cockpit and aft cockpit details, pictures of the aft piping are welcome Not bad for 26k polys me thinks
-
5 pointsMe, think that it might be again confusion in the designation system. Egypt had Mig-21RF - izd.94RA. The first Soviet MiG-21R was izd.03/izd.94R. All exported airframes were designated as izd.94RA -even for Egypt with underbelly fairing for cameras and those for European countries were also izd.94RA. Some airframes of MiG-21R (izd.94R) were upgraded with R-13 engines and then redesignated izd.96R (izd.96 was a prefix for 3rd generation airframes) - those were not for export. As for UB-32. If I remember correctly when carrying a UB-32 and/or 500kg bomb you have to remove part of the gear strut cover. I mean you can try, but I'm not going to say you'd be successful. It's just a matter of what's hardcoded and the like. Do not try to overthink it. You will make additional fuel tanks or something and it still will not be what you need. You can not expect miracles from an old game, Just adjust to what you can do. Tea was working on ODS30AE, we had a lot of ideas, but in the end, we had to make it work with what we had. In the game, for a model, you will use loadout.ini. and more likely there will be an R or D container loaded. Always. Just add a permanent flare dispenser via data.ini. - then it will always work. And If you want to carry a strike mission in R...just add SPS-141 under (also equipped with 2x ASO-2) and all will be fine. Remember this is a game, and in this game, you can not have everything the way it supposed to be.
-
5 pointsWhat if....the USAF had taken on a few F-21's for their DACM exercises?
-
3 pointsSorry for the misunderstanding And the RMAF F1EM VI is also on our to do list
-
2 pointsFunny facts to the east german CLA-87 pods. There were 3 different versions of this pod. One of this pods was to equippe with a videocamera. Small problem: in East Germany was no videocamera available. The own industrie was unable to build one and soviet video technic was crap. So the GDR found a nice solution. They bought some thousand Akai video recorders in Japan, which were sold in TV shops in the GDR. But this was only a coverstory. The real interesse was on a fistfull videocameras from Panasonic. This cameras wer not sold, but installed in the CLA-87 recon pods.
-
2 pointsIt was not a serial production, rather than a 'short run' Additionally you had to put the new electrical wiring in the aircraft, Some Polish Bis, R, and MF were modified. The idea was that any 21 could carry this, as long as it had new wiring for a pod. The principle of using Saturn-2 was that after the reconnaissance run, a pilot dropped a cassette with film over the command position. Pod used diffusion treatment of silver halogen photosensitive materials. The hydrophilic film was exposed at the time of photography and then photochemical processed on board the "plane" in a pod. This shortened circulation time of image information from several hours to about 20 minutes All D, R, and N had ASO-2 dispensers. N additionally had 152(?) illumination flare dispensers. Chechoslovakia also made an additional pod (refurbished D type) for calibrating land-based search radar stations. So technically as long as the pod is carried you can add a flare dispenser into the airframe via data.ini. I would do that, so AI flight and players could use it properly. A very early run of 21R had a pitot tube on the center of the nose LSK modified 21M into reconaisance role, and wingip SPO-3 was a part of modification. And. As I said, some 21R also had FODs, installed Here with N recon pod. Visible Illumination dispensers, and ASO-2 In the center at the pod's rear.
-
2 pointsI think to prepare skins of the USAFE 401 TFW which use the Block 15 F-16A between 1983-1988 from Torrejon AB in Spain. The Light Weight Fighter par excellence !
-
1 pointIron Tadpoles. Intruders of the Vietnam War. Still a work in progress but the first batch of drumsticks is ready. 1965 A-6A VA-75, CVW-7 USS Independence 5.10.1965 - 12.13.1965 A-6A VA-85, CVW-11 USS Kitty Hawk 10.19.1965 - 6.13.1966 1966 A-6A VA-65, CVW-15 USS Constellation 5.12.1966 - 12.3.1966 A-6A VA-35, CVW-9 USS Enterprise 11.19.1966 - 7.6.1967 A-6A VA-85, CVW-11 USS Kitty Hawk 11.5.1966 - 6.20.1967 1967 A-6A VA-196, CVW-14 USS Constellation 4.28.1967 - 12.4.1967 A-6A VA-65, CVW-17 USS Forrestal 6.6.1967 - 9.14.1967 A-6A VA-165, CVW-2 USS Ranger 11.4.1967 - 5.25.1968 A-6A and A-6B VA-75, CVW-11 USS Kitty Hawk 11.18.1967 - 6.28.1968 1968 A-6A VA-35, CVW-9 USS Enterprise 1.3.1968 - 7.18.1968 A-6A, A-6B VA-85, CVW-6 USS America 4.11.1968 - 12.16.1968 A-6A, A-6B VA-196, CVW-14 USS Constellation 5.29.1968 - 1.31.1969 A-6A VA-52, CVW-15 USS Coral Sea 9.7.1968 - 4.18.1969 A-6A VA-165, CVW-2 USS Ranger 10.26.1968 - 5.17.1969 A-6A, A-6B VA-65, CVW-11 USS Kity Hawk 12.30.1968 - 9.4.1969 coming soon...1969 -1973
-
1 pointSAAB/IAI J-35I D'rakon, 170th Squadron "The Orange Tails", 1971 There was already a israeli Draken from me, but I decided to redo it.
-
1 pointanimation 1 is the whole landing gear so i like to avoid that , why dont you edit the cockpit.ini file ??? and link the cockpit animation to the aircraft one
-
1 pointoh, and Kentucky's done. dunno why 822 was special enough for a color cap, but it had it......
-
1 pointthis is a FASCINATING thread! Expecially for those of us in the West. Please keep it going!!!
-
1 pointI made some remarks to show which recon pod belongs to East Germans and which to the Polish. It could be, that the polish pods based on UB-32 pod, while the east german pods were modified UB-16.
-
1 pointThe F1M is the next one on our to do list.
-
1 pointthat is what i have now for the F-16A_B10 , let me know if i missed something
-
1 pointhats off to you sir a USAF wing set can often be hard to pin down. and there's generally more photographers on an air force base than a carrier underway! so i can imagine the fun youre having with that
-
1 pointwell, it all started as skin pack for thirdwire Intruders. And It was nearly done, but then GKABS released his model. So soon after I started to import my work onto new skins for his model. We made some changes, lot of changes to data and now I have bunch of skins for all A-6 deployments during Vietnam War - compatible with my previous work on A-7 and some other ongoing WIPs (full CVW set for specific cruise). It will be available soon, or little more than two weeks. Still researching some serial numbers. Noteworthy is that those camouflaged birds are made via decals, so we have only few birds with famous experimental camouflages within squadron. It is not perfect, but it is good enough in my opinion. You will see. I think I still have some data work to do, just to add more compatibility to A-7, A-4 in matter of MER and TER racks.
-
1 pointThis statement is wrong and true at the same time. Of course this plates were helpfull to avoid FOD. Thatswhy they were refitted also on gunless MiG-21 versions. But the origin of this plates were war experiences. When the MiG was in a close dogfight at low speeds and low altitudes, the plane was flown with a good angle of attack and full afterburner. In such situation the engines needed much more air, than the air intake could deliver. The doors of auxilary air intakes were opend automatically. If in such a situation the gun was fired, the gun smoke had a good chance to were sucked into the auxillary air intakes, which caused compressor stalls and a flame out. The engine died and the pilot had only one choice: to use the ejection seat. During Vietnam war, but also during arab-israeli clashes, some MiG-21 pilots shot down themself by firing the gun during low speed, low level dogfights. The cure of the problem was to add the protection plates, which, as a side effect, were helpfull to avoid FOD. So i have learned the story of the protection plates from east german fighter pilots.
-
1 point
Version 0.3
434 downloads
I tried to implement the exporter only based on the information I found by investigating LOD files. I'm not a 3D Modeler myself. I only tested the exporter with rather simple object (hierarchies). The bottom line is that I have no idea if the exporter works for you. So please give feedback. Note: This plugin requires blender version 2.78 or 2.79. It is not compatible with blender versions 2.8+. 1.) Installation Open the Blender User Preferences - Add-ons Tab (File -> User Preferences... -> Add-Ons) Click "Install from File..." Browse to and select the exporter python script "io_export_sf2_lod.py" Click "Install from File..." (or double click on the script name) In the Add-Ons Tab under Supported Level select Testing and enable "Import-Export: Strike Fighters 2 LOD Exporter" The LOD exporter is now installed and enabled. Under File -> Export you should see the menu item "Strike Fighters 2 LOD (.lod)". It's greyed out until an exportable object is selected. 2.) Usage Select the object you want to export and click File -> Export -> Strike Fighters 2 LOD (.lod) The file browser opens. In the lower left area you see the LOD exporter options: -enable/disable writing the out file (text file with information about the exported object(s)). -enable/disable animation export -allow decals: This option is similar to the option in the original TW-Exporter: "Exporting using AllowDecals=0 causes the vertex to be shared, so it can reduce the size of the .LOD but also causes decals to "bleed" along the edges." This dialog setting is used as default for all objects to be exported. However, it can be overwritten by each individual object via the custom object property "AllowDecals" = 0(false) or 1(true) The selected object and all child objects are exported. Two custom object properties are supported by the exporter: -AllowDecals = 0 or 1, This option is similar to the option in the original TW-Exporter: "Exporting using AllowDecals=0 causes the vertex to be shared, so it can reduce the size of the .LOD but also causes decals to "bleed" along the edges." -UseFlatNormal = 0 or 1, if set to 1 then all vertex normals are pointing straight up (normal = (0,0,1)) in the objects local coordinate system. Please note! The objects must meet the following requirements: -No scaling in the Transform Properties allowed (that means: scale x = y = z = 1.0). If your object has scaling, it should be applied to the mesh (Ctrl-A) Scaling is only allowed for animations. -A material must be assigned to the object. Only the first material of an object is exported. The following material parameters are exported: -Diffuse Color (the lod file format also contains ambient color. Currently the exporter set ambient color = diffuse color) -Specular Color -Specular Intensity -Specular Hardness (I think in 3ds Max it's called glossiness) -if "Shading -> Emit" > 0.0 then self illumination is enabled -Transparency (if transparency is enabled, then the object doesn't cast and doesn't catch shadow. if transparency is disabled, then the object cast and catch shadow. The specific LOD format version the exporter writes, doesn't support arbitrary cast/catch shadow combinations. The other LOD formats I don't understand enough (yet). Sorry!) -Alpha -Mirror Reflectivity -Diffuse texture image name (as diffuse texture the exporter uses the texture where "Influence -> Diffuse -> Color" is enabled) -Normal map texture image name("Influence -> Geometry -> Normal" is enabled and the Normal value is also exported) -Specular map texture image name("Influence -> Specular -> Intensity" is enabled) -Normal and specular map can only be used together with a diffuse map. (If I exported a normal or specular map without diffuse map, then the LOD wasn't shown in the game or the game crashed. I don't know why...) Animation Export: This exporter supports the following object animation types: location, rotation and scaling. Frames 10, 20, 30, ..., 100 are exported as animation 1 Frames 110, 120, 130, ..., 200 are exported as animation 2, ... 3.)Credits: Thanks to logan4 and angelp who provided me with specific lod files that helped me to understand the lod file format better. 4.)Changelog: Version 0.1: -initial release Version 0.2: -bugfix: didn't work in blender version 0.79 Version 0.3: -animation support -added custom object properties: "AllowDecals" and "UseFlatNormal"
-
Popular Contributors
-
1
-
2
-
3
-
4
-
5
-
6
-
7
-
8
-
9
-
10
-
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..