Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 ... 3 4 5 [6] 7 8 9 ... 11   Go Down

Author Topic: Curtiss Hawk III Project  (Read 56593 times)

0 Members and 1 Guest are viewing this topic.

agracier

  • Modder
  • member
  • Offline Offline
  • Posts: 3048
    • The Great War in a Different Light
Re: Curtiss Hawk III build: Week 6
« Reply #60 on: April 25, 2012, 03:01:52 PM »

Curtiss Hawk III ????
yes the curtiss hawk. im surprised your against this plane radko, as it did see service in china in WWI
[/quote]

I sincerely doubt anyone is against anything ... there are enough possibilities of misunderstandings when people use emoticons in very short texts ... there is not enough info to understand what is being meant .... and besides, those silly emoticons just invite confusion anyway ...
Logged

Cracken

  • FMB addict
  • member
  • Offline Offline
  • Posts: 285
    • My downloads
Re: Curtiss Hawk III build: Week 6
« Reply #61 on: April 25, 2012, 03:15:50 PM »

I only hope this will not end up as another dead project. Do not assure me it will not, I have seen many promising project sto be abandoned after a few weeks. Please, do not take my comment badly, I pray for this to be finished one day! :)
Logged

mojojojo

  • the only guy who uses the wildcat in multiplayer
  • member
  • Offline Offline
  • Posts: 1368
Re: Curtiss Hawk III build: Week 6
« Reply #62 on: April 25, 2012, 03:31:07 PM »

it will be finished as it is still being worked on very actively. im not sure why you said this, as there are no signs of it ever being abandoned
Logged
i7 4790K quad core 4.4GHz/8GB DDR3-1600/ASUS Z87-A/ EVGA GTX 970 4GB/128GB A-Data SSD+1TB HDD/EVGA 650w 80+ gold PSU/ NZXT Source 530 gaming case

mojojojo

  • the only guy who uses the wildcat in multiplayer
  • member
  • Offline Offline
  • Posts: 1368
Re: Curtiss Hawk III build: Week 6
« Reply #63 on: April 25, 2012, 06:04:09 PM »

@radko,
the whole emoticon thing was a misunderstanding on my part, so please except my sincerest apologies
Joe
Logged
i7 4790K quad core 4.4GHz/8GB DDR3-1600/ASUS Z87-A/ EVGA GTX 970 4GB/128GB A-Data SSD+1TB HDD/EVGA 650w 80+ gold PSU/ NZXT Source 530 gaming case

LiddleMaus

  • Liddle_Maus
  • member
  • Offline Offline
  • Posts: 44
  • First bird gets worm, Second mouse gets cheese!
Re: Curtiss Hawk III build: Week 7
« Reply #64 on: April 30, 2012, 01:42:51 AM »


(Top: FB2C-1 "Goshawk" / Middle: Hawk III 68C / Bottom: Chinese Field Mod)

This week I’ve reach a crossroad. My mesh docs are a mess with parts for different Hawk III’s scattered everywhere. I need to get organized! But before continuing, I will have to separate my docs into 3-4 categories representing the different variants. For starters, I’ve listed the following:

1.   Curtis FB2C-1 --- original navalized variant ordered by the U.S. Navy. Came with tail hook and three hard-points (one in center, two on wings)
2.   Hawk III, Mod 68C --- land variant ordered by the Chinese and Argentines. Minus the tail hook, modified bomb racks allowed for two bombs to be carried on each wing
3.   Hawk III, Mod 68B --- land variant ordered by the Thai and Turks. Similar to the 68C with the exception of cosmetic difference in the gun nacelles.
4.   Hawk IV, Model 79 --- closed cockpit demonstrator. Only 1 was built and that was sold to the Argentines. (It is not likely I will model this variant)

Side Note:
The Chinese converted a number of their multi-role Hawk III’s to true fighters by removing the bomb racks, rear fuselage cover, landing lights and belly-cowl to reduce weight.

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

There are two options I will consider. :-\

Option 1: 4 Slots  ---------> FB2C-1,  Mod 68C,  Mod 68B,  Chinese Field Mod
            
Options 2: 3 Slots -------> FB2C-1,  Mod 68B/C**,   Chinese Field Mod

**Note: Users will have to make changes within their modded install to switch between the 68B and 68C


:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

Conclusion: Need to finish off the wing-tip navigation lights, canopy and wheel doors. Next month, engine and landing gears. See y'all next week.
Logged

LV 426

  • member
  • Offline Offline
  • Posts: 50
Re: Curtiss Hawk III build: Week 7
« Reply #65 on: April 30, 2012, 01:55:56 AM »

it's a wonderful work for a cute aircraft, keep it up, that promise to be a great addition! :)
Logged

Dreamk

  • Modder
  • member
  • Offline Offline
  • Posts: 2020
Re: Curtiss Hawk III build: Week 7
« Reply #66 on: April 30, 2012, 03:57:36 AM »


