Tutorial 2: Part 2: Simple Scripting

HomeForumsTutorialsTutorial 2: Part 2: Simple Scripting

Tagged: , ,

This topic has 4 voices, contains 12 replies, and was last updated by  Tim 100 days ago.

Viewing 13 posts - 1 through 13 (of 13 total)
Author Posts
Author Posts
January 29, 2012 at 10:49 pm #789

Tim

A lot of explanation, not a ton of work.

January 31, 2012 at 6:17 pm #801

griffcl

So quick question. When I get to the beginning of level two both cylinders light and sound in sequence, but the first cylinder will not “ding” when stepped on. I’ve double checked and just deleted and reworked it but no change. I went ahead and finished out level three, and the same thing happens with the first and second cylinders. I’m sure there is something small that I am missing. I’ll check back later, no hurry in responding, just trying to get an early fix on it.

Thanks,
Chad

  • This reply was modified 110 days ago by  griffcl.
January 31, 2012 at 7:32 pm #803

Tim

Great to hear you are so far already. I recommend you use the Kismet debugger to verify the flow of your script. The debugger is the feature i show in the last few minutes of the demo. Debugging these types of issues is an important part of developing some competency in scripting and game logic. You’ll learn more from these types of mistakes than you will from your easy solutions. Good luck!

February 1, 2012 at 2:46 pm #804

Tim

I can not remember if I mentioned “Max Trigger Count” in the demo or not. This is the setting that tells the engine how many times a trigger may be allowed to fire. In the case of this demo, please set your triggers in the Kismet properties box to 0. Zero = infinite.

Chad, this may be the issue you were having and if so, my bad. This setting is something that is often forgotten even by the pros.

  • This reply was modified 109 days ago by  Tim.
  • This reply was modified 109 days ago by  Tim.
Attachments:

You must be logged in to view attched files.

February 1, 2012 at 5:14 pm #813

griffcl

That is exactly what the issue was, thanks! Everything else worked perfectly

February 1, 2012 at 5:51 pm #814

Tim

My apologies. I was feeling pretty crappy when I assembled those videos. Give me a hand and note that omission to the others if they are wondering. Thank you.

…and congrats on making your (I am assuming) first video game.

February 2, 2012 at 12:14 pm #815

griffcl

Well, you can scrap the congrats for now. When I got in this morning to start messing around some more in UDK, my file will not load, instead UDK crashes! UDK starts up fine, but when I open my file it dies. I have tried on a couple different machines now, any idea as to why, or what I could do to get it back up.

Attachments:

You must be logged in to view attched files.

February 2, 2012 at 2:06 pm #817

Tim

This often happens due to some inconsistency between the shaders compiled for your map and the version of the engine you are running. Few things crash UDK as readily as that. Solution:

1. Pick a machine.
2. Verify the install is the SEPTEMBER release. You will know just by seeing the folder the editor is launched from.
3. Re-download the resources from the site labeled version 2. I am going to nuke version 1 now. Version two was built in the SEPTEMBER release and will work.
4. Reload your map. Cross fingers.

For a short while I had assets on the site using the DECEMBER release because we had not discovered Epics failure in supporting your video cards. My fear is that you were using the DECEMBER pack instead of the SEPTEMBER pack. The pack on the network under ASSIGN/Tutorial Two/ is the SEPTEMBER pack created and placed there by me.

Please keep me updated. I figured some issues would arise from this change.

February 3, 2012 at 11:57 am #818

griffcl

Just a head up for the skype this afternoon, I downloaded v2 of the pack, the simon map is not giving a fully load option. I’m still crashing when attempting to open. We can discuss this this afternoon though.

February 9, 2012 at 7:06 pm #842

dwoodley

Hey I know this is last minute, but I’m having trouble with finalizing my script. To me it looks just fine, but it’s not playing that way. Levels 1-3 work perfect and the intro for level 4 works fine. It’s when you play level 4, once you get to the 3rd pad it automatically resets you to level 3 before letting you even attempt the last pad. Then in level 3 you can activate the first pad but not the second. I’ve tried the editor overview thing while I played and just can’t seem to figure it out.

February 9, 2012 at 7:34 pm #849

Tim

Hard to say without seeing it. Work on debugging it tonight using the Kismet debugger and make sure the trigger settings are correct, including MaxTriggerCount = 0. It sounds like you have an order of operations issue where something is wired up weird…perhaps a copy/paste error where your level 4 nodes still have some connections to level 3 they should not have.

I will be in the lab from 9:30 to 12:00 tomorrow morning for help to anyone that comes in. Swing by if you can and I will help you sort through it.

You can also email it to me. I won’t tell you exactly what is wrong but I will point you in a direction. It’s important you guys do some debugging to really grock whats going on with these scripts.

Good luck.

  • This reply was modified 100 days ago by  Tim.
February 9, 2012 at 8:05 pm #852

wmm0003

So, Brad and I are having trouble with the third level. It spawns us back at the start, but wont show the color hints/sounds and just goes straight to player control. I even copied and pasted from the previous and made sure everything was attached, but it still isn’t showing me the hints afterwards.
Thanks,
Weston

February 9, 2012 at 8:50 pm #853

Tim

My first suggestion is that you open up my demo level and then open up my Kismet scene and full screen the window. Grab a nice big screen shot of it.

Go back to your level and refer back and forth between the two to make sure your sequence is the same as mine.

Next I would double check all the settings on your triggers (MaxTriggerCount=0) and double check all the settings on your gates (set to toggle off after 1, hooked up correctly, etc…)

I will be in the lab tomorrow morning for last minute help.

Your also welcome to post a screen shot here for me to check out and look for something obvious in the sequence that is messed up.

Viewing 13 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic.

Welcome TimLindsey.com

Log in

Lost your password?

Register For This Site

Join

Join to comment.