gerwin

Some info is written here: http://combatace.com...n-enemy-forces/ Answers: 1. Because there is no stock red campaign. 2. It represents how much info on that enemy unit will show on the campaign map. Maybe it does more, but I would not know.

I modified a few stock campaigs in order to play the red side with them. Now, when you start the campaign and check the map, you will see that by default the red side has hardly any data on the blue air units. I found out that this can be remedied by adding this line to blue air and ground unit entries Intelligence=XX (with XX being 20 to 80 usually) Now I was excited about the idea of putting Intelligence=100. Because I would like to have some more feedback when an enemy unit was badly shot in previous mission. But even at intelligence 100 it says: unit strength: 15+ (estimated) regardless. Is there any way to show the enemies exact unit strength on the map?

>wonder if it transfers to SF2 tis capablity It does, every stock campaign has it set, but only for the blue side point of view. I was playing operation kadesh last week and got the egyptian airforce in full retreat in the lower left corner of the map. Still every enemy unit said 15+ (estimated) until they seemed to be gone a few missions later. Thus it seems to me the map can only say "healthy unit" and "dead and gone unit", and nothing in between? Which is not much feedback at all. What I would like to see is the enemy unit reading "MiG-15bis; 5+ (estimated) combat ineffective", then thinking: that mast be the unit we decimated last mission. PS. Maybe wooden mockups should be a feature in SF1/SF2 too "You destroyed all primary targets, but it was a failure anyways" ;)

Why then even peek in the dusty SF1 forums? ignore it. ;) Correction: "Backdating" is very much possible (only the the SF2 Exp pack 2 models cannot be ported to WOI 2010)

Impossible to use these LOD models with the 2008 SF1 series. But when you install WOI addon released in 2010 you should be able to to use these LOD's, as well as .DDS and Unicode ini files. (I found only the December 2010 SF2E Expansion pack 2 models, such as the Lightning, cannot be used with the WOI addon game) ...Why are the distance LOD's of the L-39 hardly any smaller then the main LOD?

Wow, a Red-side carrier and Yak-38, should be fun! Any SF2 object can run in SF1 2010 (WOI addon), Textures can always be shrunk by the user to lighter weight. Hi poly models cannot be adjusted by anyone but the author, but usually marcelo Supplies a good set of distance lod's.

How much $$ would you pay? just two figures probably. Normally a program with the same input will give the same predictable output. unless you use certain random number generators. but you can use predictable number generators based on a seed value. So with that settled I would not know what would keep TK's program from repeating a game. It would take effort of course, and I would not care much either.

Considering that, wouldn't it be more worthwile to drop the ambitions for WOI specific speech, and better go for an overhaul of the speech in generic/english. With minimal local accents. One doesn't have to do it all at once, there is wingman 1 then the other flight members, then red crown and such. There is a download for an english speech pack at combatace which replaces some of the wingman speech. It was promising, but the samples are 'clipped', like the recording volume was to high for the sound format used.

Looking at the Alphasim Skyray: it is without any distance lods, without any damage overlays. cockpit and skin folders are a mess. Cockpit textures look nice, but that is all. Not worth paying for it in the past.

Why would that be? I agree .dds is interesting because it has so many subtypes. one of them (8.8.8) basically replacing .bmp But AFAIK both .jpg and .tga still have their strongpoints. .dds is poorly documented, here is some good info though: http://www.poopinmym.../dds_types.html Edit: looking at the link I gave, I don't trust the filesizes he writes down. my .dds files are slightly smaller. So contrary to what it says there I think .dds can do the same as .tga and .bmp with the same filesize.

The problem with this thing is synchronisation with the actually installed aircraft. A lot of the info comes from the game's ini files. It would be better to read it from the actual ini files directy. I noticed kreelin's KMD editor having a parser that does this to some extend. Most beautiful solution would be if TK added a reference section in the game (with a 3D aircraft preview with skin selector :) ). Then every aircraft should also contain an ini file with just a wikipedia like description of the aircraft and tactical advise, which can then be displayed, like F-4E_info.ini. Well the reference can be made as an external program, but then it would not be able to display the aircraft models, at most it could display screenshots made beforehand.

