[Black Wolf]

Hmmmm... Visually impressive, if a little odd looking (good Terran Vasudan Fusion though). Those chainguns make it nearly useless in a dogfight (spin up delay and the need to conserve ammo) but I suspect they'd be savage when making runs on capships. A cool little anti cruiser or corvette bomber, and certainly something different. (I've been fiddling with it in FRED - will e-mail you the mission when it's done - probably later tonight if my skill at procrastinating away my assignment time stays in good stead).

[Flipside]

Glad you like Yeah, it is a little 'odd' shaped, if I did it again, I wouldn't make the sides quite so 'square'.

Balancing is a little difficult for the chaingun because of a rearming problem at the moment, 5 of these will severely put the hurt on a Corvette until they run out of Maul ammo, which is about equivalent to 5 Artemis bombers running out of bombs. but until I know what effect re-arming has on the ships performance, it's all guesswork. To be honest, the thing is waay overpowered in the bomb-bay department, but that, to a degree, is where mission design comes in

[Black Wolf]

I'm not getting Overpowered off them. Actually, they're stuggling against a fairly standard Xolotl/Opo pairing. Of course, they probably should be...

[phreak]

Getting these errors when running it through a debug build:

Warning: Model 'Azaes.pof' has 1 dockpoints in model file; models must have 2 dock slots per dock point.
File:C:\projects\fs2_open\code\Model\ModelRead.cpp
Line: 2430
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    model_load()    techroom_select_new_entry()    techroom_do_frame()    game_do_state()    gameseq_process_events()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816fd7()
------------------------------------------------------------------

===============

Warning: Invalid subobj_num or model_num in subsystem 'communications' on ship type 'GTB Azaes'.
Not linking into ship!

(This warning means that a subsystem was present in Azaes-shp.tbm and not present in the model
it should probably be removed from the table or added to the model.)

File:C:\projects\fs2_open\code\ship\Ship.cpp
Line: 5676
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    change_ship_type()    debug_cycle_player_ship()    process_debug_keys()    game_process_keys()    game_frame()    game_do_frame()    game_do_state()    gameseq_process_events()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816fd7()
------------------------------------------------------------------

==========================

Warning: Invalid subobj_num or model_num in subsystem 'navigation' on ship type 'GTB Azaes'.
Not linking into ship!

(This warning means that a subsystem was present in Azaes-shp.tbm and not present in the model
it should probably be removed from the table or added to the model.)

File:C:\projects\fs2_open\code\ship\Ship.cpp
Line: 5676
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    change_ship_type()    debug_cycle_player_ship()    process_debug_keys()    game_process_keys()    game_frame()    game_do_frame()    game_do_state()    gameseq_process_events()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816fd7()
------------------------------------------------------------------

=======================

Warning: Invalid subobj_num or model_num in subsystem 'weapons' on ship type 'GTB Azaes'.
Not linking into ship!

(This warning means that a subsystem was present in Azaes-shp.tbm and not present in the model
it should probably be removed from the table or added to the model.)

File:C:\projects\fs2_open\code\ship\Ship.cpp
Line: 5676
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    change_ship_type()    debug_cycle_player_ship()    process_debug_keys()    game_process_keys()    game_frame()    game_do_frame()    game_do_state()    gameseq_process_events()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816fd7()
------------------------------------------------------------------

==========================

Warning: Invalid subobj_num or model_num in subsystem 'sensors' on ship type 'GTB Azaes'.
Not linking into ship!

(This warning means that a subsystem was present in Azaes-shp.tbm and not present in the model
it should probably be removed from the table or added to the model.)

File:C:\projects\fs2_open\code\ship\Ship.cpp
Line: 5676
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    change_ship_type()    debug_cycle_player_ship()    process_debug_keys()    game_process_keys()    game_frame()    game_do_frame()    game_do_state()    gameseq_process_events()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816fd7()
------------------------------------------------------------------

=============================

Warning: Invalid subobj_num or model_num in subsystem 'engine' on ship type 'GTB Azaes'.
Not linking into ship!

(This warning means that a subsystem was present in Azaes-shp.tbm and not present in the model
it should probably be removed from the table or added to the model.)