1.   Curtis FB2C-1 --- original navalized variant ordered by the U.S. Navy. Came with tail hook and three hard-points (one in center, two on wings)
2.   Hawk III, Mod 68C --- land variant ordered by the Chinese and Argentines. Minus the tail hook, modified bomb racks allowed for two bombs to be carried on each wing
3.   Hawk III, Mod 68B --- land variant ordered by the Thai and Turks. Similar to the 68C with the exception of cosmetic difference in the gun nacelles.
4.   Hawk IV, Model 79 --- closed cockpit demonstrator. Only 1 was built and that was sold to the Argentines. (It is not likely I will model this variant)

Side Note:
The Chinese converted a number of their multi-role Hawk III’s to true fighters by removing the bomb racks, rear fuselage cover, landing lights and belly-cowl to reduce weight.

There are two options I will consider. :-\
Option 1: 4 Slots  ---------> FB2C-1,  Mod 68C,  Mod 68B,  Chinese Field Mod
Options 2: 3 Slots -------> FB2C-1,  Mod 68B/C**,   Chinese Field Mod

**Note: Users will have to make changes within their modded install to switch between the 68B and 68C


You need only one slot but with meshes linked to armament array - and hidden/ showing accordingly, as each of your 4 variants is basically identical except for armament and somee optional meshes - look at the java file of the Letov S231 or the D372 to see how it's done - it's quite easy and will simplify your task.
Logged

SAS~Loku

  • SAS Team
  • member
  • Offline Offline
  • Posts: 662
Re: Curtiss Hawk III build: Week 7
« Reply #67 on: April 30, 2012, 04:02:43 AM »

I would complete one basic model first and put it into the game.Making different variants would be easier than adding or removing only small details with help of java.
Logged
P7a/P11c/f/g P24a/b/e/f/g PZL23/42 PWS-10/26 R-XIII RWD-10/14 GeeBeeR1/R2/Granville P-45 , WhippetMkI, Sdkfz-234/1/2, Kurogane, TKS, Wz.29/34 and some other shit XD

Verhängnis

  • Unofficial Heinkel Fan
  • Modder
  • member
  • Offline Offline
  • Posts: 1494
Re: Curtiss Hawk III build: Week 7
« Reply #68 on: April 30, 2012, 07:32:24 AM »

Dreamk, I think it would be greatly appreciated by us all if you could keep some sort of development, or maybe an explanation; in regards to my thread here to perhaps get some sort of 'standard' means of doing slots like this:

https://www.sas1946.com/main/index.php/topic,25119.0.html

 :)

You seem to know what you are talking about in regards to this.
Logged

LiddleMaus

  • Liddle_Maus
  • member
  • Offline Offline
  • Posts: 44
  • First bird gets worm, Second mouse gets cheese!
Re: Curtiss Hawk III build: Week 7
« Reply #69 on: April 30, 2012, 01:57:51 PM »


You need only one slot but with meshes linked to armament array - and hidden/ showing accordingly, as each of your 4 variants is basically identical except for armament and somee optional meshes - look at the java file of the Letov S231 or the D372 to see how it's done - it's quite easy and will simplify your task.


Thanks for saving me the hard work. I've taken a look at the D372 mod folder and see what you are talking about -- though I don't know the right software to open Java files. But at least I've realized that at a later stage I should be able to combine all my meshes to one folder while having multiple FMs.

For now, I’ll stick to keeping parts for four versions. At completion, we'll be seeing three FMs  --> FB2C, 68B/C, China-Mod 
Logged

Kazegami

  • target
  • member
  • Offline Offline
  • Posts: 725
  • Everyone is dumb, but some are dumber than others
Re: Curtiss Hawk III build: Week 7
« Reply #70 on: April 30, 2012, 03:32:53 PM »

though I don't know the right software to open Java files.

You will need to later!
Here's a tutorial and the software you need.
@edit: Dead link removed
Logged
DFTBA

Dreamk

  • Modder
  • member
  • Offline Offline
  • Posts: 2020
Re: Curtiss Hawk III build: Week 7
« Reply #71 on: April 30, 2012, 03:58:48 PM »

Here's a short tutorial

The various subversions of a given plane are defined through their armament array in the main java file of the aircraft, and we use this as a reference to give orders to hide or show meshes accrodingly, when a specific armament is present (= when a given subversion is selected through the armament menu in the QMB).

Here 3 versions "2xVickers" "2xVickers+2PV1" "2xOerlikon" and we want to show accordingly the meshes of 2 guns, 4 guns or 2 cannons
We can add other meshes if we wish, such as a special gunsight for the cannon, or a cockpit blister for one of the version, whatever... the principle is always the same
if...this version  Mesh Visible true  (or false)
The code is as follows (pay attention to teh fact that the conditions,as usual, are defined at the beginning of teh java file, athough the versions are defined at through the armamanent array at the end of the file)

