Creation Kit - Starting Dialogue Not Firing

[FinalCloud]

Ok So, I am really quite confused here with the CK, Basically the other day I was using the CK, logged in Skyrim to check my quest, everything worked perfectly, then I went outside to play some tennis. When I got back, goddamn Steam had updated my Skyrim to 1.7, and my quest dialogue no longer fired, I uninstalled Fuz Ro Doh and tried recording some dialogue and coudlnt fix it, so I uninstalled Skyrim, and reinstalled it and the CK and remodded my Skyrim. I deleted my old quest to try again, I have now just opened the CK and tried to make a very simple bit of dialogue with one npc to test it, Created a female nord, with female nord voice, made just an opening piece of dialogue with GetStage > 10 and GetisRefAlias (tried just GetISID aswell) conditions but this first piece of dialogue just will not fire, the npc just keeps saying Standard Nord Greetings without saying anything related to my quest.

 

Sorry for the TextWall

 

Any help would be greatly appreciated, this is frustrating!

 

Edit - For the record I have searched around numerous threads with this (or similar) problems and tried a few "solutions" to no avail

[FinalCloud]

More Info - I updated Fuz Ro Doh to latest earlier today and the problem persists, I am really confused, are there any mods known to cause this? Or any changes in the CK to make following the tutorial on the creationkit site not work? Does no one have any ideas? I am totally baffled by this.

[Ulfengaard]

I gotta bump this. I have the same problem and cannot get my questgiver to present the opening dialogue option for my quest. Did you find a solution, Final?

 

EDIT: The dialogue works if I forcegreet. Don't know what that suggests.

[AleKahpwn]

It seems a few of us over at the talk page at the tutorial wiki are having the same problem.(http://www.creationkit.com/Talk:Bethesda_Tutorial_Dialogue - All the way at the bottom)

 

So, yeah. Bumping for justice and hopefully someone somewhere can help us out.

[AleKahpwn]

Alright, I found a solution that worked for me. Silly, but I just had to save my game, and load that save, and it worked. Not sure if it's also related to the patch I just got.

 

Either way, give saving your game and loading it a shot.

[Ulfengaard]

Could it... could it really be so simple? I hope so. I'll try it right now.

[FastestDogInTheDistrict]

It is possible that this may be related to load order. Something very similar happened to me recently [LINK], and it was related to conflicting .esp's.

[FastestDogInTheDistrict]

EDIT: Scratch that.