jers

Update to this, with some research I found that it looks like there's an upper limit of 4000 groups, inspecting our logs this problem happens every time at some point int he mission when the supercarrier is respawning crewmen. 2020-05-2221:28:00.356WARNING FLIGHT: procCrewAssignAircraft client id 4294967295, crew_id 2, hot_start 0 2020-05-2221:28:00.356WARNING FLIGHT: crew 2 wCarrierCrew::reset_LA() 2020-05-2221:28:00.356WARNING EDOBJECTS: RegMapStorage has no more IDs 2020-05-2221:28:00.356ERROR EDOBJECTS: Failed assert `false` at Projects\edObjects\Source\Registry\RegMapStorage.cpp:42 2020-05-2221:28:00.356WARNING FLIGHT: carrier technician [2: shooter] created, id 4 2020-05-2221:28:00.356WARNING EDOBJECTS: RegMapStorage has no more IDs 2020-05-2221:28:00.356ERROR EDOBJECTS: Failed assert `false` at Projects\edObjects\Source\Registry\RegMapStorage.cpp:42 2020-05-2221:28:00.356WARNING EDOBJECTS: RegMapStorage has no more IDs 2020-05-2221:28:00.356ERROR EDOBJECTS: Failed assert `false` at Projects\edObjects\Source\Registry\RegMapStorage.cpp:42 2020-05-2221:28:00.356WARNING EDOBJECTS: RegMapStorage has no more IDs 2020-05-2221:28:00.356ERROR EDOBJECTS: Failed assert `false` at Projects\edObjects\Source\Registry\RegMapStorage.cpp:42 2020-05-2221:28:00.356WARNING EDOBJECTS: RegMapStorage has no more IDs 2020-05-2221:28:00.356ERROR EDOBJECTS: Failed assert `false` at Projects\edObjects\Source\Registry\RegMapStorage.cpp:42

Hello everyone. We added the Supercarrier to our Persian Gulf mission today and things seem to go fine for a while but after about an hour or so we begin to see this error spamming out logs thousands of times over: [color=#B9BBBE][font=Consolas]2020-05-23 02:30:57.535 WARNING EDOBJECTS: RegMapStorage has no more IDs[/font][/color] [color=#B9BBBE][font=Consolas]2020-05-23 02:30:57.535 ERROR EDOBJECTS: Failed assert `false` at Projects\edObjects\Source\Registry\RegMapStorage.cpp:42[/font][/color] [color=#B9BBBE][font=Consolas]2020-05-23 02:30:57.535 WARNING EDOBJECTS: RegMapStorage has no more IDs [/font][/color] [color=#B9BBBE][font=Consolas]2020-05-23 02:30:57.535 ERROR EDOBJECTS: Failed assert `false` at Projects\edObjects\Source\Registry\RegMapStorage.cpp:42[/font][/color] We've tried reducing the number of units in the mission taking a hint from that error, but so far it hasn't seemed to help. Is there any way an engineer can tell us exactly what triggers this error so that we might be able to fix whatever it is that's triggering it? Thanks! Zelly

+1 to this. Any time a new unit is spawned the log is filled with this and performance suffers to the point of the process becoming unresponsive and we're forced to kill it. We'll be rolling back our servers in the meantime.

Seeing a lot of HTTP request dcs:checksession failed with error 28: Timeout was reached at the same time we're seeing a good deal of lag on our server. Is the outgoing request done in LUA and single threaded/blocking until the timeout is reached? Our networking is pretty ok at the time, and we're also seeing 503's which further lead me to believe that the problem isn't on our connection's end, but I could wrong about that.

Flying online with folks without having the struggles of keeping up with a VFS is exactly why we created https://reddit.com/r/hoggit, so might be worth it for a lot of the people I'm hearing here to check it out cause it sounds like a lot what you might be looking for. We're also all over Discord too. We're pretty active there as a Discord partner, and we're definitely always trying to help out new players, or seasoned players just looking to smoothly get into multiplayer in a low stress way.

20+ on a residential internet connection is highly likely to experience issues. NIC on the server could also be a problem.

Dear lord I hope that doesn't work. If a server starts messing with my keybinds that would literally be the last time Id touch that server.

My theory was that this had something to do with sounds playing due to the log files, but it's pretty coincidental. Basically it looks like something hangs up whatever thread the network communication is on for all clients that have the F-14B installed, even if they aren't flying it at the time. The simulation on the server and clients without F14 installed works fine. This was repro'd by someone testing uninstalling the module and reconnecting, they had no problems going forward when others with it installed still did. This also only seems to be happening on Persian Gulf. When we removed the Iranian AI F-14B's the problem immediately went away. Here's some sample log files from some of the clients: https://gist.github.com/jeremysmitherman/7668454bde66aa208477528579aa7a2d https://gist.github.com/jeremysmitherman/a5374182bf0b07bd523bf97209092682 https://gist.github.com/jeremysmitherman/687a2e1d6bd43f2a5e5855c19bcba4bb

As an admin on Hoggit it's a pretty frustrating line to walk because we know you're upset and we try our best to ensure that player's frustrations are centered on the product. I feel like we (meaning the community, as much as the administration) does a pretty solid job at calling out bad behavior, and personal attacks are one of the few things we freely swing the banhammer for. That all being said, toxicity is not disagreeing with your business practices, even vehemently so. And we go to the extent of our abilities to ensure that the conversation stays on the product. We are not perfect as we are not omni-present, but we clean up things when we find it and we encourage the community as hard as we can to do the same. I also highly encourage everyone to use the facilities that reddit provides to help us identify when things go to far so that we can help you. We are not products, we are people and everyone here will respect that or be asked to leave. But this 100% feels like ED using Hoggit as a vehicle for their own frustrations. Using our "toxicity" as a scapegoat for the, let's be frank, failings of DCS World doesn't feel fair. It's not Hoggit's toxicity that created a system that can potentially cost $<insert dollar amount here> with every new addon or module that comes out. Imagine if you had to buy $200 worth of add-ons to be able to play on GAW. And then imagine something else came out so now the people who have already paid $200 now have to pay $59.99 more, or new players $259.99 if we enforced their use. Look at the number of products you have in early access. It isn't Hoggit's toxicity that made you guys have 45% of your available modules in early access, With even more on the way! We love DCS, it's obvious. We adore your product, it's why we're all here. We want the best for it. But you guys don't foster healthy discussion on your forums, so that tends to pour gas on fires you have set yourself. And the worst thing about having to make this post is that we think as a company you guys are wonderful and have the best 4th gen simulation that will likely ever be made for the consumer market. We have your back through so much of this (many of us are software developers ourselves and understand the pressures that come with that), and we personally work hard to make sure that we have a healthy community so that everyone can thrive even through the rough times and rough decisions (God knows we've had our share on Hoggit too). So Hoggit, being one of the few populous places where people can talk about the flaws of the product freely, is going to have large buildups of negative opinions from time to time and I highly highly encourage you to work *with* us to make that better instead of... whatever this is.

