Ok, i know that i've been posting a lot, but there's another problem.

My quest Doesn't start and i don't know how to solve this problem.

I checked all my script and there's no error of compilation.

I checked all my scenes and dialogue and everything seems to be correct.

When I try to speak with the NPC that gives me the quest the dialogue doesn't start.

I have also made a trigger with this script:

Quest Property (NameQuest) Auto

Event OnTriggerEnter(ObjectReference akActionRef)

if AkActionRef == Game.GetPlayer()

(NameQuest).SetStage(10)

(NameQuest).SetObjectiveDisplayed(10)

endif

Endevent

In this case the quest "start", but there's no marker, no stage test (I wrote something but it doesn't appear) and a scene that used to start when my quest is set on stage 10 didn't start.

I HAVE TRIED TO GENERATE SEQ FILES, BUT IT DOENS'T FIX THE PROBLEM.

I have lost my hope guys.... I really don't know what to do. If someone know something and wanna help me I would be very grateful.

With "stage test" i mean the things that i wrote in the log entry

One of your aliases might not be filling. Make them all optional and test on a new save. If the quest starts check SQV in the console to see which alias is not filling properly. It may be reserved by another quest, meaning you'll have to tick the allow reserved box for it.

SQV will also tell you whether the quest is running and what stage it is at.

Just to pick up on this one point, as it's a common issue. The dialog that starts a quest can't be part of the quest, as it's not available until the quest has already started. Catch 22.

You typically need a separate starter quest that is marked "start game enabled" that has the dialog, and gets stopped as soon as the other one starts.

That's strange, because i do it every time.

The others quest i've started by dialogue work properly.

I just put on the dialogue a condition that says

GetStage (namequest) < 10

it works all time

SGE quest dialogue can be used to start a quest, by setting the stage, but technically the quest is already running. That's where an SEQ comes into play.

You'd better use the different DefaultSetStage... triggers that already exist. They work perfectly.