Jump to content

Leaderboard


Popular Content

Showing most liked content on 01/06/2019 in Posts

  1. 8 points
  2. 6 points
    Go Time! Call Me Ishmael MNF in Lebanon Bird of Prey Firebirds Egress with cover Taking in the view The Oldest and The Boldest
  3. 5 points
    Found this in my YouTube recommendations and thought I should share it.
  4. 5 points
  5. 4 points
  6. 4 points
    Time for some fresh screenies from our favourite, niche WWI flight sim - FE2. Been doing a bit of WOFFing and a lot of ROFing lately on the BootCamp side of the Mac Pro (in Win10), and I'm pleasantly surprised how well FE2 holds up when compared to those sims. It seems that we have FMs now that are close to those in ROF (from what I've been able to compare in ROF), but AI that is closer (more varied) to the one used in WOFF - best of both worlds I think. Thank you modders for your continued work on FE/FE2. Early morning offensive patrol in the pics below, using Stephen's new Galicia terrain (pics. below are on medium settings in WineSkin, by the way, on the Mac side of things). Von S P.S. If you've put in enough "flight time" with the modded FMs in FE/FE2...you shouldn't have any special difficulty flying the FMs in ROF that have often been described as very difficult on full realism settings.
  7. 3 points
    Final update I think, I have been working yesterday on the tracks and I think I got them correct thanks to yakarov79 for his tip.
  8. 3 points
    View File F-101B VooDoo. SF.2 2019 Redux. Reworked pack of F-101B/F VooDoo. Generally old good VooDoo in new dresses. There are some small changes in data.ini files mostly in weapon stations section - so Backup your original file. You might not like it. Pack contains three versions - In reality, IR sensor was applied to different airframes different block build - not really possible to cover in this game engine limits. To make it easier in this game it will be. This is mostly to cover in some right way decals I've made and units. VooDoo '59 without IR sensor - block build 65-96. VooDoo '65 with IR sensor - block build - 100-120. VooDoo '69 ANG - same as 65 - just different set of skins. (I have an additional nation in my install: USA Air National Guard - that's why I have it as a separate model - but in this pack, it is set as USAF bird). All new skins in 3072x3072 resolution. New bump maps and specular maps. also in 3072.. plus more than 1000 decals so the set is again huge after unpacking. Pack contains 17 skins for Air Defense Command - all squadrons that ever used F-101B (from different time periods to cover years of usage). and 7 skin sets for Air National Guard from different time periods. All new decals consisting 451 serial numbers for blocks 65-120. Plus some buzz numbers decals - not all - as Buzzes disappeared in mid 60's. Serial numbers cover B and F models. Backup your original F-101 Folders. Also Decals! Some time ago (long ago) I started to use specific AIR-2 Genie for Voodoo - to accommodate it in weapons bay it is moded as specific stationcode=AIM4 - so to appear this Genie in a game you have to copy weapon AIR-2_Genie_101 also. Genie has new skin. Credits: Original models ErikGen yakarov - skins / decals / some small ini tweak Plane Number (airbrake decal) for 132FIS ANG from original VooDoo pack by Dave. Have Fun. May the VooDoo be with you. Jarek Hereda Submitter yakarov79 Submitted 01/06/2019 Category F-101  
  9. 3 points
    Mike - I had the same problem and fixed it by replacing two groups in the wwiCaporetto_data.INI - [SolidObjectTextureMaterial] and [AlphaObjectTextureMaterial] - with the two shown below. Just copy/paste and it should work. [SolidObjectTextureMaterial] DepthBufferCheck=TRUE DepthBufferWrite=TRUE RenderedInOrder=TRUE AlphaTestEnabled=TRUE CullMode=NO_CULL LightEnabled=TRUE SpecularEnabled=FALSE EmissiveEnabled=FALSE FogEnabled=TRUE AmbientColor=1.000000,1.000000,1.000000,1.000000 DiffuseColor=1.000000,1.000000,1.000000,1.000000 ZBufferOffset=5.000000 BlendOp=BLEND_SRC_ALPHA NumTextureStages=1 TextureStage[01].TextureName= TextureStage[01].MipMap=TRUE TextureStage[01].FilterEnabled=TRUE TextureStage[01].StageColorOp=TEXTURE_MODULATE_DIFFUSE TextureStage[01].StageAlphaOp=TEXTURE [AlphaObjectTextureMaterial] DepthBufferCheck=TRUE DepthBufferWrite=FALSE RenderedInOrder=false AlphaTestEnabled=TRUE CullMode=NO_CULL LightEnabled=TRUE SpecularEnabled=FALSE EmissiveEnabled=FALSE FogEnabled=TRUE AmbientColor=1.000000,1.000000,1.000000,1.00000 DiffuseColor=1.000000,1.000000,1.000000,1.00000 ZBufferOffset=2.000000 BlendOp=BLEND_SRC_ALPHA NumTextureStages=1 TextureStage[01].TextureName= TextureStage[01].MipMap=FALSE TextureStage[01].FilterEnabled=TRUE TextureStage[01].StageColorOp=TEXTURE_MODULATE_DIFFUSE TextureStage[01].StageAlphaOp=TEXTURE Fade=NORMAL StartFadeDistance=50.0 EndFadeDistance=50.0
  10. 2 points
    Gotcha. So, you can do a rudimentary HUD with only rounds showing for your purpose. Problem is it might interfere with your normal gun sight. This is an example that will at least show you your remaining rounds: [HUD] HUDMaterial=HUDMaterial HUDColor=0.0,1.0,0.3,0.8 BoresightOffset=0.0,0.0 ViewportTopLeft=-0.155,-0.195 ViewportBottomRight=0.155,0.210 [HUDMaterial] EffectShaderName=fltHUD.fx DepthBufferCheck=FALSE DepthBufferWrite=FALSE RenderedInOrder=FALSE AlphaTestEnabled=TRUE CullMode=NO_CULL LightEnabled=FALSE UseLightLevel=FALSE SpecularEnabled=FALSE EmissiveEnabled=FALSE FogEnabled=FALSE AmbientColor=1.000000,1.000000,1.000000,1.000000 DiffuseColor=1.000000,1.000000,1.000000,1.000000 ZBufferOffset=0 PriorityLevel=1 BlendOp=BLEND_SRC_ALPHA NumTextureStages=1 TextureStage[01].TextureName= TextureStage[01].MipMap=FALSE TextureStage[01].FilterEnabled=TRUE TextureStage[01].StageColorOp=TEXTURE_MODULATE_DIFFUSE TextureStage[01].StageAlphaOp=TEXTURE_MODULATE_DIFFUSE [HUDFont] TextFontName=Arial TextSize=14 TextBold=TRUE [HUDModeNav] Symbol[01]=HUD_WeaponCount [HUDModeAA] Symbol[01]=HUD_WeaponCount [HUDModeAG] Symbol[01]=HUD_WeaponCount [HUD_WeaponCount] SymbolType=WEAPON_COUNT_TEXT TextPosition=0.0,0.140 HorizontalAlignment=CENTER TextFormat=%01d You'd add this to the bottom of the aircraft's AVIONICS.ini file. Others out there might have better solutions.
  11. 2 points
    Being a bit of a stick-in-the-mud - not an entirely inappropriate condition, for a player of WW1 air combat sims - all the recent modding activity for the Italian front hasn't yet lured me away from my Biggles-based but still dominant affection for the Western Front (all quiet or not). My Jasta 4 Cambrai campaign came to a nasty end when I collided with a comrade attacking the same enemy; first time that has happened in a while. So for a change of pace, I started off an Armchair Aces campaign with KEK Douai in August 1915, flying the Fokker E.I. I'm staying alive and racking up a surprising number of kills, including several on a single sortie. This is all the more surprising because the E.I is a truly awful fighting aeroplane. Rate of climb is nearly non-existent, while turn rate and radius are nearly as bad, with a tendency to judder on the point of a stall at the drop of a hat and to fall into a wild spin if you don't ease back or push the nose down when duly warned. Recovery is do-able but only after a lot of height is lost, so tight turns at low level are right out. Still, the varied and smaller-scale air fights are a lot of fun and modded FE2 brings all its inherent virtues to the party, including the ability to 'warp' and avoid transit flights, the rarity of uneventful, contact-free missions, the reliability of flak in indicating enemies, and the unequalled variety of aircraft types. Here are some scenes from recent missions. Illustrating the continued superiority of FE's pilot animations over all comers, I look down soon after take-off, despairing at why the earth is taking so very long to drop away below me. After finally managing to get above a few hundred meters and reach my patrol area, a more agile French-made and flown Morane 'Bullet' goes down, after I eventually managed to put enough rounds into him. Bringing on your flight-mates is a strong point of FE/FE2, so I am happy to keep watch above, as a comrade knocks down a Vickers two-seater. Not to be left out, on a later flight, I knock down a BE myself... ...and on another mission, I too clobber another hapless Vickers... Sadly, no pics were taken of Nieuport 10s doing what they do best, namely, bursting into flames after a few hits. I think I will edit the campaign files for that period as I am seeing too many of these (the British didn't use them apart from the RNAS near the coast, not where I'm flying, and a handful briefly loaned to the RFC 'for special duties'). And we must by now have shot down an entirely disproportionate number of the forty-nine Morane Bullets produced. The Morane Type L 'Parasol' would probably be a decent substitute for one or both, and I have seen none of these so far. Anyhow, for the sake of historical accuracy, I'm resisting any temptation to put more than two or three Fokkers into the air at once. Thankfully, the equally small enemy flights make this no particular risk, although we have lost one pilot due I think to a mid-air collision. Despite the pretty hopeless performance of our machines, we are usually well able to beat up one enemy flight before moving on to the next. So life with Kampfeinsitzerkommando Douai is pretty sweet...at the moment. And I'm reminded why I still reckon modded First Eagles/FE2 is at least as good, if not better, than any other WW1 air combat sim.
  12. 1 point
  13. 1 point
    Hi Mike, Also check over the following two links that overlap with the good info. Geezer has posted above (should get rid of the shimmering oddities that way): https://combatace.com/forums/topic/91359-airfield-figures-help-wanted/?tab=comments#comment-738584 https://combatace.com/forums/topic/91359-airfield-figures-help-wanted/?tab=comments#comment-738564 Happy flying, Von S
  14. 1 point
  15. 1 point
    I have all three, but I couldn't make any hand at ROF, whatsoever (this is my fault, rather than that of what is an excellent sim, enjoyed by many). So, I removed it from my increasingly-crowded hard-drive. And, while I appreciate the great achievement that is WOFF, I almost always turn to FE2. I couldn't do a mod to save my life, so I can only repeat my gratitude for the work the talented people on here have so generously shared in order to bring this game to its current level of excellence, achieved in the face of such worthy competition. Thanks is also due to TK for providing us with a series of games in which all this has been possible.
  16. 1 point
    I set IAS/TAS 0.488 because I made simulations for 22 km altitude because that's the max alt the missile reaches before diving to target. In SF1 the ASM function is not present so I'm not quite sure how you will simulate the missile. As far as I remember cruise missiles in SF1 use radio command or semi auto command. These types of guidance don't use loft, so you just fire the missile from high altitude and you hope that there will not be mountains between missile and target. Send me your copy of Kh-22 missile and I will make some tests using both ASM and semi auto command.
  17. 1 point
  18. 1 point
    I think these values are quite unrealistic. Let me explain some things taking into account the russian wikipedia: https://ru.wikipedia.org/wiki/Х-22 1. IAS/TAS Ratio has to do with the flight altitude, 0.86 is 10,000 feet (3000m). Maximum range for initial Kh-22 was 300 km when fired from 10-12 km altitude. Shortly after launch the missile climbs to 22 km (75000 ft) and at that altitude accelerates to 3700 km/h (3.5 Mach). So, reaching 585 km at 3000m level flight is even unrealistic for later variants Kh-22M/MA. 2. Maximum speed in your graph is 1447 m/s which is 5200 km/h at 3000m alt. Maximum speed for Kh-22M/MA was 4000 km/h at 22000m. I guess we all know that a missile can fly faster at higher altitudes due to thinner air. So according to this graph the Kh-22 should fly at about 5500-6000 km/h at high altitude! 3. Sonic speed must be set 343 m/s when the missile flies at surface level. The higher the altitude the lower the sonic speed. This changes at 18 km altitude. Higher than 18 km sonic speed starts increasing. This is my effort on how to tweak this missile: However keep in mind that the missile simulator tool calculates speed, range and time for level flight. So at this graph you have a missile reaching 300 km at 0.488 IAS/TAS (22.5 km) altitude. Practically game range should be shorter because Kh-22 is being launched at 10 km alt, climbs at 22 km alt and then at a certain distance from target starts diving. In general, determing the correct values for ASM missiles is more difficult and you need to test missile's performance in game again and again because flight profile of ASM missiles is more complicated. Personally when using this tool to determine values for surface to air missiles I test missile's performance in game again and again. Then according to what I have seen in game I keep working using the range tool until I have achieved the best combination between real values and realistic performance. Unfortunately it's an extremely time consuming process.
  19. 1 point
    Ok, I tried working on the skin to make it look nicer, it is 90% completed.
  20. 1 point
    Excellent work. You put a lot of effort into those skins. For my part, I'm working on a cockpit for the Caudron R11.
  21. 1 point
  22. 1 point
    Hello, all the brothers-at-wings. I present to you a small selection of skins for a wonderful Nieuport-17 by Geezer. This is my first experience that I decided to publish, so please do not judge me very harshly. I do not think that this work deserves to be laid out in the Download section, but I hope someone will like them. In any case, all the credit belongs to Geezer, since I just used his works. So, what's in the archive? The "Dux" folder represents you the most correct type of the Russian Nieuport-17, built at the Moscow Dux Plant. The specific Russian roundels - a distinctive feature of the Dux-built aircraft - were applied in 14 positions. This generic scheme is also well suited for the Nieuport-21, although it needs a small correction (the 'leuvers' drawn on the sides of the aircraft and the elevator control wires do not match). The following three folders represent the 19th Air Squadron (19th Corps Air Detachment or 19th KAO) of the 1st Air Combat Group (1st BAG) - perhaps the most famous aviation detachment of old Russia. 1st BAG fighters had no marked external differences as far as markings were concerned, but the scull of the unit emblem was slightly different on each individual aircraft. A pair of Nieuport-17s represented a staff flight. Capitan (of cavalry) Alexander Kozakov, Commander of a 1st Air Combat Group, flew on a French-built Nieuport-17 in Summer-Autumn 1917. Kozakov’s assistant, pod’esaul (Cossacks sub-Capitan) Shanghin was using a Russian-made aircraft at the time. Since Shanghin kept aloof from his command duties, the actual commander of the 19th Air Squadron was Boris "Bob" Huber. In the "19th KAO" folder is the standard skin, typical of the aircraft of the 19th Air Squadron, where there were aircraft of both French and Russian production. The rudder bore the “Adam’s Head” - the emblem of the 19th KAO. This generic scheme can also be used for Nieuport-21. Finally, the "3rd KAO" folder contains an interesting paint scheme of another Russian aviation unit. It correctly represents the aircraft built in France for delivery to Russia. The Indian’s head was the emblem of the 3rd Air Squadron (3rd Corps Air Detachment). The serial number is fictitious; the colors of the squad emblem are supposedly given. All you need is to simply place the unzipped files in your Nieuport17c folder and start the game. New skins will be available for selection in the Loadout menu. https://oldbrowser.files.fm/u/ga6a2ywd
  23. 1 point
    Mig-21SM Cockpit view... can you spot the other aircraft?
  24. 1 point
    I am still tweaking colours, trying to find better balances. They are something in between Cellinsky's widesky and the stock SF2 colours. Fog colours are a real PITA to get right. My huge thanks to Cellinsky, Stary, PanamaRed, Fubar512, Brain32, ShrikeHawk, BearGryllis, Orsin, luk1978, for their respective mod works! Following screenshots are just a work in progress, not the final quality; for some reason the new night colour seems very dark on screenshot, but in-game the environment is reasonably visible. Day Sunset Dusk Night Overcast Inclement
  25. 1 point
    in my case any way do not work no object nor vertex ((( Working at aircraft stoped.
  26. 1 point
    Actually it is from frame 1-10, frame 0 should be the object without animation keys. the movement is OK the way you describe. Although if you make a search (early warning) radar then simply look at the "spoonrest" or the "flatface" it does not need animation, just in the _data.ini have to define the modelnodename= that should turn (radar entry) and the timing you want. the game engine will handle the rest.
  27. 1 point
    yes, you can make a light rotate (see Stary's lighthouses) you'd need to build in the animation into the LOD, and most likely use a 'self illuminating tga', and the tga for the light beam itself would need creating
  28. 1 point
    down load this, study the entries, adjust as needed for your use. somewhere also is an post about adding smoke to buildings (like powerplant exhaust stacks). that should also have some relevant clues. not sure if one can make a light rotate, but it can be made to blink and the blink rate can vary. best advice until someone else posts
  29. 1 point
    Thanks guys for the replays. Got it fixed. Will pack the RT-33A mod together now. ;-) Ready for download!
  30. 1 point
    Try this link http://www.tailsthroughtime.com/2015/08/canadas-nuclear-strike-force-1st-air.html
  31. 1 point
    we do have a RF nose but the dimensions of it are wrong , i´m currently working on a shorter more correct nose this is the old nose we have , the new one will look much better ( i hope )


×

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