Free Allegiance Forums

Change alliance mid-game, how possible is that?

Say there is an alliance between two teams (red and blue), but one team is not doing aswell as the other team (say red is failing), blue can only offer up a certain amount of help without hurting their own eco/offense/D,

Just want to cancel/change alliance, so red now become blues enemy etc...

Since there is only alliance swithces in lobby, are there any chat commands that could be put in?

Redteamchat: Join Alliance Blue/Orange/Green/Purple/Lime = join alliance
Redteamchat: Leave Alliance Blue/Orange/Green/Purple/Lime = leave alliance

???????

Imago wrote:QUOTE (Imago @ Aug 10 2009, 05:20 AM) parci there is nothing wrong with the stock gauges so i suggest you report this to Cort.

I assume it's not a CortUI issue since all works fine with R4 but this is not the case with R5 Beta. It seams like JustifyBottom doesn't work as it should be truncating the top of the image. Instead it cuts the bottom part and lowering it. So something changed between R4 and R5 and broke it.
Also, keep in mind that this is a Software HUD and it doesn't work the same as the Normal style HUD.

Another change that I noticed in R5 Beta is that the energy, hull, ammo and fuel gauges appear transparent (they don't in R4):


Although my HUD looks cooler like this and I like the transparency, there is no reason why it's there in R5. Also, although I use exactly the same commands for hull and shields (GaugeImage with JustifyBottom, etc) they do NOT appear transparent! So something is different with hull and shields gauges. Since my code of the HUD is the same and only R4 changes to R5 I presume that something changed in Alleg code and is the reason for all this.

Also, since I use commands that are used commonly between HUDs and other elements this might also affect more artwork than simply my HUD.

Nevertheless I will also let Cort know about this since he might shed some more light on it's cause.

i'm not making any more code changes to support cortui, cort or yourself can fix them. this is mostly becasue of the complete lack of help i've received from cort who is supposedly on the dev team. delaying the release of R5 because of this would be silly, especially when I'm telling you it's an issue with cortui and not the client. don't make me start fixing cortui as well.

@yiggz: no, just no.

parcival wrote:QUOTE (parcival @ Aug 10 2009, 11:30 PM) Also, keep in mind that this is a Software HUD and it doesn't work the same as the Normal style HUD.

It works exactly the same actually. It's just two names, setting a flag to 0 or 1 depending on what you select. That's all that is different from the client's point of view. The rest is in the MDLs.

parcival wrote:QUOTE (parcival @ Aug 10 2009, 11:30 PM) Another change that I noticed in R5 Beta is that the energy, hull, ammo and fuel gauges appear transparent (they don't in R4) [...] Since my code of the HUD is the same and only R4 changes to R5 I presume that something changed in Alleg code and is the reason for all this.

The transparency handling has definitely changed in R5. As Imago said, I haven't looked into the R5 changes yet so I can't tell you exactly whether it was intentionally changed or caused by one of the DX9 changes.
I'm not sure how it was in R4, but my understanding is that in R5, perfect black (RGB(0,0,0)) is considered transparent, and everything else is not. All your backgrounds are black, so one way you could fix this is changing the color to almost-black (e.g. RGB(0,0,1)). Alternatively, there is some indication in the source that the second parameter of ImportImageFromFile() might be used to toggle transparency off by setting it to 'false', but I haven't tested this.


-- Cort

Cortex wrote:QUOTE (Cortex @ Aug 11 2009, 01:00 AM) I'm not sure how it was in R4, but my understanding is that in R5, perfect black (RGB(0,0,0)) is considered transparent, and everything else is not.

No change from R4 to R5, 000000 is transparent, and my experience is that 030303 is the lowest you could go before breaking the rendering and still get Transparency(dont know why, it just did).
I used 050505 to be on the safe side.

Boy my English sucks

I am not referring to the transparent/black areas around each gauge. These are supposed to be 100% transparent and they are (R4 and R5). I am referring to the non transparent/black pixels of each gauge. Those pixels in R5 appear semi-transparent (I falsely used the word transparent to my previous post). To elaborate:

(the edge of the GT Garrison can be seen even behind the ammo and fuel gauge non-black pixels)

To sum it up, transparent areas are normal and OK. Semitransparent areas have no explanation.

Did some tests and rechecks on my code to clarify this.
There is a difference between hull/shields and the rest of the gauges.
For hull/shields I use ImportImageFromFile.
On the other hand, for thrust/fuel/ammo/energy I wrap the ImportImageFromFile calls into GaugeImageRect calls. The reason for this can be seen here. Basically it's a workaround for an R4 bug that is probably the reason for all this mess. There was a change in the Alleg code by KGJV to fix the exploding pillars bug but I presume this fix caused the falsely truncated from the bottom gauges that are present now in R5.

So, to sum this up for R4:
1) ImportImageFromFile doesn't make the gauge appear semitransparent BUT the gauge image is falsely truncated from the bottom (e.g. when fuel is reduced when boosting or when energy goes down when nanning).
2) Wrapped ImportImageFromFile calls into GaugeImageRect calls are correctly truncated from the top BUT the gauges are appearing semitransparent.


Imago I am sorry to bust your balls on this one. Please free to split this. I also don't expect a fix for R5. It's just that I can't get a normal working version of my HUD since R3 and I am working using workarounds since then...

If i could split all of my replies to you and cort and you and cort's posts to another topic called "Cortex's Cheats for Allegiance" I would. This is a topic regarding the R5 client.... not Artwork.

EDIT:
Also in the topic you linked there is still no Zip file that dogbones requested a year ago. That ould be step #1. Zip up your artwork and make it available. The last thing I want to do, besides working on CortUI, is have to fish around for your artwork. Bump your ORIGINAL TOPIC, by 7zip up your artwork folder and making it available via. a link

Imago wrote:QUOTE (Imago @ Aug 11 2009, 07:07 PM) This is a topic regarding the R5 client.... not Artwork

Although I understand your point of view I have to mention that ImportImageFromFile and GaugeImageRect are used numerous times in dialog.mdl (90+ and 70+ respectively in mine, probably a little less in the default dialog.mdl) in conjunction with GaugeImage and JustifyBottom and this might cause problems not immediately noticed since both methods do not work as they supposed to.

Imago wrote:QUOTE (Imago @ Aug 11 2009, 07:07 PM) Zip up your artwork and make it available...

Done

Imago wrote:QUOTE (Imago @ Aug 11 2009, 07:07 PM) Bump your ORIGINAL TOPIC, by 7zip up your artwork folder and making it available via. a link

and
Done

parcival, seriosuly. now you're just making @#(! up.

GaugeImage is used 30 times in dialog.mdl and ImportImageFromFile is used ZERO. All occurrences of GaugeImage in the vanilla dialog.mdl work as they should. (BECAUSE THEY DON'T USE IIFF)

Please!!!!!!! Go litter CortUI forums with your posts.