Jump to content

SAS_Storebror

Members
  • Content Count

    1402
  • Joined

  • Last visited

Everything posted by SAS_Storebror

  1. If tanks were a known issue before 3.005c (I never saw any dev statement telling so) I'd be wondering why they let us struggle with such issues for so long now. Removing all tanks from any mission definitely is no feasible workaround. It breaks mission logic and for certain servers it would completely kill the objectives. I could deal with temporarily removing player driveable tanks, but that seems unrelated. Mike
  2. Thanks a lot Kadin, so that's the reason - or at least one of - for the doubles. Now we still have the singles and quadruples Crashes related to tanks... interesting theory. Let's see what we have at The Flying Ass Clowns. First off, we've had two crashes last night: Aug 04 7:33 PM - uptime 42:48 hours Aug 04 10:06 PM - uptime 2:33 hours ...lo and behold, the 7:33 PM crash was the first Winter map crash (the other one was Autumn again) - hooray, celebrate! Let's look at the end of the logs of our missions, latest first, to see where there's something tank related in there: Aug 04 10:06 PM crash: T:575033 AType:12 ID:475136 TYPE:SPAD 13.C1 COUNTRY:101 NAME:Spad XIII PID:-1 POS(105215.391,111.877,87116.656) T:575033 AType:12 ID:774144 TYPE:BotPilot_Spad13 COUNTRY:101 NAME:BotPilot_Spad13 PID:475136 POS(105215.227,111.699,87116.500) T:575033 AType:4 PLID:475136 PID:774144 BUL:400 SH:0 BOMB:0 RCT:0 (105215.391,111.877,87116.656) T:575041 AType:13 AID:594944 COUNTRY:101 ENABLED:1 BC(0,3,2) Tank related: NO Aug 04 7:33 PM crash: T:454561 AType:13 AID:592896 COUNTRY:201 ENABLED:1 BC(0,0,0) T:454590 AType:12 ID:775184 TYPE:KV-1s ChTZ(1943) COUNTRY:101 NAME:KV1 PID:-1 POS(96445.977,91.896,82386.672) T:454590 AType:12 ID:515088 TYPE:BotDriver_KV1 COUNTRY:101 NAME:BotDriver_KV1 PID:775184 POS(96443.938,92.696,82386.453) T:454590 AType:10 PLID:775184 PID:515088 BUL:0 SH:0 BOMB:0 RCT:0 (96445.977,91.921,82386.672) IDS:a4a28a30-5b9e-409a-9d95-2a492ea685b9 LOGIN:1fbb56cd-3fb7-4e6e-809a-7a1cd292a1ba NAME:ST_Malesan TYPE:KV-1s ChTZ(1943) COUNTRY:101 FORM:0 FIELD:0 INAIR:1 PARENT:-1 ISPL:1 ISTSTART:1 PAYLOAD:0 FUEL:0.000 SKIN: WM:0 Tank related: YES (last lines refer to KV-1) Aug 03 12:55 AM crash: T:576955 AType:4 PLID:819200 PID:442368 BUL:2800 SH:0 BOMB:0 RCT:0 (95433.320,1528.296,76588.047) T:576955 AType:12 ID:763904 TYPE:Spitfire Mk.IXe COUNTRY:101 NAME:Spitfire IXe PID:-1 POS(104654.344,112.283,86329.820) T:576955 AType:12 ID:909312 TYPE:BotPilot_Spit9 COUNTRY:101 NAME:BotPilot_Spit9 PID:763904 POS(104653.039,111.927,86329.813) T:576955 AType:4 PLID:763904 PID:909312 BUL:740 SH:0 BOMB:0 RCT:0 (104654.344,112.283,86329.820) Tank related: NO Aug 01 9:31 PM crash: T:576921 AType:16 BOTID:750616 POS(105357.570,111.196,86546.289) T:576923 AType:16 BOTID:842775 POS(94459.359,160.379,75066.406) T:576924 AType:4 PLID:654361 PID:800793 BUL:0 SH:0 BOMB:0 RCT:0 (0.000,0.000,0.000) T:576929 AType:16 BOTID:800793 POS(94436.992,164.530,75254.672) Tank related: YES (BOTID:800793 is T-34) Jul 31 9:14 PM crash: T:587609 AType:4 PLID:1056768 PID:696320 BUL:600 SH:0 BOMB:10 RCT:0 (82298.898,4988.423,81607.750) T:587609 AType:12 ID:539648 TYPE:Yak-1B ser.127 COUNTRY:101 NAME:Yak-1b Ser.127 PID:-1 POS(105171.023,111.900,87089.148) T:587609 AType:12 ID:781312 TYPE:BotPilot_LaGG3 COUNTRY:101 NAME:BotPilot_LaGG3 PID:539648 POS(105170.344,111.928,87088.672) T:587609 AType:4 PLID:539648 PID:781312 BUL:360 SH:0 BOMB:0 RCT:0 (105171.023,111.900,87089.148) Tank related: NO Jul 28 4:45 PM crash: T:354077 AType:16 BOTID:332825 POS(96022.430,100.515,81314.594) T:354079 AType:16 BOTID:599055 POS(94149.211,159.294,73999.406) T:354083 AType:2 DMG:1.000 AID:-1 TID:841743 POS(94147.914,158.732,73999.281) T:354085 AType:3 AID:-1 TID:841743 POS(94147.914,158.732,73999.281) Tank related: YES (BOTID:599055 is PzIII) Jul 26 10:11 PM crash: T:574334 AType:4 PLID:437248 PID:899072 BUL:1620 SH:0 BOMB:0 RCT:0 (104657.000,111.883,86435.031) T:574334 AType:12 ID:302080 TYPE:Il-2 mod.1942 COUNTRY:101 NAME:Rake PID:-1 POS(120636.000,250.088,131345.797) T:574334 AType:12 ID:701440 TYPE:BotPilot_Il2 COUNTRY:101 NAME:BotPilot_Il2 PID:302080 POS(120636.422,250.381,131346.438) T:574334 AType:4 PLID:302080 PID:701440 BUL:1580 SH:0 BOMB:4 RCT:0 (120636.000,250.088,131345.797) Tank related: NO Jul 26 10:07 PM crash: T:3673 AType:12 ID:194563 TYPE:T-34/76 STZ(1942) COUNTRY:101 NAME:T34 PID:-1 POS(96445.781,92.211,82386.648) T:3673 AType:12 ID:195587 TYPE:BotDriver_T34 COUNTRY:101 NAME:BotDriver_T34 PID:194563 POS(96444.406,92.811,82386.750) T:3673 AType:10 PLID:194563 PID:195587 BUL:0 SH:0 BOMB:0 RCT:0 (96445.781,92.266,82386.648) IDS:a2c53c09-f320-4f9e-a4d3-3e0d4a054f15 LOGIN:54010b30-950a-46b7-999d-f4b1d856f75b NAME:AeroAce TYPE:T-34/76 STZ(1942) COUNTRY:101 FORM:0 FIELD:0 INAIR:1 PARENT:-1 ISPL:1 ISTSTART:1 PAYLOAD:29 FUEL:0.000 SKIN: WM:0 T:0 AType:15 VER:17 T:4730 AType:22 PID:194563 POS(96441.094, 91.936, 82386.109) Tank related: YES (last lines refer to T-34) Jul 26 10:05 PM crash: T:645 AType:20 USERID:a54efbbc-c70c-424d-966d-6cb52fe5a1aa USERNICKID:ce80d746-efb6-4a5e-8d7a-6db98b20d45f T:1447 AType:12 ID:194562 TYPE:T-34/76 STZ(1942) COUNTRY:101 NAME:T34 PID:-1 POS(96445.781,92.206,82386.648) T:1447 AType:12 ID:195586 TYPE:BotDriver_T34 COUNTRY:101 NAME:BotDriver_T34 PID:194562 POS(96444.406,92.806,82386.750) T:1447 AType:10 PLID:194562 PID:195586 BUL:0 SH:0 BOMB:0 RCT:0 (96445.781,92.266,82386.648) IDS:a2c53c09-f320-4f9e-a4d3-3e0d4a054f15 LOGIN:54010b30-950a-46b7-999d-f4b1d856f75b NAME:AeroAce TYPE:T-34/76 STZ(1942) COUNTRY:101 FORM:0 FIELD:0 INAIR:1 PARENT:-1 ISPL:1 ISTSTART:1 PAYLOAD:0 FUEL:0.000 SKIN: WM:0 Tank related: YES (last lines refer to T-34) Jul 25 7:59 PM crash: T:574307 AType:4 PLID:408650 PID:439370 BUL:1308 SH:0 BOMB:0 RCT:0 (105492.813,194.553,85441.859) T:574307 AType:4 PLID:485451 PID:341067 BUL:0 SH:0 BOMB:0 RCT:0 (105013.508,112.059,86937.563) T:574311 AType:16 BOTID:341067 POS(105010.516,111.955,86935.781) T:574314 AType:16 BOTID:439370 POS(105509.016,199.294,85426.109) Tank related: NO Jul 25 6:48 PM crash: T:210317 AType:1 AMMO:explosion AID:1368084 TID:1393664 T:210318 AType:1 AMMO:SHELL_GER_20x82_HE AID:1368084 TID:1393664 T:210320 AType:1 AMMO:explosion AID:1368084 TID:1393664 T:210338 AType:13 AID:688128 COUNTRY:101 ENABLED:1 BC(0,11,4) Tank related: NO Jul 25 6:40 PM crash: T:15270 AType:12 ID:401417 TYPE:BotGunner_Bf110G2 COUNTRY:201 NAME:BotGunner_Bf110G2 PID:400393 POS(99066.422,92.305,51926.016) T:15270 AType:3 AID:-1 TID:401417 POS(99062.859,100.203,51919.992) T:15278 AType:16 BOTID:394249 POS(99068.742,98.440,51931.566) T:15290 AType:6 PID:393225 POS(99066.594, 99.266, 51926.984) Tank related: NO 12 crashes within 11 days since 3.005c came out, 5 of them have tank related things at the end of the logs, 7 don't. No clear picture if you ask me. Mike
  3. ...and has just been posted 11 hours ago already.
  4. I know what setting it is (ChatLogUpdateEnabled IIRC), however I didn't notice this causing any crashes as the crash frequency was the very same before I used SturmovikServerControl. Nevertheless, I'll disable that feature. Mike
  5. While I agree that no prop driven aircraft has ever broken the sound barrier, I'd be careful with the rest of the statement. I don't believe that the claims of WW2 pilots about breaking the sound barrier in a dive are correct either, however... Spitfire PR.XIX PS852 is known to have reached Mach 0.96 is a dive on 5 February, 1952. The XF-88 went slightly above Mach 1.0 in a dive, and the propeller efficiency at Mach 1.01 was still 78 percent (see https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19930090296.pdf). This means that probably it's possible to exceed Mach 1.0 in a prop driven aircraft, it's just that no one did that because it made no sense. And if you don't insist on prop power only, Mach 1.0 at least has been passed with a prop equipped aircraft already. Mike
  6. I think that we already know that the SIM thread message thing is unrelated to the Server crash. At least I know, since I have had multiple crashes now where there was no single time when the SIM thread message log line appeared. Stopping the map rotation would surely clarify the Winter map thing, however I'm just not about to kill our server just to prove something that probably doesn't move the whole matter forward a single micrometer. If a dev would step down off his pedestal to let us know which check on our side would help them to further tackle down the issue, I'll try to make that happen immediately, but without any hint from official side, all I'm ready to do is to keep the ball rolling. Mike
  7. Next crash on our server was at Aug 03 12:55 AM - uptime 27:24 hours on the "Autumn" mission again (remember last two times it was "Summer", we yet have to see the "Winter" mission crash). What's been different this time is that the Windows Error Reporting wasn't triggered, instead DServer.exe just died "silently" without throwing any exception. No sorry sniperton, the crashes are completely unrelated to server activity or peak hours. We see both crashes when many people are online and crashes when no one is online at all. It doesn't even have any influence on the uptime whether or not the activity inbetween was high or low. Not at all. If crashes group up around a certain time of a day, IMHO this rather means that the "other end of the rope" (Master Server?) has peak time issues at that time. Concerning the "SIM thread message" thing, I can see several different incarnations of this message in the logs. The most reproduceable one is right when mission rotation is in progress, and it usually comes six times in a row: 18:46:49 ===== Rotation is in progress (2 seconds to wait before loading) ===== 18:46:49 Unhandled SIM thread message: 60 18:46:49 Unhandled SIM thread message: 60 18:46:49 Unhandled SIM thread message: 60 18:46:49 Unhandled SIM thread message: 60 18:46:49 Unhandled SIM thread message: 60 18:46:49 Unhandled SIM thread message: 60 18:46:51 ... Server name 'The Flying Ass Clowns' 18:46:51 Loading mission (...) Usually means that it can also appear more than six times... 01:13:27 ===== Rotation is in progress (2 seconds to wait before loading) ===== 01:13:27 Unhandled SIM thread message: 60 01:13:27 Unhandled SIM thread message: 60 01:13:27 Unhandled SIM thread message: 60 01:13:27 Unhandled SIM thread message: 60 01:13:27 Unhandled SIM thread message: 60 01:13:27 Unhandled SIM thread message: 60 01:13:27 Unhandled SIM thread message: 60 01:13:27 Unhandled SIM thread message: 60 01:13:27 Unhandled SIM thread message: 60 01:13:27 ... chat log reopened 01:13:29 ... Server name 'The Flying Ass Clowns' 01:13:29 Loading mission (...) ...or even not at all... 02:24:03 ===== Rotation is in progress (2 seconds to wait before loading) ===== 02:24:06 ... Server name 'The Flying Ass Clowns' 02:24:06 Loading mission (...) We have missions with no "SIM thread message" log line ever plotted at all, then we have singles... 01:04:11 ... chat log reopened 01:04:25 Unhandled SIM thread message: 60 01:04:26 ... chat log reopened ...doubles... 00:46:55 ... chat log reopened 00:47:05 Unhandled SIM thread message: 60 00:47:05 Unhandled SIM thread message: 60 00:47:10 ... chat log reopened ...and quadruples. 01:07:41 ... chat log reopened 01:07:46 Unhandled SIM thread message: 60 01:07:46 Unhandled SIM thread message: 60 01:07:46 Unhandled SIM thread message: 60 01:07:46 Unhandled SIM thread message: 60 01:07:56 ... chat log reopened Quadruples seem to be the "biggest" form of the phenomenon. Sometimes in the log there seem to be quintuples, but looking closer, you see that it's just a single that huddled up to a quadruple: 00:12:23 ... chat log reopened 00:12:24 Unhandled SIM thread message: 60 00:12:28 Unhandled SIM thread message: 60 00:12:28 Unhandled SIM thread message: 60 00:12:28 Unhandled SIM thread message: 60 00:12:28 Unhandled SIM thread message: 60 00:12:38 ... chat log reopened Even quadruples sometimes snuggle up: 23:02:33 ... chat log reopened 23:02:36 Unhandled SIM thread message: 60 23:02:36 Unhandled SIM thread message: 60 23:02:36 Unhandled SIM thread message: 60 23:02:36 Unhandled SIM thread message: 60 23:02:40 Unhandled SIM thread message: 60 23:02:40 Unhandled SIM thread message: 60 23:02:40 Unhandled SIM thread message: 60 23:02:40 Unhandled SIM thread message: 60 23:02:48 ... chat log reopened Interestingly, triples don't seem to exist. If we spot them, they are singles huddled up with doubles: 18:07:44 ... chat log reopened 18:07:44 Unhandled SIM thread message: 60 18:07:45 Unhandled SIM thread message: 60 18:07:45 Unhandled SIM thread message: 60 18:07:59 ... chat log reopened To sum things up, we see all kind of combinations of chained up occurrances: 21:49:29 ... chat log reopened 21:49:43 Unhandled SIM thread message: 60 21:49:43 Unhandled SIM thread message: 60 21:49:43 Unhandled SIM thread message: 60 21:49:43 Unhandled SIM thread message: 60 21:49:44 ... chat log reopened 21:49:54 Unhandled SIM thread message: 60 21:49:54 Unhandled SIM thread message: 60 21:49:59 ... chat log reopened 21:50:04 Unhandled SIM thread message: 60 21:50:14 ... chat log reopened I must admit I fail to see any pattern in here. Mike
  8. The only thing better than a Jug is... a pair of Jugs Mike
  9. Absolutely agree, no need for a mudfest, it's just the lack of feedback that wears out on the affected users, in this case server operators. Can't think of a good reason why there's never been any word on the dreaded "SIM thread message" thing from official side either. Nevertheless... where have we been? Ah, next crash: Aug 01 9:31 PM - uptime 24:17 hours One more observation: I have just checked the logs to see how many times which specific mission crashed. During the past weeks, we are running the very same mission on the Stalingrad map, on all three available seasons (Summer, Autumn, Winter) in random rotation. From the logs I could check 9 recent crashes. Crash 1-7 happened on the Autumn map, crash 8 and 9 on the summer map. No crash on the winter map. Coincidence or a reference to the underlying issue? God knows, and maybe - hopefully - devs do. Mike
  10. Thanks Von-Target, it's a pleasure for us to give you an enjoyable time! Mike
  11. Since the question came up whether a Henschel could kill a KV-1: I've put this up for a test, placed a Henschel and a KV-1 on a map so that the Henschel points at the KV-1's back from above, in order to attack the alleged "sweet spot" which is supposed to be the top cover of the engine area, right behind the turret. Turns out that I can put as many MK 101 bullets in there as I like, no damage. So I tried from the side, shooting the tracks area: No damage. Tried up front, no damage (as to be expected). The only spot I could find where I can kill the KV-1 with 30mm guns is when I shoot at the lower half of the rear and of the KV-1's body, so to say at the bottom belly of it. That way, after 17 hits with MK 101, the KV-1 blows up. Practically I'd say it's impossible to put that many bullets exactly into that area in flight. See attached track. Mike KV-1 vs Hs 129 v1.2018-08-01_17-15-42_00.zip
  12. No Information available. This is a sad example of complete absence of customer care. I mean we server operators are not supposed to be the dumbest people on earth, therefore we could be valuable assets in tracking this bug down. But instead we're left here with nothing, no information, not even a confirmation of this issue. It simply cannot be our task to narrow down the issue, especially when we're being ignored like that. Mike
  13. Can't stress that enough. According to L.Dv.T.2129 B-1 und B-2/Wa, setting the group switch on the Henschel's stick to position 1 would fire the Mk 101/103 only. This means that ingame the weapon should be alone on one of the two triggers, too. Mike
  14. A few things you might want to try: Run the game in "windowed fullscreen" mode instead of true fullscreen mode. Basically that's disabling the fullscreen mode and then selecting your screen's physical resolution for the game. Update to Windows 10. Mike
  15. We've had our next crash, too: Jul 31 9:14 PM - uptime 76:29 hours It's just random. One feeling I get when looking at the list of available dogfight servers is that the more AI you have on your missions, the more you suffer from this issue. Just a feeling, no hard facts. Mike
  16. It's a nice flightseeing plane, but to me that's it almost. I don't feel comfortable in it whenever I know I'm gonna meet something that can shoot back at me, be it ground targets or other airplanes. Especially against Trucks with AA guns I sometimes think to myself "if I had an IL-2, I could have swallowed 100 times as many bullets and still go home on both legs" while I'm going down for another belly landing with smokepile in the weed on my brave duck. That's the only part that doesn't feel right to me, but I cannot back this up with real life data: I thought of the Henschel being a tougher plane that could take quite a punch without suffering critical damage, however ingame I'm going down with shot up engines after first, latest second AA hit. Mike
  17. Just for the record, the server is still up with no crash since Jul 28. Uptime right now is 71 hours. Mike
  18. Why would you shoot little hitler if maybe with patch 3.006 you could get a device to tickle him to death? Mike
  19. Why would any of these want to follow a Stuka in a tight sustained turn? It this was a relevant criteria, we would still fly biplanes. Mike
  20. No. And I don't even need to read further. Mike
  21. Didn't want to sound rude, it's just that some things come around again and again and again and again and... Maybe it's easier just to link to something I've posted concerning the same matter almost half a year ago: https://www.sas1946.com/main/index.php/topic,58022.0.html Mike
×
×
  • Create New...