Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dpeters95]

The new structure means that SASEngineMOD 2.7 + Western's Patch is standardised across all modules.  Tiger33's Flybys are hard coded and players should try the Bf109 F4 and the Grumman Duck particularly, it would be good to get more feedback on this too.  Are you all hearing the flybys?.  Other soundsets can be tried as well, without breaking the flybys, just put them inside #WAW above 'Classes-Sound'.

As feedback, I hear the flyby's for both the BF-109 F4, the Grumman Duck and others I have tried using the compressed files from WAW #16...

Dennis

[creature]

Happy Holidays

Thanks for the Christmas present C.U.P.  Team!!!!!!!!

C

[BlackAce7727]

Merry Christmas to all at SAS and the CUP team, I wonder what also the guys have in store? HA-1112 maybe? We will have to see!

[SAS~Monty27]

Merry Christmas to all at SAS and the CUP team, I wonder what also the guys have in store? HA-1112 maybe? We will have to see!

...on the list and moving through the test hangar.  Thanks for understanding that we do this slowly and thoroughly.   

[csvousden]

Monty,

Can the Yak-9B be included?
Yak-9B            air.YAK_9B 1                          NOINFO  r01   SUMMER

CV

[BlackAce7727]

I always knew Monty and your team were the best at this!

[rustydawg]

Thanks for all the work all of you've have done on C.U.P.
I was wondering if your going to add the rest of Dragonfly planes numbered 39 and 42. I looked all over for them but couldn't find them.
Also what SFS file is the Dragonfly 34 and 36a in? I would like to make some skins for them from the skin1o files.


Best regards,

rustydawg

From left to right front row Dragonfly36a, Dragonfly39, and Dragonfly42.

[SAS~Monty27]

The work of Paulus, much of which is in TGA, is indeed superb and I agree we should extend the Dragonfly Series into WAW with the next update.  They would sit very well under 'Prototypes'.

Its very easy to take any normal skin for any aircraft and convert it to the default skin for that aircraft.  The starting point is the new skin, which is then compressed to fit the default aircraft.  When you have made the skins, in the normal way, I will be happy to assist in searching SFS files and fitting it as default or a default option.

[rustydawg]

I'll give it try. I'm not worried about a default skin, I just wanted a choice for different missions. I thought I needed the skin1o.tgb to make a basic skin or void.

I didn't know I could make a skin the way you described it above.

Thank You very much.

All the best,

rustydawg

[SAS~Monty27]

skin1o.tgb is usually too small to work with, its a compressed form of the normal skin 1024.

[rustydawg]

I think the skin for the Dragonfly34 is like the Sky Raider, that has a different set of skins for the wings, and a different set for the fuselage and tail section. This was made from the skin1o.tga! There was no panel lines, I just estimated where the wings were from the panel finder. The skin1o did make a outline of the tail section and stabilizer from the damage. I made a guess where fuselage was and painted the area dark blue, with a light blue grey bottom, but it came out default!

I'll try the Dragonfly 36a and see what happen with it next.

On the Dragonfly34 the wings show the new color but the fuselage stays default.... here's some pictures.



Notice the tail hook is white original it's grey, back ground is white.


I found the spot that has the windshield frame.

[PapaG39]

Happiness is getting all 16 parts of #WAW flowing like a smooth light wind right down the runway on a clear cool day...ha ha

I had to go to my saved clean copy of 1946 from several months ago, but danged if I didn't get all to come together.
I really appreciate this CUP setup.  Even an old fart like me can eventually get it put together correctly...How about that...ha ha...

I really did need to start afresh with a clean copy because I completely screwed up the this last setup...I should know better in my old age to
NOT try and install stuff that doesn't come with a concise file path...otherwise I am sure to put the pieces in the wrong order...hence,  the messed up install...