D2Jk Posted July 24, 2014 Hello, It would be useful to see what value an argument is currently holding, but at least A_Print doesn't seem to work too well for this. This code crashes on startup: A_Print(args[3]) And if I write this instead... A_Print("args[3]") ...it will just print "args_3_" in the game. Are there any other options? 0 Share this post Link to post
scifista42 Posted July 24, 2014 Arguments are identified by a name. Don't you give names to the arguments in the script's head definition? Such as:script 1 (int a, int b, int c, int d) {In the code above, d is your args[3]. EDIT: I'm sorry, disregard the above, I thought you were talking about Print in ACS. EDIT2: Well, A_Print can only have 3 arguments, so perhaps you have to call args[2]. Args[0] is the 1st argument. Args[3] would be a 4th one. 0 Share this post Link to post
D2Jk Posted July 24, 2014 Sorry, I meant I was trying to achieve this in the decorate code without using scripts, like so: TNT1 A 0 A_Print(args[3]) // TNT1 A 0 A_Print("args 3 is currently equal to: " + args[3]) Is scripting the only way to do this, then? EDIT: Ok, I've now read your edit above, and tried with args[2], but it crashes on startup as well. 0 Share this post Link to post
scifista42 Posted July 24, 2014 Now I see - my advice above is pretty stupid, because it's not about parameters for A_Print (of course!), but the thing's arguments. Try to pass all A_Print parameters. If you're testing the wad with Zandronum source port, try ZDoom, because Zandronum doesn't support some features (yet). If it fails, I don't know then. I can only recommend ACS script. EDIT: And also, what exactly do you mean by "crashes on startup"? Is there any error message? Is it startup of a map or the whole wad? 0 Share this post Link to post
D2Jk Posted July 24, 2014 It's the WAD that crashes on startup, because of having 'args[2]' inside the A_Print. The error message says it expected a ',' but got a '[' instead. I guess A_Print can only take strings and nothing else? Maybe I'll give this another shot using scripts instead, I'll just first have to refresh my memory on those since it's been a while. 0 Share this post Link to post
scifista42 Posted July 24, 2014 D2Jk said:I guess A_Print can only take strings and nothing else?It's quite possible, the wiki page implies it. Print function in ACS is definitely more flexible. 0 Share this post Link to post
D2Jk Posted July 24, 2014 Now trying with this script:Script "PrintArgument" (int Test) { print (d:Test); Delay(1); } And for testing, I'm using this code in a Ready-state of a weapon: Ready: CHGG A 1 A_WeaponReady TNT1 A 0 A_SetArg(2, args[2]+1) TNT1 A 0 ACS_NamedExecute("PrintArgument", 0, args[2]) Loop The printed message on the screen doesn't seem to update; it prints "0" once, and doesn't come back after it's faded out, despite being continously called in the looped ready-state. Why is this? EDIT 1: Nevermind, suddenly it began working (?). Thanks for the help. :-) EDIT 2: Is it possible to control player's FoV with ACS? 0 Share this post Link to post