Window_Duppel.zip 2024-06-10

This is a CFS3 skins package that was originally posted on the Netwings site. They were intended for stock CFS3 and/or CFS3 with Firepower ONLY. Nothing has been modified in any way and it is still in it's original *.zip file. Here is the README for full acknowledgement:

Window/Düppel Readme
This is the same as the word doc without the jpgs which you can also see in the zip.
First I should mention that I know very little about spawns and how they work, so be warned!
Second all the real work was done by Mathias with some additions by Moi (as Olivier was then known) who did the Wiondows2. Details of the development can be found at
http://www.allensrule.com/cgi-bin/TO...m=1116687219/0
The zip includes the original files from Mathias and Moi with slight alterations in the window.xml and spawn files. In addition there are files named lanc_WI-N and lanc_DU-P which are the Window_2 and Window respective files renamed to fictitious lanc files on the basis that anyone using labels will think they are a/c!
My idea is that mission makers should make their own windows spawns with their own a/c names which can be any fictitious lanc, halibags or whatever, and preferably many different spawns which will keep the player guessing. With this in mind the missions builder should always make these hidden in the mission.
I haven’t really worked out the difference between Window and Window_2 except the latter has bigger files. The 2 missions enclosed use both (Windows_test_WIN.xml = Windows_2 and Windows_test_duppel.xml = Window based spawns)
TO INSTALL
Extract all to a temp folder and then drop the folders into the similarly named folders in your CFS3 install. Alternatively open the folders and copy-paste/drag the contents into the similarly named folders in your CFS3 install.
REQUIREMENTS
The missions use
lanc_ai which is the AI of the FP Lanc. If you don’t have it or don’t know how to make it, open up the mission xml file and replace all lancs with the a/c m3d name of your choice.
Facilities:
gc_flak5.XML
gc_search_flak_2
Frankly I forget where I got those but they are in my earlier Bombers to Hamburg missions so should be around.
Spawns:
Those which are in this zip.
Making your own Window or Düppel
1. Make you own a/c folder and files by changing the name of wither the Window or Window_2 to the new name; for instance Halifax_GT-U. Make sure you go into the aircraft.cfg file and xdp files and change the a/c name to Halifax_GT-U or whatever. (Look at the lanc_WI-N files to see what I mean). Place this folder into your aircraft folder
2. Change the name of the xml file to HaliGTU.xml or something similar . Then using readme or an xml editor, change all the a/c names IN the file to you a/c name (e.g. Halifax_GT-U), A shortcut is to change 5 or 10 and then copy them in to what ever number of a/c windos you want; the original is 40 I think.
Then at the bottom make sure the 3 mentions of “Alt="7000.00" read “7000” or a similar figure. This should be the metric alt at which they ‘should’ spawn!
2, Change the name of the LancDUP.spawns or LancWIN.spawns file to match your new xml file name (e.g. HaliGTU.spawns). Then using a hex editor, go into the spawns file and chance all mentions of DUP or WIN to you new name ending, e.g. GTU.)
3. Place the (HaliGTU).xml and (HaliGTU).spawns files into your spawns folder.
4. Now when you make the mission you do the following
a) Make a facility using “Mission_target_facility_15k” (Mathias used “Mission_target_facility_7k” but don’t ask me what the difference is!)


spawn1.jpg
b) Then Go to the spawn table and choose your spawns file (HaliGTU or whatever). See above.
c) Press the spawn edit and you should see something like this (below)
spawn2.jpg
Here I don’t really know what I am doing but it seems to work if I make “If the player is in the spawn box, chances (%) this spawn is run: 100% “, and also check the box for “ No additional spawn tables will be evaluated” !!!!
d) This shows the same thing for the other spawns.
spawn3.jpg

After that just insert in the usual way! I hope more sense of this will be made after testing and final UL’ing to Netwings and SOH. Meanwhile any queries to the TOW site!​