169th_Moose Posted February 17, 2005 Posted February 17, 2005 Hi, First, thanks for your contribution to eliminate as much bugs as possible. My question is in regards of multiplayer. Is multiplayer more stable when hosting with overcast/thunderstorm missions with 1.1? The rain frozen in mid air effect dubed the Matrix effect, is it still there? 2nd part of my question. I know the Dev's dont support multiplayer air refueling but have you tried it with 1.1? The issue with the invisible boom, is it still there? 3thrd part. Friendly air defence, does it still shoot you down on take off? 4th. Is the Nuke effect that crashes servers still present with 1.1? Any confirmation on what was the cause of this with the present and previous versions? I've seen replies that multiplayer codes being improved. But these issues. Have they really been eliminated? Can you make and establish a confirmation? Thanks in advance.
SUBS17 Posted February 17, 2005 Posted February 17, 2005 The friendly fire bug doesn't occur if you get permission to take off first. [sIGPIC] [/sIGPIC]
Pilgrim Posted February 17, 2005 Posted February 17, 2005 Haha. Nazi sam operators. "Ze pajlot did not have clearance. Ze bastard must die" ASUS P4T533-C|P4 3.06@3.45|1024Mb Kingston 1066 rambus|ATI 9.... *EDITED* - Listen to Mods!!!
169th_Moose Posted February 17, 2005 Author Posted February 17, 2005 The friendly fire bug doesn't occur if you get permission to take off first. If you talking about friendly sams shooting you down, then no, this was attempted multiple times and you still get show down by the sams even though you asked permission to take off. Its not related.
bear.is.flying Posted February 17, 2005 Posted February 17, 2005 I thought the friendly sam issue was caused when you switched teams. The solution was to reconnect first and then select your new team. Intel Core i7-8700K @ 5.0 GHz // Nvidia GTX 1080Ti // 32 GB DDR4 RAM // 1 TB SSD
169th_Moose Posted February 17, 2005 Author Posted February 17, 2005 I thought the friendly sam issue was caused when you switched teams. The solution was to reconnect first and then select your new team. Yes we have notice to be one factor of this. But it also happend when starting from the initial coalition. Bare in mind also seem to be sproradic, since it does not happen all the time and not to everyone on the server at the time of flight. No matter what im getting 1.1 so I guess will wait and see :wink:
SUBS17 Posted February 18, 2005 Posted February 18, 2005 [ If you talking about friendly sams shooting you down, then no, this was attempted multiple times and you still get show down by the sams even though you asked permission to take off. Its not related. Yeah, I have found since I started getting permission first that I don't get shot down. I found this out a while back when someone mentioned it on the Lock forum. [sIGPIC] [/sIGPIC]
Xses Posted February 19, 2005 Posted February 19, 2005 I too saw someone post about requesting permission before taking off to cure the friendly sam problem. Gave it a try and its made no difference whatsoever. I request taxi.. and request takeoff when on the correct runway.. Still randomly cop the SAM launch up the tailpipe. No76_Xses
169th_Moose Posted February 19, 2005 Author Posted February 19, 2005 I too saw someone post about requesting permission before taking off to cure the friendly sam problem. Gave it a try and its made no difference whatsoever. I request taxi.. and request takeoff when on the correct runway.. Still randomly cop the SAM launch up the tailpipe. No76_Xses I've seen that post, I've tried it, request taxi, then, request take off. Boom friendly sam shooting up my six. I've tried multiple instances to confirmed issue, since presently I request taxi and takeoff almost all the time. Im 99% sure that it aint related....
Alfa Posted February 19, 2005 Posted February 19, 2005 Hi, ...Bare in mind also seem to be sproradic, since it does not happen all the time and not to everyone on the server at the time of flight. The friendly-fire SAM bug is believed to be fixed. But like you said, it is not a consistant bug, which makes it difficult to isolate the cause of it. Cheers, - JJ. JJ
Tracker Posted April 6, 2005 Posted April 6, 2005 I have tracked this FF bug a little. Situation 1: PlayerA joins game in progress and chooses aircraft slot x on either coalition, plays a while and dies. Switches sides chooses slot y and gets shot by FF and leaves game. PlayerB joins (same mission) and takes slot y. All of the entries in the log for PlayerA now say PlayerB. PlayerB gets shot after takeoff by FF. Situation 2: Mission incorrectly setup to attack targets and accidently includes one or more slots from same team. Switching planes fixes the problem because the other plane has not been set as a target for the AAA or SAM. Situation 3: Player Joins Mission, Plays on Team x and leaves. (this can be for any time interval, perhaps even days if server is still up) The player returns and this time chooses Team y. The mission seems to 'Remember' his previous choice, and he is shot by FF. When all else fails, Eject then read the manual. Oh, and a good wingman helps.
Tracker Posted April 6, 2005 Posted April 6, 2005 In 1.02 The frozen rain seems to be related to players renaming the High, Med and Low scenery files. In 1.02 the invisible boom interestingly seems visible in external views which indicates to me it is related to the code that 'tears through' very close objects. I have participated in refueling the Su-33 with 3 of us on the same tanker simultaneously. Once in position, the basket does appear. The nuke is a render eater and seems to be related to the runaway averaging we see when a players network connection is lost and his altitude and speed steadily climb to infinity. Similarly, an explosion that should be small scale 'runs away' and becomes very large and troublsome for the processors to render. This may also have ties with memory leaks that step on variables used for scaling. :cool: When all else fails, Eject then read the manual. Oh, and a good wingman helps.
Recommended Posts