Jump to content

Crusader

+MODDER
  • Content count

    4,157
  • Joined

  • Last visited

  • Days Won

    39

Everything posted by Crusader

  1. Green Hell 2

    yep, klasse vid (und mod)
  2. Tornado Package chaff & flares

    zur anzahl der täuschkörper im BOZ107 ... 28 flares chaff... das ding ist ein bulk ( massen) dispenser der das zeugs in aufgerollten langen bändern mitführt... ich hab chaff=300 oder so eingestellt.... sollte genügen anmerkung zu WOI : TK stellt generell die doppelte anzahl der realen menge ein ..... wohl besser für die AI vögel am kanal und über dem Golan... bei WOE v08.30.06 haben A-10 und F-15 noch die reale anzahl. jeder wie er will ... :ph34r:
  3. check the scale ...very "roomy" cockpit :ph34r:
  4. great vid, very cool :ph34r: you should post that at TW forum.. to encourage TK .. hehe.
  5. you are probably using the old version of the terrain editor, the latest version fixed the north-south axis DEM importing error. I started an Aegean Sea terrain long ago ( all lost in HDD crashes ) and had no problems creating a 1000y1000km map with the Aegean Sea in the center. get the latest TE here http://www.thirdwire.com/downloads_tools.htm
  6. AN/ALE-38 bulk chaff dispenser pod, first used in 1972 , also delivered to Israel in 1973 and used by the GAF on RF-4E the AN/ALE-40 system on the inboard pylons came into service in ~1976, chaff only at first, with flares added in 1977 ... so most planes were re-fitted even later TMF has the ALE-38 pod in the "to do" list...
  7. Dropping tanks and racks/ordinance?

    If there’s one word that you typically think of in regards to the Thud, it’s fast. Just how fast could you go off-target? What did it take to get it there? How often did you jettison the external tanks? In 110 combat missions, I can only recall jettisoning tanks about three times in the 105—and one of those was accidental. We almost always brought the tanks home. In the F-4, on the other hand, we jettisoned the C/L tank on every Pack VI mission. We usually brought the outboards back, but on long missions we would get rid of those as well. As for speed, typically 600 into the target area and 600 out. I have seen as high as 750 knots outbound but that was rare. These are knots indicated. Military power—full throttle but no A/B would do 600 easily even with tanks and ordinance. http://www.sponauer.com/rasimus/index.html good book, btw.
  8. I second streakeagle on 95% of all that....
  9. check out latest Mirage Factory weapon pack for SF/WOV/WOE ...AIM-9C inside
  10. New CVN refuel at sea

    can it beat the duracell rabbit ?
  11. Dropping tanks and racks/ordinance?

    theres a huge different in jettision policy of normal day-to-day routine and actual combat. When you read the pilot accounts from DS F-15 pilots, you learn that they generally jettisoned the external tanks before an engagement, at least the wing tanks first, the centerline depended on how the situation developed. One Flight was engaged by SAM, and they jettisioned the wingtanks, out-maneuvered the SAMs, continued the mission, and then dropped the centerline tanks before engaging Iraqi aircraft. From reading various books about F-105's in SEA, it was standard procedure to drop the tanks before bombing the target.( edit: apparently not.. see below.. ) For the MiGCAP/Escort F-4 flights, it was the same. The big 600 gal F-4 centerline tank was a ferry tank by design, with speed and G limits for jettision. It also restricted the use of the 2 forward Sparrows, since they can collide with the tank. I guess all F-4 pilots just liked a clean plane while fighting MiGs... In the 1973 YKW, IDF/AF pilots on CAP jettisioned so many fueltanks after GCI vectors which often lead to unsucessful intercepts that they were told to drop them only if they had sight of the enemy.... they run low on extra tanks so fast that many replacements they used were still painted in red primer.. no time for fancy paint. Soviet and Soviet trained pilots were told by their GCI what to do and when to do it, that included when to drop the tanks...
  12. well, I think you are missing the sound files (and cant hear the engines), and its not a "engines won't start" problem. sounds attached J79sound.zip
  13. ok, np if the editor is run from within the zip, the program is unpacked to a temp directory (usually something like C:\Windows\temp ) in that place the editor "finds" all the needed .dll's to work I guess that you use Win ME or anothe rolder OS... that means you should be able to run the editor normal ( no zip) from a place like C:\Windows\Program Files or just C:\any directory
  14. what OS ? and from which place (HDD) do you try to run the editor ? try following: set the editor to compat. mode use winzip to pack the editor.exe then run the exe from within the zip file ( little trick I learned from 'starfighter2' )
  15. they are for night time photography
  16. what game ? editor version ? WOI needs the latest weapon editor , all other jet games version 08.30.06 the old editor check if you have the correct compatibility mode set (win98/ME)
  17. I think there are 2 versions... J/APR-4 which uses the same screen as the AN/ALR-56 and the advanced version J/APR-4A which has a different screen, square with rounded corners look at the pictures here http://blog.goo.ne.jp/itackey/e/a18d5df927...791957ea03277d0 but I'm not 100% sure... there might be differences between J and DJ models, ect...
  18. check the name of the soundfile and the entries in the soundlis tini, they must be all identical, e.g. : Cannon.wav in sounds folder [soundList] SoundFile001=Cannon <--- ... [Cannon] <------------- Priority=NORMAL Looped=TRUE NumBuffers=4 3DSound=TRUE DopplerEffect=FALSE MaxDist=1000.000000 MinDist=50.000000 InsideConeAngle=360 OutsideConeAngle=360 ConeOutsideVolume=0 then check the name in the gundata ini
  19. yep, Flight folder. check that the numbering sequence is not broken
  20. RF-84F Thunderflash

    LOL, Aldaaaaaaa!!!!1 .. voll krass.. ey!1
×

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