Code: [Select]
public void onAircraftLoaded()
    {
        super.onAircraftLoaded();
        if(super.thisWeaponsName.equals("2xVickers"))
        {
            hierMesh().chunkVisible("WGun1_D0", true);
            hierMesh().chunkVisible("WGun2_D0", true);
            hierMesh().chunkVisible("WGun3_D0", false);
            hierMesh().chunkVisible("WGun4_D0", false);
            hierMesh().chunkVisible("WCannon1_D0", false);
            hierMesh().chunkVisible("WCannon2_D0", false);
            return;
        }
        if(super.thisWeaponsName.equals("2xVickers+2PV1"))
        {
            hierMesh().chunkVisible("WGun1_D0", true);
            hierMesh().chunkVisible("WGun2_D0", true);
            hierMesh().chunkVisible("WGun3_D0", true);
            hierMesh().chunkVisible("WGun4_D0", true);
            hierMesh().chunkVisible("WCannon1_D0", false);
            hierMesh().chunkVisible("WCannon2_D0", false);
            return;
        }
        if(super.thisWeaponsName.equals("2xOerlikon"))
        {
            hierMesh().chunkVisible("WGun1_D0", false);
            hierMesh().chunkVisible("WGun2_D0", false);
            hierMesh().chunkVisible("WGun3_D0", false);
            hierMesh().chunkVisible("WGun4_D0", false);
            hierMesh().chunkVisible("WCannon1_D0", true);
            hierMesh().chunkVisible("WCannon2_D0", true);
            return;
        } else
        {
            return;
        }
    }

then the armament array definitions

Code: [Select]
Aircraft.weaponTriggersRegister(class1, new int[] {
            0, 0, 0, 0, 1, 1
        });
        Aircraft.weaponHooksRegister(class1, new String[] {
            "_MGUN01", "_MGUN02", "_MGUN03", "_MGUN04", "_CANNON01", "_CANNON02"
        });
        try
        {
            ArrayList arraylist = new ArrayList();
            Property.set(class1, "weaponsList", arraylist);
            HashMapInt hashmapint = new HashMapInt();
            Property.set(class1, "weaponsMap", hashmapint);
            byte byte0 = 11;
            String s = "2xVickers";
            Aircraft._WeaponSlot a_lweaponslot[] = new Aircraft._WeaponSlot[byte0];
            a_lweaponslot[0] = new Aircraft._WeaponSlot(0, "MGunBrowning303k", 500);
            a_lweaponslot[1] = new Aircraft._WeaponSlot(0, "MGunBrowning303k", 500);
            a_lweaponslot[2] = null;
            a_lweaponslot[3] = null;
            for(int i = 11; i < byte0; i++)
                a_lweaponslot[i] = null;

            arraylist.add(s);
            hashmapint.put(Finger.Int(s), a_lweaponslot);
            s = "2xVickers+2xPV1";
            a_lweaponslot = new Aircraft._WeaponSlot[byte0];
            a_lweaponslot[0] = new Aircraft._WeaponSlot(0, "MGunBrowning303k", 500);
            a_lweaponslot[1] = new Aircraft._WeaponSlot(0, "MGunBrowning303k", 500);
            a_lweaponslot[2] = new Aircraft._WeaponSlot(0, "MGunPV1", 750);
            a_lweaponslot[3] = new Aircraft._WeaponSlot(0, "MGunPV1", 750);
            a_lweaponslot[4] = null;
            a_lweaponslot[5] = null;
            for(int j = 11; j < byte0; j++)
                a_lweaponslot[j] = null;

            arraylist.add(s);
            hashmapint.put(Finger.Int(s), a_lweaponslot);
            s = "2xOerlikon";
            a_lweaponslot = new Aircraft._WeaponSlot[byte0];
            a_lweaponslot[0] = null;
            a_lweaponslot[1] = null;
            a_lweaponslot[2] = null;
            a_lweaponslot[3] = null;
            a_lweaponslot[4] = new Aircraft._WeaponSlot(1, "MGunMadsen20", 60);
            a_lweaponslot[5] = new Aircraft._WeaponSlot(1, "MGunMadsen20", 60);
            a_lweaponslot[6] = null;
            a_lweaponslot[7] = null;
            a_lweaponslot[8] = null;
            a_lweaponslot[9] = null;
            a_lweaponslot[10] = null;
            for(int k = 11; k < byte0; k++)
                a_lweaponslot[k] = null;

            arraylist.add(s);
            hashmapint.put(Finger.Int(s), a_lweaponslot);
            s = "none";
            a_lweaponslot = new Aircraft._WeaponSlot[byte0];
            for(int l = 0; l < byte0; l++)
                a_lweaponslot[l] = null;

            arraylist.add(s);
            hashmapint.put(Finger.Int(s), a_lweaponslot);
        }
        catch(Exception exception) { }
    }
}
Logged
Pages: 1 ... 3 4 5 [6] 7 8 9 ... 11   Go Up
 

Page created in 0.047 seconds with 26 queries.