(Review Completed) [MP coop 1-32] Destroy power station V28

[fleepee]

No AI but only players can deploy mobile spawn.
There is an option in the lobby to choose between ambulance or medic respawn type.

[hoz]

We played last night the 14 version and found that the once we killed the electrical station the objective didn't set as done. we blew up everything but the big building. also one player didn't have any notes. not sure if thats a fluke or what

[fleepee]

as written in the briefing, you have to blow ALL buildings...
No reason not to see the notes ...

[hoz]

I see ok  previously taking out the electricals worked.

[fleepee]

No, it never did!
I think it's in eve of destruction...

[hoz]

Oh your right! thanks

Edit:

Played with the newest patch tonight and the mobile respawn wasn't working. Not sure if its the revive or what it seemed to work in the previous beta.

[fleepee]

It's certainly due to the beta patch as I have tested it: mobile respawn and revive work all right...
My game version: 1.04.59026

edit: It works also with beta patch 1.04.60141...

[hoz]

We played again with the newest beta and still nojoy. Can't use the mobile respawn and the tasks don't show for the medic. maybe related?

[fleepee]

OK, I found the problem, I had wrong parameters in the revive_init script...
but the for the task problem... i don't understand...
corected and tested...
version1.15 uploaded...

[hoz]

The funny thing we noticed about this mission is the medic in the lobby didn't have a number assigned to him. We'll give it go soon enough.


EDit:

Ok smobile respawn still not working...  breifing not working for the other player (who happens to be medic) except that the revive options are shown in his breifing.  we ment to check if it was the same issue if he was another player besides the medic but we didn't...


on another note.. the sidechat message in yellow with the custom voice is only played for me. it doesn't play for the other player.

[fleepee]

I don't understand what's happenning with the briefing...
There's no reason for a player to see it or not...
The medic should have number 7 in the lobby.

the sidechat message in yellow with the custom voice is only played for me. it doesn't play for the other player.

I think you're talking about the intro message ("All the staff is watching you..."): did the other player ear the voice?
Or is it that he didn't have voice nor text?
voice is send by "sideRadio" and the chat message associated to the voice uses "[west, "HQ"] commandchat format" to include the leader name. I thought that sideradio will make all players ear the message... 

I tried again on a dedi (on the same Pc the game is running) V1.15, both mobile repawntype were working allright, but i didn't always ask if the 2 other players were having the radio and text messages, so I don't remember if there was problems or not...
I'm trying something with the init file and will upload V1.16 if needed...

[hoz]

I think you're talking about the intro message ("All the staff is watching you..."): did the other player ear the voice?Or is it that he didn't have voice nor text?

He hear's nothing sees nothing.

The medic should have number 7 in the lobby.

He is player 8 in the leader menu.

[fleepee]

He hear's nothing sees nothing.

I've changed that first radio message with globalchat, for its voice, it's now globalradio... tell me if it changes something for other players, if it does, I'll have to make the changes for all commander messages.

He is player 8 in the leader menu.

I know but he appears on seventh position in the lobby and the mission.sqm...

Code: [Select]

7: Medic (Mobile Respawn) is in the description field of alpha medic

[hoz]

MObile respawn... doesn't work in v16.
Tasks and briefing don't work for the other player. even if he chooses a slot besides the medic.


The starting message... neither of us got the  text, and the other player got the audio this time!

Code: [Select]


Server RPT...
Performance warning: Very large search for 376791 (>300 m)
Performance warning: Search for 77a8800# 376791: trafostanica_velka.p3d was very large (10470 m)
Performance warning: Very large search for 363697 (>300 m)
Performance warning: Search for 363697: wall_woodf_5_2.p3d was very large (10260 m)
Performance warning: Very large search for 348629 (>300 m)
Performance warning: Search for 348629: t_salix2s.p3d was very large (9150 m)
UnExpected call of CreateVehicle for 'Logic', pos(0.000000.2,0.301897.2,0.000000.2). Vehicles with brain cannot be created using 'createVehicle'!



client rpt..

Performance warning: Very large search for 362086 (>300 m)
Performance warning: Search for 4c95800# 362086: ind_pec_03a.p3d was very large (1740 m)
Performance warning: Very large search for 362226 (>300 m)
Performance warning: Search for 50aec00# 362226: a_stationhouse.p3d was very large (1740 m)
Performance warning: Very large search for 362099 (>300 m)
Performance warning: Search for 4c96000# 362099: ind_stack_big.p3d was very large (1740 m)
Performance warning: Very large search for 376789 (>300 m)
Performance warning: Search for 4456800# 376789: trafostanica_velka.p3d was very large (1770 m)
Performance warning: Very large search for 376790 (>300 m)
Performance warning: Search for 89a5400# 376790: trafostanica_velka.p3d was very large (1770 m)
Performance warning: Very large search for 376791 (>300 m)
Performance warning: Search for 5291800# 376791: trafostanica_velka.p3d was very large (1800 m)
Performance warning: Very large search for 363697 (>300 m)
Performance warning: Search for 363697: wall_woodf_5_2.p3d was very large (1590 m)
Performance warning: Very large search for 348629 (>300 m)
Performance warning: Search for 348629: t_salix2s.p3d was very large (1500 m)


One thing I would do is tighten(50M) up the search for these objects. You can do that by placing a some object near the search then  use nearestobjects search. Plus.. i don't think you need to do this on both the client and server... you can probably keep this to a server side check and then notifiy the clients when the object is killed. If you need an example I think i may have one here abouts. This search your doing now could be causing some inital lag.

[hoz]

Any updates here?