Jump to content

Recommended Posts

Posted (edited)

Something is wrong with dynamically spawned units on the CLIENT side.

 

So, when you would run this mission on the SERVER side, all would look fine. but once you log into a mission on the CLIENT side, you would see the underlying missing fields.

 

These fields are missing ONLY when the unit is spawned (coalition.addGroup) when you are actually already logged onto the server. (When you are logging into a server, and the units are already spawned on the server, the client will just load these units and the fields will be properly propagated.)

 

1. Vehicles are not showing the "group" field.

 

tceg.jpg

 

2. Air units are not showing the "task" field.

w4hu.png

 

i can upload a test mission that illustrates this problem (without using MIST...).

 

Guys like ENO etc, can you confirm this error also on your side?

 

kind regards,

Sven

Edited by FlightControl

[TABLE][sIGPIC][/sIGPIC]|

[/TABLE]

Posted

I reported a similar problem back in either 126-127 when I was using dynamically spawned units / group spawns in random zone or group to random zone. Server side was fine but clients showed units all over the place. I got frustatrated and stopped using those functions awhile ago- except in CTTS where only infantry are spawned. Older missions resaved and with mist / CTTS reset still have scripting errors reported by Ajax- but not the issue you're reporting. New missions using this script (built in 128) have spawned infantry with no problem.

 

If you can send me a mission or post a mission example here like that one used above I can run a test on it between fly in missions today.

"ENO"

Type in anger and you will make the greatest post you will ever regret.

 

"Sweetest's" Military Aviation Art

Posted

Here you go:

 

A side note, i would love to have this mission running stable for about 2 hours without a single crash in 1.2.8 RC3. I got this running stable in 1.2.8 RC2, but after the RC3 update, i get a crash after 1.30h...

You'll see i've put a lot of work in this mission. This mission is to run on servers. Running it on a single machine and also play it, then you might have performance problems...

And please, let the community not start again about eye candy...

 

Sven

Anapa Invasion - 2014.05.04.068.miz

[TABLE][sIGPIC][/sIGPIC]|

[/TABLE]

Posted

i have an issue related to the problems that ajax are reporting. That is that air units, when you destroy them on the client, and they were dynamically spawned, they will report that i 'killed a building'... Trying to find the root cause of this action...

[TABLE][sIGPIC][/sIGPIC]|

[/TABLE]

Posted

Message to the moderators

 

I saw that my error raise was moved to "Mission editor issues". This problem has nothing to do with mission editor issues at all...

 

It has to do with runtime. Please move this back into the right location.

 

thanks,

Sven

[TABLE][sIGPIC][/sIGPIC]|

[/TABLE]

Posted

Trigger and scripting engine related bugs are grouped as mission editor related.

Good, fast, cheap. Choose any two.

Come let's eat grandpa!

Use punctuation, save lives!

  • 3 months later...
Posted (edited)

In search for who killed the building ...

 

Remember this post?

 

In search for these guys who kill buildings???

 

Well... It is still not resolved in DCS 1.2.10...

 

To summarize: this problem only related to dynamically spawned units using Coalition.addGroup( CountryId, CategoryId, GroupStructure )

 

Problem1:

Dynamically spawned "planes" and "helicopters" are recognized on the CLIENT as a "building". We can recognize this because when we kill such a dynamically spawned air unit, the CLIENT will report that we killed "A BUILDING"...

 

The same was with "vehicles" some while ago, but then i found that the problem related to a wrong field in my GroupStructure parameters... Once that was corrected, vehicles are correctly recognized on the server.

 

Note that i pass EXACTLY the same GroupStructure input parameter to AddGroup(), as the structures defined within the mission editor file ("mission" file in the unzipped mission.miz file). The only thing that i change is the field: 'lateactivation', which i set from true to false...

 

Problem 2:

The fields on the map are not shown correctly on the client, see the first post within this thread...

 

DCS, please check these flaws, which may be easy fixes... For the community, please motivate the DCS bug fix team to evaluate if this is an issue that can come into the fix pipeline with a considerable priority...

 

Thank you for reading this post, understanding it, and your kind support in this.

 

thanks,

Sven

Edited by FlightControl

[TABLE][sIGPIC][/sIGPIC]|

[/TABLE]

Posted

Hi Sobek,

 

This problem has nothing to do with trigger and scripting engine related problems. This problem has to do with the multiplayer engine of DCS world.

I am afraid it got moved into the wrong section on the forum.

 

thanks,

Sven

[TABLE][sIGPIC][/sIGPIC]|

[/TABLE]

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...