File Name: Damage overlay textures for WOI/SF2 addon Aircraft File Submitter: gerwin File Submitted: 04 August 2010 File Category: Skin Templates Damage overlay textures for WOI/SF2 addon Aircraft version 1.2 by Gerwin 4-8-2010 DESCRIPTION: This pack includes damage overlay textures. These textures show when an aircraft is damaged, showing bullet or shrapnel holes in the surface of the aircraft. These overlays are specific for every aircraft model, and are included in the game for all stock aircraft. But most third party planes come with overlays of inferior quality or non at all. I tried to remedy this for the following aircraft: -F/A-18A by The Mirage Factory and Flying Toaster -MiG-29A by The Mirage Factory and Olivier Anguille (BPAo) -Su-27 by MarcFighter helped by BPAO -F-86F by David Zurawski -F-5E by the Mirage Factory (modeler: BPAO) -C-130A Third Wire Stock SFP1 Aircraft To save time I only made damage overlays for both wings and the main part of the fuselage. CHANGELOG: v1.1, 15-12-2012: added C-130A v1.2, 26-12-2012: improved F-5E INSTALLATION: copy the .dds files to the matching aircraft folder. This folder also contains the aircraft ini file, open this ini file and make sure the following two lines are included: [DamageTexture] DamagedPostFix=_holes.dds ADDITIONAL INFO: This mod was tested on WOI+addon with 2010 patch level. It should work fine in any SF2 game as well. SFP1,WOV and WOE can not use these textures directly, but only after you convert .dds back to .tga with photoshop or something. In that case use: DamagedPostFix=_holes.tga THANKS TO: Third Wire for the Strike Fighters Based Games and the included damage textures that were used as a basis to make the included variants. Click here to download this file

I tried to read a little on this subject, but I find it hard to get some bits of information. I am not sure if the description below is right regarding the engines: -Egyptian Spitfire Mk IXc - Merlin 66 engine - guns: 2x20mm, 4x.303 -Israeli Spitfire Mk IXe [Clipped wings] - Merlin 66 engine - guns: 2x20mm, 2x.50 -Israeli P-51D - Packard V-1650 engine (based on merlin) - guns: 6x.50 In the datafiles the Spitfires both have 980595.5 thrust, the P-51D seems to have a higher value: 1111093.0 Then, It seems the model in the game can also represent a Spitfire XVI with Merlin 266 engine, which is a US build merlin 66. Unfortunately all other spitfire variants show differences with the game model. Was the Spitfire Mk IXc or IXe also exported to the soviet union?, either way I use them over germanyCE this way. Was the P-51D model in the game also used in korea? probably yes.

Thanks for your replies, before I was mainly reading the wikipedia entries. I don't know wheter I will get my hands on these books, I actually did not intend to spend my entire evening reading on the subject in the first place. This mornig I found references that state the Spitfire IXe was exported to the soviet union. In fact the israeli Spitfires are told to be ex-Czechoslovakian examples.

Wings Over Israel Add-On - IS OUT Official webpage

I just installed only the F-5F from your Northrop 2 seater pack. It displays fine. flaps/rudders/airbrakes/destroyed-lod all work. This parameter works for terrains now, or did it already work before? IsraelME.ini: [Terrain] GroundObjectTexture=tan

As mentioned by capun, the 'request help' radio command seems to work now. I did not have any luck with it in single missions but in campaigns I got the response that help would be send.

-The Mystere IV that installs with the addon has skinnable droptanks. So that means it works right?. They jettison properly. -Testing the WOV campaign with the new 2010 binairies, now at mission no 7; it does not give repetative, airfield biased, missions. So far so good. -No sign of RWR symbology working, installing the SF2 F-15A pit gives nothing on the RWR. No dll files containing the word "HighLark" (=RWR Mig-23 family) either.

No, unmodified SFP1/WOV/WOE '06 or '08 cannot read the aircraft model format of the addon planes. But you have a good chance you can just update SFP1/WOV/WOE '08 manually by replacing all dll files and the exe file with the new ones from the addon. After that these games should read the new formats fine. (untested!) Something else, I extracted the A-7D_78 files from SF2E and put them in an aircraft folder in WOI, it worked right away. Did not do any conversions, just copied the files. Makes me wonder if the new drop tank format is also supported natively. Need to try wheter the campaign code was changed to handle WOV better, but this seems unlikely...

I noticed, thanks. So TK could not help working on the engine a little, because most/all dll files are new. Multiplayer is still there. Features ported form SF2: -Destroyed aircraft wrecks. -Can read additional cat file objectdata02.cat. -Can read DDS format damage overlays. -Can read Certain Jpeg files (yet unable to use Jpeg hangar screens?) -Can read Unicode INI files. -Can read Unicode CAT files (cat format v2). -Can read Unicode LOD model format, supposedly allowing importing all SF2 aircraft models (instead of just the few that were still in old LOD format). These SF2 features are NOT present after the addon -corrected F-16A model. -new RWR icons. -userlists. -save single mission. -choose service in single mission. Attached a list of all files included in the WOI addon. ObjectData02.index.txt woi_addon_index.txt

Very common problem. Usually caused by overheating. You might be able to give the card new life by heating up the main chip with a small smokeless torch/lighter. Sounds silly But it worked for me on a geforce Go7600 a few weeks ago.

Nice release again! Distance Lod's, damage overlays, four nice skins - 100% finished.