Lost with Python

[Valdez]

Well, Python has once again left me clueless. I don't even know how to start a Python file let alone coding it. Right now I am just working on clickable objects with the writer's tutorial. But now it seems I need a new python file. I have Python 2.5 installed, I just don't know where to begin. Can someone please help me or lead me to some inforamtion on this? I would REALLY appriciate it.

[Goofy]

I know where your coming from. Everytime I even look at python I get a headache. Trying to remember where everything goes or to put what in what file makes my head spin. I just decided to get my modeling and texturing down first then if that doesn't melt my brain(which its getting close to) I'd give the coding part a try.

[andylegate]

There are several ways you can go about it, but first: it depends on why you need the Python in the first place. In other words: What are you trying to do?

Have a journal work?
Have a linking book work?
Have an object move?
Trying to do something with cameras?

You can come here and ask someone if they have a python file that will do these things. If you are looking into Journals and Linking books, I recommend D'Lanor's Template. The files are already coded for you, you just have to go in and change certain things in it, and D'Lanor shows you where in the template.

Other things are a bit more difficult, but there are many, many people on here that would be glad to help you, if you but ask.

[Valdez]

Ok then, what I am trying to do is have a clickable button that when pressed triggers a NPC voice. I already know how to set up emitters and I know how to do that part but I don't know what the code means by 'pythonfile:' I do know it is asking me for a .py file, but I do not know how to create or how to set it up and WHAT to code to trigger stuff. Is it actually nessasary to have a Python file (besides the optional character animation) for a button that triggers a .ogg? I would really appriciate it if you could help me. And I can give any extra information if I did not give you enough since I seem to never do that.

Thanks,

Valdez

[andylegate]

A clickable needs a Python file, IF you are using python to do something. Technically, if all you are doing is having a button that clicks, with avatar animation, and a sound played, and that's ALL, you don't NEED a python file at all. All you need is ALCscripting!

You would use a python file to say....delay the sound, or move the button, or to have that action make a mesh move (because right now the only way to get meshes to move is with a python file).

But if all you are doing is having a sound play, then, no you don't need a python file at all. Just remove that part from the ALCscripting, and you should be fine.

[Valdez]

Well, it exported correctly but it isn't clickable. I know I put all the alcscript in right and I postitioned it right. I have been checking my work with the tutorial and it seems to be right. I checked the post earliar about things not being clickable, but he was using python. Will I need it after all? And what are some common things to look out for? If you must see my AlcScript for it here it is:

Code: Select all

# insert AlcScript code here

FootStepRgn_grass:
   type: region
   regiontype: footstep
   surface: grass
      
Button_Decals:
   physical:
      pinned: true
   quickscript:
      simpleclick:
         region: Decal_Rgn_click
            
Button_Decals:
   physical:
      pinned: true
   quickscript:
      simpleclick:
         region: Decal_Rgn_click
         soundemitter: sound_emit_decals
            
sound_emit_decals:
   type: soundemit
   sound:
      file: DecalKate
       volume: 1.0
      type: NPCVoices

Is there something wrong there? If you need anymore information, like always, I will give it to you.

Thanks,

Valdez

[Trylon]

I see you have "Button_Decals" declared twice. I don't know how that affects the script processing, but iit is quite possible that it only looks at the first declaration, which is not set to trigger a soundregion.

Code: Select all

Button_Decals:
   physical:
      pinned: true
   quickscript:
      simpleclick:
         region: Decal_Rgn_click
           
Button_Decals:
   physical:
      pinned: true
   quickscript:
      simpleclick:
         region: Decal_Rgn_click
         soundemitter: sound_emit_decals


[Valdez]

Oh! I have to bind the sound emitter with the first one! I see. Well I am going to see if that works.

[Valdez]

It was probably good I got rid of it and you were right about it not mattering for it still is not clickable. This is what my screen looks like in Blender, parts of the button have been listed for your convienience.

http://www.photoshack.com/displayimage.php?pid=13554&fullsize=1

Is there anything modeled incorrectly? If you need to see another view I can happily put it on here. And also, what are some common problems for buttons that arn't clickable?

[D'Lanor]

The most common problem is probably when people forget to make the clickable an actor.