[JACK JONES]

Hi. It's my first time with a text opcode and I have a problem:
I'm trying to make exactly the same text in VC when the player is busted so I use this:

CODE

0217: text_styled 'BUSTED' time 5000 style 3

and the text style is identical as in the busting moment but it won't dissapear after 5 sec and it's just standing there forever. I tried clear text, remove text but that didn't help. I also noticed that the other styles are working with time but not style 3. And I know about this too:

CODE

05E0: 0@ = read_memory 0x94AD28 size 4 virtual_protect 0   000A: 0@ += 0x244 // integer values 05DF: write_memory 0@ size 1 value 62 virtual_protect 0

and it's working but now I'm starting to think that these 3 lines were responsible for a strange game crashing in some of my old scrypts so I really hate to use them. So is there some other way to remove style 3 text after a while (besides kiling the player)?

[SilentPL]

SA has an opcode for this, but I think VC lacks it. So indeed, writemem may be the only way.

[krasiejow]

Have you tried to use text style 3 with an empty GXT string? Should remove your text .

[JACK JONES]

QUOTE

SA has an opcode for this, but I think VC lacks it. So indeed, writemem may be the only way.

SilentPL can you tell me why are these addresses causing troubles? I remmember that a few days ago you told me that using them isn't such a good idea. Are you sayng that I shouldn't use them at all or maybe only in some situations?

QUOTE

Have you tried to use text style 3 with an empty GXT string? Should remove your text.

Well not exactly but I tried to put some other style 3 text after 5 sec (both with 00BA and 0217) and that didn't help either - text "BUSTED!" was still there . And I'm using gtatexter for editing gxt files - this tools doesn't allow to create empty text tables.

[krasiejow]

Okay, try this from "documenting memory addresses"

QUOTE

busted / wasted texts in lower right corner, this text STAYS there until you make the first char ZEROED 7917824 > text

7917824 is the memory address in dec, not hex.

[JACK JONES]

I used CE to see the values of that add but there's nothing (only sign ?) It exists only in SA - I need it for VC. But good idea - I'll go to VC/III mem documentation right away.

[SilentPL]

QUOTE (JACK JONES @ Sunday, Jul 15 2012, 10:41)

SilentPL can you tell me why are these addresses causing troubles? I remmember that a few days ago you told me that using them isn't such a good idea. Are you sayng that I shouldn't use them at all or maybe only in some situations?

Address you posted in the 1st post looks alright. The one I said was wrong was pretty high (> 0x02000000). It pointed to custom EXE part, added to HOODLUM EXE to omit SecuROM checks. Thus, this address wouldn't work on any other exe but 1.0 US HOODLUM. That's why it's not a good idea.

[JACK JONES]

QUOTE

The one I said was wrong was pretty high (> 0x02000000).

Interesting. Thanks for the info.