Home » MODDING HQ 1.13 » Flugente's Magika Workshop » New feature: Arulco Special Division
|
|
|
|
| Re: New feature: Arulco Special Division[message #360320 is a reply to message #360317]
|
Mon, 08 June 2020 07:30  
|
|
| Kitty |
 |
Messages:439
Registered:October 2017
Location: Germany |
|
|
@silversurfer
Hm, maybe we come from different points of view and/or refer to different numbers and therefore find different conclusions.
Therefore I try again. Here is what I think how it works:
Don't know about the code, but the Index-Nr. in Ja2setdat.xml (or ja2set.dat) are connected to the sub-categories in the MapEditor (like ONROOF1 or FIRSTCLIFFHANG).
Those Index-Nrs ain't the same as the TileIndex-Nrs, but connected. The Index 70 (ONROOF1) in xml is starting with TileIndex 1689 and Index 9 (FIRSTCLIFFHANG) is starting with TileIndex 348.
(that's what I meant, when I said, we may refer to different numbers - IndexNr in the Tileset versus TileIndex)
And if a tileset has an index not filled with content, this content then will be used from the Default Tileset (0 for JA2, 50 for UB) instead, so there are no real unoccupied indexes.
But that's nitpicking, I get what you mean.
What I don't know is, can the game place the graphics for the Heli on ground, when in the tileset-definition used for the map the Heli is on roof? I don't think so.
When for example, looking at the Tileset for WF-Airport, the roofbags are at ONRROF2. If they weren't at an index in the category "roof", they wouldn't be on the roof.
At some point, the game needs a definition, where to place stuff and that's the maps, which are based on the content of their Tileset, which is defined in the ja2setdat.xml (or ja2set.dat). At least, that's how I understood (you probably know how this whole worldef.cpp and whatever else is involved are working - I'm only seeing the result).
Like I said, my point of view is from somebody with close to no knowledge about the code. It's based on what I found about Tilesets here and elsewhere in the web and trial-and-error while working with Tilesets and maps.
But at least for the MapEditor, the following seems to be a thing:
Toggle Spoiler
The Index-Nrs in Tilesets are connected to the categories and subcategories used in the mapEditor.
Example: Changes to Index 12 will allways result to changes in subcategory OSTRUCT1 in category Rocks under the Terrain-Tab of the Map-Editor.
If the tileset is used for a map, the changes will be seen on map.
This is true for all Tilesets, here shown at Tileset 0 (Generic 1).
Any Index-Nr not used by another Tileset will use the Index-Nr of the Default Tileset (in JA2 this is Tileset 0, including any custom Tilesets, like the Tilesets 50-59 in JA2).
Like, when a Tileset isn't using the Indexes 0-8, the Ground and Water Textures defined at those Indexes in Default Tileset (0) will be used instead.
If using the UB-exe, the Default Tileset is 50. And only if using the UB-exe. If using Tilesets 50-59 in Data-113 with JA2, the Default Tileset still will be Tileset 0.
<Name>GENERIC 1</Name>
<AmbientID>0</AmbientID>
<Files>
<file index="0">earth.sti</file><!-- Ground Textures Slot 01-->
<file index="1">earth2.sti</file><!-- Ground Textures Slot 02-->
<file index="2">sgrass1.sti</file><!-- Ground Textures Slot 03-->
<file index="3">sgrass2.sti</file><!-- Ground Textures Slot 04-->
<file index="4">grass.sti</file><!-- Ground Textures Slot 05-->
<file index="5">lgrass2.sti</file><!-- Ground Textures Slot 06-->
<file index="6">path.sti</file><!-- Ground Textures Slot 07-->
<file index="7">newbank.sti</file><!-- Water Texture 01, shallow -->
<file index="8">deeplake.sti</file><!-- Water Texture 02, deep -->
<file index="9">cliff_l.sti</file><!-- Banks and Cliffs - FIRSTCLIFFHANG -->
<file index="10">l_cliff.sti</file><!-- Banks and Cliffs - FIRSTCLIFF -->
<file index="11">cliff_sh.sti</file><!-- Banks and Cliffs - (S)FIRSTCLIFFHANG -->
<file index="12">drum_01.sti</file><!-- Rocks - OSTRUCT1 -->
<file index="13">drum_02.sti</file><!-- Rocks - OSTRUCT2 -->
<file index="14">dump.sti</file><!-- Barrels and other Junk - OSTRUCT3-->
<file index="15">mdrock.sti</file><!-- Rocks - OSTRUCT4 -->
<file index="16">montbush.sti</file><!-- Barrels and other Junk - OSTRUCT5 -->
<file index="17">weeds_1.sti</file><!-- Trees - OSTRUCT6 -->
<file index="18">block_01.sti</file><!-- Barrels and other Junk - OSTRUCT7 -->
<file index="19">nogobush.sti</file><!-- Barrels and other Junk - OSTRUCT8 -->
<file index="20">tree1_t.sti</file><!-- Trees - OFSTRUCT1 -->
<file index="21">tree2_t.sti</file><!-- Trees - OFSTRUCT2-->
<file index="22">tree2_t.sti</file><!-- Trees (?) *-->
<file index="23">tree2_t.sti</file><!-- Trees (?) *-->
<file index="24">drum1shd.sti</file><!-- Rocks - (S)OSTRUCT1 -->
<file index="25">drum2shd.sti</file><!-- Rocks - (S)OSTRUCT2 -->
<file index="26">dumpshdw.sti</file><!-- Barrels and other Junk - (S)OSTRUCT3 -->
<file index="27">mdrocksh.sti</file><!-- Rocks - (S)OSTRUCT4 -->
<file index="28">montbshs.sti</file><!-- Barrels and other Junk - (S)OSTRUCT5 -->
<file index="29">weedssh.sti</file><!-- Trees - (S)OSTRUCT6 -->
<file index="30">block_02.sti</file><!-- Barrels and other Junk - (S)OSTRUCT7 -->
<file index="31">nogobuss.sti</file><!-- Barrels and other Junk - (S)OSTRUCT8 -->
<file index="32">trshdwt1.sti</file><!-- Trees - (S)OFSTRUCT1 -->
<file index="33">trshdwt2.sti</file>><!-- Trees - (S)OFSTRUCT2 -->
<file index="34">trshdwt2.sti</file>><!-- Trees - (S) index22 * -->
<file index="35">trshdwt2.sti</file>><!-- Trees - (S) index23 *-->
<file index="36">build_01.sti</file>><!-- Walls - WALL1 -->
<file index="37">build_05.sti</file><!-- Walls - WALL2 -->
<file index="38">build_10.sti</file><!-- Walls - WALL3 -->
<file index="39">build_06.sti</file><!-- Walls - WALL4 -->
<file index="40">door1.sti</file><!-- Doors - DOOR1 -->
<file index="41">door1.sti</file><!-- Doors - DOOR2 -->
<file index="42">door1.sti</file><!-- Doors - DOOR3 -->
<file index="43">door1.sti</file><!-- Doors - DOOR4 -->
<file index="44">door1s.sti</file><!-- Doors - (S)DOOR1 -->
<file index="45">door1s.sti</file><!-- Doors - (S)DOOR2 -->
<file index="46">door1s.sti</file><!-- Doors - (S)DOOR3 -->
<file index="47">door1s.sti</file><!-- Doors - (S)DOOR4 -->
<file index="48">roofceil.sti</file><!-- Rest (roofceil.sti) -->
<file index="49">cracks.sti</file><!-- Debris - ANOTHERDEBRIS -->
<file index="50">roadtile.sti</file><!-- Rest (roadtile.sti) * -->
<file index="51">window1.sti</file><!-- Rest (window1.sti) * -->
<file index="52">walldec1.sti</file><!-- Damaged Walls - DECORATIONS1 -->
<file index="53">walldec2.sti</file><!-- Damaged Walls - DECORATIONS2 -->
<file index="54">walldec3.sti</file><!-- Damaged Walls - DECORATIONS3 -->
<file index="55">walldec3.sti</file><!-- Damaged Walls - DECORATIONS4 -->
<file index="56">w_dec01.sti</file><!-- Wall Decals - WALLDECAL1 -->
<file index="57">w_dec02.sti</file><!-- Wall Decals - WALLDECAL2 -->
<file index="58">w_dec03.sti</file><!-- Wall Decals - WALLDECAL3 -->
<file index="59">w_dec04.sti</file><!-- Wall Decals - WALLDECAL4 -->
<file index="60">floor_1.sti</file><!-- Floors - FLOOR1 -->
<file index="61">floor_2.sti</file><!-- Floors - FLOOR2 -->
<file index="62">floor_3.sti</file><!-- Floors - FLOOR3 -->
<file index="63">floor_4.sti</file><!-- Floors - FLOOR4 -->
<file index="64">flat_r1.sti</file><!-- Roofs - ROOF1 -->
<file index="65">flat_r2.sti</file><!-- Roofs - ROOF2 -->
<file index="66">flat_r3.sti</file><!-- Roofs - ROOF3 -->
<file index="67">flat_r4.sti</file><!-- Roofs - ROOF4 -->
<file index="68">slant_01.sti</file><!-- Roofs - SROOF1 -->
<file index="69">slant_04.sti</file><!-- Roofs - SROOF2 -->
<file index="70">roofvent.sti</file><!-- Roofs - ONROOF1 -->
<file index="71">roofvent.sti</file><!-- Roofs - ONROOF2 -->
<file index="72">highl3.sti</file><!-- Rest (highl3.sti) -->
<file index="73">furn_6.sti</file><!-- Furniture - ISTRUCT1 -->
<file index="74">furn_7.sti</file><!-- Furniture - ISTRUCT2 -->
<file index="75">furn_8.sti</file><!-- Furniture - ISTRUCT3 -->
<file index="76">furn_9.sti</file><!-- Furniture - ISTRUCT4 -->
<file index="77">furn_6.sti</file><!-- Furniture - FIRSTCISTRUCT -->
<file index="78">dirtroad.sti</file><!-- Roads - FIRSTROAD -->
<file index="79">debrocks.sti</file><!-- Debris - ROCKS -->
<file index="80">sblast.sti</file><!-- Debris - WOOD -->
<file index="81">sweeds.sti</file><!-- Debris - WEEDS -->
<file index="82">miniweed.sti</file><!-- Debris - GRASS -->
<file index="83">cracks.sti</file><!-- Debris - SAND -->
<file index="84">twigs.sti</file><!-- Debris - MISC -->
<file index="85">lakeobj.sti</file><!-- Banks and Cliffs - ANIOSTRUCT -->
<file index="86">oldfence.sti</file><!-- Banks and Cliffs - FENCESTRUCT -->
<file index="87">oldfencs.sti</file><!-- Banks and Cliffs - (S)FENCESTRUCT -->
<file index="88">truck.sti</file><!-- Barrels and other Junk - FIRSTVEHICLE -->
<file index="89">truck.sti</file><!-- Barrels and other Junk - SECONDVEHICLE -->
<file index="90">truck_s.sti</file><!-- Barrels and other Junk - (S)FIRSTVEHICLE -->
<file index="91">truck_s.sti</file><!-- Barrels and other Junk - (S)SECONDVEHICLE -->
<file index="92">litter.sti</file><!-- Debris - MISC2 -->
<file index="93">damgdeb.sti</file><!-- Barrels and other Junk - FIRSTDEBRISSTRUCT -->
<file index="94">deb_02.sti</file><!-- Barrels and other Junk - SECONDDEBRISSTRUCT -->
<file index="95">damgdebs.sti</file><!-- Barrels and other Junk - (S)FIRSTDEBRISSTRUCT -->
<file index="96">deb_02s.sti</file><!-- Barrels and other Junk - (S) SECONDDEBRISSTRUCT -->
<file index="97">f_weed.sti</file><!-- Barrels and other Junk - NINTHOSTRUCT -->
<file index="98">montbush.sti</file><!-- Barrels and other Junk - TENTHOSTRUCT -->
<file index="99">f_weeds.sti</file><!-- Barrels and other Junk - (S)NINTHOSTRUCT -->
<file index="100">montbshs.sti</file><!-- Barrels and other Junk - (S)TENTHOSTRUCT -->
<file index="101">rubble1.sti</file><!-- Rest (jsd DestructionPartner >0 and <40) * -->
<file index="102">rubble2.sti</file><!-- Rest (jsd DestructionPartner >= 40) * -->
<file index="103">drum_01.sti</file><!-- Barrels and other Junk - FIRSTLARGEEXPLODEDDEBRIS -->
<file index="104">drum_01.sti</file><!-- Barrels and other Junk - SECONDLARGEEXPLODEDDEBRIS -->
<file index="105">drum1shd.sti</file><!-- Barrels and other Junk - (S)FIRSTLARGEEXPLODEDDEBRIS -->
<file index="106">drum1shd.sti</file><!-- Barrels and other Junk - (S)SECONDLARGEEXPLODEDDEBRIS-->
<file index="107">basefrn1.sti</file><!-- Furniture - FIFTHISTRUCT -->
<file index="108">hilfurn1.sti</file><!-- Generic Furniture - SIXTHISTRUCT -->
<file index="109">furn_6.sti</file><!-- Generic Furniture - SEVENTHISTRUCT -->
<file index="110">furn_6.sti</file><!-- Generic Furniture - EIGHTISTRUCT -->
<file index="111">flat_r4.sti</file><!-- Rest (flat_r4.sti) * -->
<file index="112">flat_r4.sti</file><!-- Rest (flat_r4.sti) * -->
<file index="113">w_dec01.sti</file><!-- Wall Decals - WALLDECAL5 -->
<file index="114">w_dec01.sti</file><!-- Wall Decals - WALLDECAL6 -->
<file index="115">w_dec01.sti</file><!-- Wall Decals - WALLDECAL7 -->
<file index="116">picture.sti</file><!-- Wall Decals - WALLDECAL8 -->
<file index="117">bld_prnt.sti</file><!-- Rest (Bloodstains) -->
<file index="118">m_b_prnt.sti</file><!-- Rest (Bug Bloodstains) -->
<file index="119">switches.sti</file><!-- Wall Decals - FIRSTSWITCHES -->
<file index="120">slant_01.sti</file><!-- Rest (slant_01.sti) * -->
<file index="121">flat_r4.sti</file><!-- Rest (flat_r4.sti) * -->
<file index="122">flat_r4.sti</file><!-- Rest (flat_r4.sti) * -->
<file index="123">smguns.sti</file><!-- Rest (Weapons on map) -->
<file index="124">smp1items.sti</file><!-- Rest (Items on map) -->
<file index="125">smp2items.sti</file><!-- Rest (Items on Map) -->
<file index="126">glashatr.sti</file><!-- Rest (Breaking Glass) * -->
<file index="127">smp3items.sti</file><!-- Rest (Items on map) -->
<file index="128">bod_blow.sti</file><!-- Rest (exploding Person) * -->
<file index="129">exittex.sti</file><!-- Rest (exittex.sti) * -->
<file index="130">steps.sti</file><!-- Rest (Foodprints for Pathways shown) -->
<file index="131">ptrs1.sti</file><!-- Rest (quadrangle Cursors) * -->
<file index="132">ptrs2.sti</file><!-- Rest (some arrow-shaped pointers) * -->
<file index="133">ptrs3.sti</file><!-- Rest (ptrs.sti) * -->
<file index="134">g-run.sti</file><!-- Rest (Run-Icon) -->
<file index="135">g-walk.sti</file><!-- Rest (Walk-Icon) -->
<file index="136">g-swat.sti</file><!-- Rest (Swat-movement Icon) -->
<file index="137">g-pron.sti</file><!-- Rest (Prone-movement Icon) -->
<file index="138">white.sti</file><!-- Rest (Select Icon) * -->
<file index="139">action1.sti</file><!-- Rest (Hummer Icon) * -->
<file index="140">hand-wi.sti</file><!-- Rest (Grab and Open Icon) -->
<file index="141">x.sti</file><!-- Rest (X-Icon - unpassable structure) -->
<file index="142">g-ring.sti</file><!-- Rest (Yellow Ring, placed light Editor) -->
<file index="143">r_key.sti</file><!-- Rest (Key-Icon) -->
<file index="144">sel-ring.sti</file><!-- Rest (Green Ring, placed items Editor) -->
<file index="145">highl3.sti</file><!-- Rest (highl3.sti) * -->
<file index="146">bull.sti</file><!-- Rest (flying bullet) * -->
<file index="147">miss1.sti</file><!-- Rest (richochet bullet) -->
<file index="148">w_miss.sti</file><!-- Rest (bullet impact in water, splashing) -->
<file index="149">ripple.sti</file><!-- Rest (water wave ripples, expanding circles) -->
<file index="150">wirefram.sti</file><!-- Rest (Frame for Wirefences) * -->
</Files>
I'm with you, when you say the Heli can be placed at different places in the Tileset. But I don't think that each and any place (Index-Nr) can be used. Index-Nrs used for GroundTextures, Walls, Furnitures, Rest and Roofs may not work. While most categories under Terrain, like Barrels and other Junk, Rocks, Banks and Cliffs should work (not sure about Trees, I'd rather avoid them for this).
And this "may not work" is realy a "may". I haven't yet been able to produce an ingame situation where I was seeing a landed Enemy-Helicopter at Meduna Airport. Might be because it doesn't work, but might also be that I wasn't at place at the right time, dunno.
But it may just be safer to place this Heli either at the place in Index that WF uses, or replace one of the two drum01 (Barrels and other Junk) in 113.
The definition for ENEMYHELI_BASE_PARKPOSITION used in modsettings.ini also is refering to ground-level, there is no other hight-level mentioned (like ,1). That's why I think this whole roof-thingy might be a little danger prone.
[Updated on: Mon, 08 June 2020 08:10]
How to get: latest 1.13, 7609 and more | 7609 SCI (eng) | Compiling+SVN
I need more details. (Didi Hallervorden) Report message to a moderator
|
|
|
|
|
|
|
| Re: New feature: Arulco Special Division[message #360326 is a reply to message #360323]
|
Mon, 08 June 2020 16:56
|
|
| Kitty |
|
Messages:439
Registered:October 2017
Location: Germany |
|
|
@silverfurfer:
The sector where this is happening, is defined as well.
Out of mod_settings.ini:
[Enemy Heli]
; enemy heli base and park positions
ENEMYHELI_BASE_X = 3
ENEMYHELI_BASE_Y = 14
; If the tileset of the helicopter base contains helicopter graphics, they can appear in the map when they are currently at the base. Use -1 to not use
ENEMYHELI_BASE_PARKPOSITION_1 = 18475
ENEMYHELI_BASE_PARKPOSITION_2 = 18469
; heli teile index in the map tileset (see also HeliSites.xml). In changed maps, you will need at least a map editor to figure this one out
ENEMYHELI_BASE_PARK_TILEINDEX = 1689
And out of the "Enemy Helicopter" Feature Description by Flugente:
"Provided the sector has the correct tilesets, it is also possible to destroy enemy helicopters on the ground if they are parking in their home base. For vanilla maps, I did this by adding the correct tileset to the Meduna airfield (Ja2set.dat.xml, entry 48). This also requires USE_XML_TILESETS to be TRUE."
This aspect of the feature is refering to "enemy helicopters on the ground if they are parking in their home base".
The sector (map) of this home base is defined by ENEMYHELI_BASE. The place where Heli is parking on the ground is defined by ENEMYHELI_BASE_PARKPOSITION. The graphics used for the parked Heli are taken from ENEMYHELI_BASE_PARK_TILEINDEX.
Those definitions are used in a simular way as in HeliSite.xml:
<!--
refuelSector - refuel site coordinates. simular: ENEMYHELI_BASE
refuelHeliTileIndex - 1st Heli tile index number in map tileset.
The 6 heli tiles must be in the same sequence as original, with 3rd & 6th tile offset
by 1 tile to the northeast. simular: ENEMYHELI_BASE_PARK_TILEINDEX
refuelHeliGridNo - Show heli graphics when landed in sector. Require heli tiles in map tileset
to display correctly. Else, will show tiles that occupies the same tile index. simular: ENEMYHELI_BASE_PARKPOSITION
-->
<refuelIndex>1</refuelIndex>
<refuelSector>
<x>13</x>
<y>2</y>
</refuelSector>
<refuelHeliTileIndex>399</refuelHeliTileIndex>
<refuelHeliGridNo>9001</refuelHeliGridNo>
</REFUEL>
<REFUEL>
<refuelIndex>2</refuelIndex>
<refuelSector>
<x>6</x>
<y>9</y>
</refuelSector>
<refuelHeliTileIndex>435</refuelHeliTileIndex>
<refuelHeliGridNo>13067</refuelHeliGridNo>
</REFUEL>
</REFUELLIST>
</HELI_INFO>
So, those changes only take place in a certain defined sector. The landed, parked Enemy Helicopter on ground can only be destroyed in this sector (and when the tileset the sector-map is using contains Heli-graphics at place defined in mod_settings.ini). Therefore there is no need to make adjustments to other maps or tilesets.
After seeing that the HeliTileIndex in Tileset 48 is at a place that the MapEditor (and therefore the map) is using for stuff that is on roof, I asked to make sure if this is nescessary, just to be sure.
A Heli could be placed on roof, but then the definition of the gridNo for placement would require something that tells the height-level as well (like can be done with fortifications-nodes in sector fortification). But since 113-Meduna Airport has no flat roof to land anyway, putting the Heli at a non-roof place in tileset seemed reasonable to me, this will require a little change to a single tileset, while adding a height-level definition to the gridNO probably would require a amount of coding.
But at feature description for Enemy Helicopters, there are also Screenshots of a landed Heli. Given that the settings as of now are used for those, this would strongly support your point, that it doesn't matter at which TileIndex the Heli-graphics are placed. Since I don't know the code, it may be possible that this feature uses mechanisms for placements that differ from those that the MapEditor is using while creating a map.
Geez, anytime I thought to have understood something, there is a twist lurking arround the corner. I'll try some more testplays, to see if I can create the situation with a parked Heli at Meduna Airport.
How to get: latest 1.13, 7609 and more | 7609 SCI (eng) | Compiling+SVN
I need more details. (Didi Hallervorden) Report message to a moderator
|
|
|
|
|
|
|
| Re: New feature: Arulco Special Division[message #360328 is a reply to message #360327]
|
Tue, 09 June 2020 01:08
|
|
| Flugente |
 |
Messages:3509
Registered:April 2009
Location: Germany |
|
|
Eh. If the enemy had helicopters that are currently not flying they are in their base. Now, the intention was that those helis are thus on the ground, so it would be a neat thing to actually see them parked. Additionally we'd be able to destroy them then.
Thus the two grid positions (for up to 2 helis parked) and the tileset index. I recall doing something to the map's tileset to tweak the heli tiles in. Maybe that got changed again over the years, I don't know, but roofs were never a part of this AT ALL.
Hmpf. I guess I have to debug and see whether this still works, and possibly fix it if not.
I know now that it could never work between us, as much as we wanted to, it could never be! Not because you're a rabbit, but because you're black.
If you want, you can donate to me. This will not affect how and what I code, and I will not code specific features in return. I will be thankful though.Report message to a moderator
|
|
|
|
|
| Re: New feature: Arulco Special Division[message #360333 is a reply to message #360328]
|
Tue, 09 June 2020 23:41
|
|
| Flugente |
|
Messages:3509
Registered:April 2009
Location: Germany |
|
|
Well, this is what I get with a normal 1.13 installation, only changes from stock are some mercs that are unrelated to map changes:
USE_XML_TILESETS is TRUE, ENEMYHELI_BASE_PARK_TILEINDEX is 1689. Sooo... I don't know what you're doing, but assume it's not in stock.
I know now that it could never work between us, as much as we wanted to, it could never be! Not because you're a rabbit, but because you're black.
If you want, you can donate to me. This will not affect how and what I code, and I will not code specific features in return. I will be thankful though.Report message to a moderator
|
|
|
|
|
| Re: New feature: Arulco Special Division[message #360412 is a reply to message #360333]
|
Sat, 20 June 2020 23:34
|
|
| Kitty |
|
Messages:439
Registered:October 2017
Location: Germany |
|
|
Well, what initialy bothered me was the placement of the Helicopter in Tileset 48 (Queen's Airport).
The TileIndex used for this feature is resulting in Helicopter.sti placed under the "roofs"-section in section "buildings" of the mapEditor.
I'm not able to build a full Heli with this in the MapEditor, even when I add a building with flat roof.
That's why I was wondering if this would hinder the Enemy/ASD-Heli to be built with this feature.
As it turns out, this concern was unnescessary. The Heli at this TileIndex might be bothersome in the MapEditor, but as far as this feature goes,
the game doesn't seem to care which category in MapEditor is used.
Like Silversurver probably meant, when he said "onroof" is only a name in an enumeration and your pic also is showing.
(although the shadows seems to be missing, which of course won't affect the feature at all)
Pic from MapEditor in stock 113 (8796) with xml-tilesets=true
[Updated on: Sat, 20 June 2020 23:45]
How to get: latest 1.13, 7609 and more | 7609 SCI (eng) | Compiling+SVN
I need more details. (Didi Hallervorden) Report message to a moderator
|
|
|
|
|
|
|
Goto Forum:
Current Time: Sat Apr 20 07:59:36 GMT+3 2024
Total time taken to generate the page: 0.01080 seconds
|
Blog
Search
Help
Members
Register
Login
Home
