GoldenEye 007 Nintendo 64 Community, GoldenEye X, Nintendo 64 Games Discussion

[Lazlo52]

Wreck wrote:

I'm curious what the "Partial Visibility" means exactly? Is kind of a hard term to quite understand.

I'm sorry, I knew I should have posted an excerpt from my pdactions.ini with it. Here:

Code:

0040.XXXX.YYYY.RR If guard has line of sight to radius Y of Jo, return RR. Can see cloaked player. X affects Y in some way and allows non-line of sight checks? 0041.XXXX.YYYY.RR If Jo has line of sight to radius Y of guard, return RR. Human guards typically have 001E for Y. X affects Y in some way and allows non-line of sight checks?

Its common usage is to detect if the player can partially see the target guard or vice versa. It typically uses 001E to prevent the player from getting a free shot off a guard in cover. I believe I picked up on these actions thanks to Jonathan's action block from The Duel. There, he starts moving either after a timer or when Jo can see him.

I haven't seen any examples of X being used, it's always been 0. When X was a low number, it passed for indiscernible reasons and sparsely, and it shortened the Y radius on the guard. When X was obscenely high, it passed constantly. For now, it's best to keep X at 0. I'm hoping I'll happen upon a block that reveals its secrets.

I suggested the name, "Partial Visibility" because it's concise and gets across the action's intended purpose.
_________________

Quote:

22 not happening nerds. forget about it. 23 til the day i die.

[CrashOveride]

Is it possible to add Collada DAE import to the editor, or is it impossible to do that due to limitations in Obj2an8?
_________________
Playing old, low poly games since 2003

[SubDrag]

Collada is supportable by obj2an8, so I did allow it as a choice now in the editor...however, bear in mind, Collada is a very open spec...and to work right, you need to have your XYZ in the right order, animation euler order, etc.

However, it's there if you want to try it (and you will need a relatively recent obj2an8).

[CrashOveride]

DAE is unavailable as a import option, which is why i was asking.
_________________
Playing old, low poly games since 2003

[SubDrag]

I added it now. Is it still missing anywhere in beta?

[CrashOveride]

Nevermind, updated.
Also the names for matrixes for guard meshes are hard to understand, most people will not know what a shank is.
_________________
Playing old, low poly games since 2003

[SubDrag]

If you have better names can use them. Technically shank is a valid term, I think that list is from Zoinkity originally.

if (command == 0x1) modelPartName = "Waist (complete body)";
if (command == 0x2) modelPartName = "Chest (complete upper body)/autoaim spot";
if (command == 0x3) modelPartName = "Head + collar";
if (command == 0x4) modelPartName = "R bicep (+ forearm + hand)";
if (command == 0x5) modelPartName = "L bicep (+ forearm + hand)";
if (command == 0x6) modelPartName = "R forearm (+ hand)";
if (command == 0x7) modelPartName = "L forearm (+ hand)";
if (command == 0x8) modelPartName = "R hand";
if (command == 0x9) modelPartName = "L hand";
if (command == 0xA) modelPartName = "L shank (+ shin + foot)";
if (command == 0xB) modelPartName = "R shank (+ shin + foot)";
if (command == 0xC) modelPartName = "L shin (+ foot)";
if (command == 0xD) modelPartName = "R shin (+ foot)";
if (command == 0xE) modelPartName = "L foot";
if (command == 0xF) modelPartName = "R foot";

[CrashOveride]

if (command == 0x1) modelPartName = "Hip (complete body)";
if (command == 0x2) modelPartName = "Waist (complete upper body)/autoaim spot";
if (command == 0x3) modelPartName = "Head + collar";
if (command == 0x4) modelPartName = "R Shoulder";
if (command == 0x5) modelPartName = "L Shoulder";
if (command == 0x6) modelPartName = "R Elbow";
if (command == 0x7) modelPartName = "L Elbow";
if (command == 0x8) modelPartName = "R Wrist";
if (command == 0x9) modelPartName = "L Wrist";
if (command == 0xA) modelPartName = "L Thigh";
if (command == 0xB) modelPartName = "R Thigh";
if (command == 0xC) modelPartName = "L Knee";
if (command == 0xD) modelPartName = "R Knee";
if (command == 0xE) modelPartName = "L Ankle";
if (command == 0xF) modelPartName = "R Ankle";
_________________
Playing old, low poly games since 2003

[SubDrag]

OK thanks I updated it.

[Lazlo52]

I've noticed that things that use "Pad centered on" (cameras, turrets) aren't updated when a change in pads/presets causes its number to shift. This potentially makes deleting pads quite a hassle.


Also, Extra Pads can't be deleted from Visual Editor because they're considered path presets, but the Bare-bones option, Undos, and Pads Editor window can delete the Extra Pads. I am 70% certain that it's safe to delete Extra Pads (especially ones we've placed), but...
That being said, can there be an option for Bare-bones to not delete Extra Pads? Their existence is most always beneficial to guard AI, and re-placing them is a tedious task. What's also tedious is placing a bunch in a room only to find out the game isn't using all of them and being unable to quickly delete the few unnecessary ones.
_________________

Quote:

22 not happening nerds. forget about it. 23 til the day i die.

[AL64inthedark]

On my laptop, resolution is too low to display the model editor correctly.

I cannot access to the options that are at the bottom. For some reason the thing to scoll on the side appear only sometimes...and it doesn't work anyway because when sliding down, everything just dissapear.

_________________
Listen to me
https://youtu.be/BzZ3k3NmhLM?t=25m51s

[SubDrag]

I'll try and look into those issues. Pad Centered on, was that both GE and PD?

What resolution is your laptop AL64?

[CrashOveride]

@AL64 are you scrolling all the way down? try scrolling little by little.
_________________
Playing old, low poly games since 2003

[SubDrag]

I think I fixed the PD mode issues (drone gun/camera delete by 1, and the delete extra presets.

[Wreck]

I remembered recently about an object bitflag that we sort of knew what it did in Perfect Dark for a single prop model (the lanterns in Deep Sea), but we didn't pursue it further. This one may have been long overlooked because most testing is done via emulation for convenience. With only certain graphics plugins supporting a crucial detail, it could be totally missed by the player and the emulator.

00000400 00000000 Ignore Clipping Colour

So what this appears to do is keep the model's RGB shading, without the colouring / lighting assigned to the clipping tile it is tied to affecting it. It functions for both GE and PD in the same manner (or similar, as PD also has room lights that could play into things further). I compared a before and after image of my newest custom model imports, and you can definitely see the difference in a side-by-side shot. This could be useful in various situations, such as if the clipping is very dark and your object turns almost black.

I don't know if it completely ignores the clipping tile RGB %100 (perhaps a totally bright red clipping spot could still tint it a bit), so it may need another few tests in other areas of the game.