File:C:\projects\fs2_open\code\ship\Ship.cpp
Line: 5676
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    change_ship_type()    debug_cycle_player_ship()    process_debug_keys()    game_process_keys()    game_frame()    game_do_frame()    game_do_state()    gameseq_process_events()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816fd7()
------------------------------------------------------------------

==========================

Warning: Ship class GTB Azaes has only 3 points on dock path "Dockpath".  Recommended minimum number of points is 4.  Docking along that path will look strange.  You may wish to edit the model.
File:c:\projects\fs2_open\code\ai\aicode.cpp
Line: 11269
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    ai_execute_behavior()    ai_frame()    ai_process()    ship_process_post()    obj_move_all_post()    obj_move_all()    game_simulation_frame()    game_frame()    game_do_frame()    game_do_state()    gameseq_process_events()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816fd7()
------------------------------------------------------------------

=================================
(This one causes a crash in debug)

Assert: pm1->docking_bays[dockee_index].num_slots == 2
File: c:\projects\fs2_open\code\ai\aicode.cpp
Line: 9749
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
    ai_dock()    ai_execute_behavior()    ai_frame()    ai_process()    ship_process_post()    obj_move_all_post()    obj_move_all()    game_simulation_frame()    game_frame()    game_do_frame()    game_do_state()    gameseq_process_events()    game_main()    WinMain()    WinMainCRTStartup()
------------------------------------------------------------------

[Flipside]

Heh, most of that comes from me forgetting to put the subsytems in

I can add another point to the Dock path, and I'd forgotten about the 'double' needed for Dockpoints to be honest, I can fix those tomorrow and get it re-uploaded.

[phreak]

k thanks flip.  I'll be waiting

[Flipside]

Ok, made the alterations, I'm going to test it out at this end make sure there nothing else lurking and that those fixes didn't somehow manage to get the Support ship working (I don't see how docking code could be related to re-arming in that way, but anything's possible).

I'll let you know how it goes

[Flipside]

Ok, the fixes are in place, and Ive changed the Muzzleflash to a modular version.

http://www.aqsx85.dsl.pipex.com/Azaes.zip

The fixes didn't make any difference to the reloading btw.

[PotzUK]

Oh now that's just plain pretty 

[Col. Fishguts]

Very nice. Are there any builds that can use the -norm map already ?

[Flipside]

Alas, not yet, I just included them because it is pretty certain that they will be needed in the future, so it's easier than having to do a normals pack later.

[Getter Robo G]

Hey Flipside.

  Cute little bugger you got.  Got me thinking from the paneling, would you be interested at a go with a puddle jumper rom SG-Atlantis if you had a high poly model to use as a reference?

OR alternately reduce the poly count of that model (as we have permission to use it)...

Would you be interested in such an attempt?

[Flipside]

I'll have a go at it if you've got a picture/model or something to base it on, I'm usually better at making stuff up than copying other peoples work, but that just means it's all the more useful to get practice

[Tyrian]

I downloaded this a couple of days ago, and I can't get it to work.  I put it in my MediaVP folder, with the -mod MediaVP command line.  It won't show up in game.  What did I do wrong?

[Flipside]

If you're trying to get to it from the tech room, I'm not quite sure, I had the same problem, I put it down to the fact I haven't actually touched the campaign with that Pilot, but really wasn't sure. Can you add them into your own missions using Fred?

Edit : Actually, should have thought of this earlier, since the Autolycus, the other ship I released, doesn't show up and that was pretty much a copy/paste of the Ulysses entry...

[Black Wolf]

The tech database is... weird at the best of times. Some things show up, some don't. The only certain way to make things appear is to put the "tech-add-ships" sexp into a mission in a campaign.

[Tyrian]

I mean it doesn't show up in the ship selection screen.  I can't fly it.  Any ideas?

[Flipside]

If you mean what I think, you'll need to edit the mission to allow you to use them, use the mission loadout editor for that mission in Fred and make a few Azaes available

[Tyrian]

Thanks, Now f1x0R3d!!!

[spartan_0214]

actually, I think that the only mention of the Vasudan sleep cycle is in-game. I looked up in the Tech Room, and it didn't say anything about their sleep cycle. I actually think they sleep longer than humans because of their extended time.