Obviously I don't have the source but it feels like when certain sounds are supposed to play with the AI F-14B, whatever thread that is handling the network communication between the affected players just stops working.

At Hoggit on our server Persian Gulf At War we've encountered a weird bug with AI F-14B's. It seems like on certain events that are supposed to emit engine sounds (after burners, etc etc) on AI F-14B's on Persian Gulf only it causes every player on the server that has the F14 module installed to freeze and eventually crash to desktop. The simulation continues running perfectly fine for everyone without the F-14 installed (we even repro'd it with a guy who got a freeze with the F14 installed, he uninstalled it and no more problems). I've got a host of log files showing the issue and will add them to this thread when I get them put together.

Hey guys, over at Hoggit we've been rocking Georgia at War for a good while now ( ), lately we've been plagued with rubberbanding and lag, however we have migrated our mission to dedicated hardware and all of our issues with rubberbanding and lag are gone! So I guess the point of this post is if you've tried out GaW in the last couple of weeks but got turned off by rubberbanding, we've solved that issue and we'd love for you guys to try it out if you're into dynamic, medium scale PvE that has a focus on teamwork and helping noobs. The server's name is "Hoggit - Georgia at War" and the password is hoggit1fw. If you join up, you'll be helped greatly by joining our discord and checking out the #georgia-at-war channel. It's very active and we're always looking to help folks have a good time while working as a team to help push along a moving frontline (https://gaw.hoggitworld.com to see the current status of the mission!) You can find detailed information about how to progress the mission here: https://wiki.hoggitworld.com and clicking the GAW - Georgia at War banner with the F-18's on it, and you can get a realtime look at the map, the enemy and friendly positions, and each aircraft playing here: https://gaw.hoggitworld.com We also run a highly populated training server named "Hoggit - Training Server" where you can practice everything from Tomcat bombing to SRS communications with other pilots or ATC. We strive to provide a relaxed environment that can get as serious or as laid back as you'd like it to be. Thanks guys, looking forward to seeing some new faces there!

Getting a message on our dedicated server interface that the WebGUI is under maintenance. Is there an expected ETA until we can use this again?

No matter how crazy the server gets with rubber banding (And boys it's getting really crazy these days), weapons always seem to never be affected. My theory is that the weapons are all server authoritative, I obviously have no way to verify thatbut whatever it is in the netcode that handles the weapons desperately needs to be the way that client aircraft are handled as well.

The icons do no appear if you are not part of the owning coalition. You can confirm this by going back to spectators then using F10 again if the server lets you see map data from spectators.