Bug #30094

JIP broken

Added by Xeno over 3 years ago. Updated over 3 years ago.

Status:New Start date:04/05/2012
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
CPU: Single / Multi Player?:
System RAM size:

Description

I've connected to the TAW server yesterday which was running the mission just to take a look at mission.

After JIPing in I had a comletely empty map, no notes, no tasks and at least one error regarding some R3F problem.

There are also a lot of "beginner" script errors in the mission.
For example, never use waitUntil and Sleep in init.sqf. It delays further execution of init.sqf until the player is ingame.
Get rid of call compile formats, they are slow as hell.
Don't use execVM or Spawn from events, events can run code in the same frame, execVM and Spawn is at least running one frame later and can be delayed several frames.
Dont't set markers globally in MP if not needed (onJIP script, ececuted by every client plus server).
Try to avoid using the BIS MP framework for sending stuff over the network, make your own.
And so on...

History

Updated by Psychobastard over 3 years ago

destructive criticism - but where he is right he has right.
I join this mission two days ago too and wonder me about the empty map without any markers, tasks or whatever - result: disconnect after 3 minutes.

Updated by Xeno over 3 years ago

Psychobastard wrote:

destructive criticism - but where he is right he has right.

It's not destructive but constructive :)
Like you wrote, if people have absolutely no idea what to do after joining then they leave again.

Edit: It's one of the most important things in MP mission making to have missions working technically ok, even more important than adding more features.

Updated by Psychobastard over 3 years ago

ok, revision: set devastating for destructive. ;-)

Updated by Tonic-_- over 3 years ago

Xeno wrote:

I've connected to the TAW server yesterday which was running the mission just to take a look at mission.

After JIPing in I had a comletely empty map, no notes, no tasks and at least one error regarding some R3F problem.

There are also a lot of "beginner" script errors in the mission.
For example, never use waitUntil and Sleep in init.sqf. It delays further execution of init.sqf until the player is ingame.
Get rid of call compile formats, they are slow as hell.
Don't use execVM or Spawn from events, events can run code in the same frame, execVM and Spawn is at least running one frame later and can be delayed several frames.
Dont't set markers globally in MP if not needed (onJIP script, ececuted by every client plus server).
Try to avoid using the BIS MP framework for sending stuff over the network, make your own.
And so on...

Currently there are nothing in the task part so that would explain why tasks are empty, as for the empty map do you mean as in there were no markers in general on the map other then the standard AEG or you had no map period? Currently this is a experimental sandbox style play with only 5 side missions that do not repeat (but will in future when I build up the list) so that may explain why there were no objectives as they were already completed and all that was left was building yourself a base and gathering your resources to survive. Right now most of the code is sloppy but I like the advice and will be cleaning it up as the project goes along to improve overall stability and do you happen to know which error it was in general for R3F?

Also available in: Atom PDF