When is the next client update due?

[Lt_Damage 0]

Could anyone please post information about the next client update?

1.49 has stablilised the server environment.

But players are still dealing with crashes to desktop on 1/2 the maps due to 1.46 client.

[ALDEGA 0]

I haven't had any crashes. Are you sure it's not a missing addon issue?

[Lt_Damage 0]

It depends on the map we play.

Some maps work, some crash the players to the desktop as soon as we load the map. (After selecting team, before breiefing)

It is only some maps, it is not an addon issue, as all maps have been extensively tested to make sure they do not require additional addons.

All the maps worked fine until 1.46 client update was released.

The server is quite stable now with 1.49, I think its absolutely fantastic, hoping the clients can match it.

Regards,

[ALDEGA 0]

Whenever a crash occurs, it's always useful to check out the latest entry of flashpoint.rpt . If it IS a simple error like missing addon then you will be able to interpret the error message in there. The reason why those maps work when you tested them is because you may have installed the necessary addon but not all other players have. Because you can download the official patches without the vehicle addons, even missions that only use official units may cause this.

[Lt_Damage 0]

No, I have checked the flashpoint.rpt and it is not an addons issue.

I have a stock standard install of Operation Flashpoint and I have added nothing to it but the official upgrades.

This issue started since 1.45 or 1.46 and is not related to addons used by maps, it is usually an "access violation" in Operationflashpoinh.exe. I have no idea what is causing this violation, hoping BIS will nail it down shortly.

I was thinking since config.bin is somewhat protected now it is creating access violations when something tries to access it in some way.. dunno.

[suma 8]

As I still have very few crash analysis results from 1.46 clients running on 1.49 servers, I can only speculate why it crashes.

I think the most common reason can be the server that is using Dynamic Sound Range config replacement (with less cargo positions available in Hind). When server using this mod has any Hind in the mission (it may be even empty), clients may easily crash. I think clients using this replacement should be quite safe, though it is hard to tell it exactly. If you want the 1.46 client to be stable, I would advice not to use any config modification on both 1.46 client and 1.49 sever.

About the original question ("When is the next client update due?"): as we still do not know what is causing the client crashes, we still do not know what needs to be fixed on client side - depending on this, we will decide if some simple fix can be made to the existing client or if client patch is necessary.

I can tell you certainly that you should not expect any client fix within next two weeks. See

this Multiplayer forum topic.

[Lt_Damage 0]

Ok, a few things:

When I said "no addons" I thought I was being clear.

Let me restate:

Server, 1.49, Only addon is the EditorUpgrade102

Clients, all 1.46, most without any addon at all. Some have tried the sound addon but I have advised them to roll it back as it can lead to an unstable playing environment in 1.46 as it has not been fully tested yet.

(Users who did try to use it were unable to connect to a game, once uninstalled, this issue disappeared.)

So to summarise, we do not use ANY unofficial addons besides the editorupgrade (because so many maps now use it). We are aiming for a stable server evironment so addons are currently not an option.

The only other modification I can think of is custom faces, if a user uses a custom face addon, maybe that is causing it. But I also think this unlikely as very few people on the server use them and 100% of users get disconnected, noone is spared when it crashes to desktop. So this issue must be in some way related to a conflict between 1.46, and 1.49 Standalone server.

I will endeavour to have all the players on my server send through crash reports to [email protected]

Regards,