MobiSev

It's evidently not at shooting down missiles in MP at the moment while the TOR does.

How much “guiding” does the BK90 actually do? Can it pull G’s or is it only really capable of minor adjustments? For example, could I do the following if I wanted two MJ2s to come in from different angles without having to make a separate attack run? 1. launch one like normal 2. pull off a little and launch a second one Would the BK90 in this case pull hard to get back on course? I know that it’s just a glider, and the speed would be reduced.

If I have a human RIO, I do not crash at all. With Jester, it’s the luck of the draw How many use human RIOs and how many use Jester?

Several questions: 1. How often do you fly MP? I.e very frequently, or do you only get on DCS every now and then? 2. How long have you owned the 14? Had it since release? 3. What type of servers do you fly on? Heavy missions, or servers like the acrobatic server? I’m asking because, there have been several major bugs related to Jester that caused everyone to crash. After these crashes were addressed, it’s been a little more stable. However, it still crashes more frequently than it should for me and the around 50 people I play with. It might be the servers that we play on? Like, there might be information overload on some of the servers causing a crash?

I asked this a while ago and my question went unanswered for some reason. I think it auto reactivates. What really concerned me was the limit to authorizations, around 10. Idk what that means. Do I only get 10 authorizations before I have to get in touch with ED? Hopefully someone will answer is this time around....

just to make sure...you set the bomb laser code to be the same as the pod code, right?

you play MP or SP?

Technically its in early access. It's not the "release" version I think. I crash and everyone I know and play with crashes with the 14. It’s just not as frequently as it used to be. It’s only with the 14 too, other modules seem to be fine.

Well, it might be that way now, but once the missiles get updated by Heatblur, it shouldn't do that I don't think.

1. If you STT launch with a 54, you are essentially launching a glorified fox 1. It does not matter if it's an A or a C. I don't know about commanding it active, but if you lose lock once launched in STT, the missile will go stupid....at least that's how it should be lol. Right now, I think they just go active upon losing lock. This will change in the future though. 2. No, once the host radar loses track, the connection should be severed. The A models, since they have analogue tracking, do not have the capability to store the target's last known characteristics to calculate an intercept point. They should go stupid. The C's do have this ability with their digital tracking. Once the connection between host and missile is severed, the C will store the target's last known heading, alt, speed, etc. and fly to the point it should be near based on these characteristics. Keep in mind though that the C variant does not go active until it get's close, so it wouldn't be able to update the intercept point as it would have no way of knowing where the target is until it goes pitbull (that is, if the target didnt change directions before this point lol).

First part: I think it should be the same in the real airframe (at least it doesn't make sense otherwise). I think the only thing that's different between the two tws modes is who is controlling the tracking cone. It's still in TWS. It's just that the computer is controlling auto and the RIO is controlling manual. If you swap from auto to manual, as long as the RIO keeps the target in the cone, it does not make sense that you would lose guidance. Haven't heard anything about swapping from tws to PD-STT in the real airframe though. Second part: With the real 54, yes, I think the A models will be trashed as soon as tracking is lost before it goes pitbull. The C model, however, will continue to an intercept point and go pitbull 5 or so miles from that point. I don't think reacquiring TWS tracking will change these behaviors. It happens as soon as TWS is lost on a target. Someone please correct me if I'm wrong lol. I'm just going off what others have told me.

Ugh that’s kind of dumb...especially when there are other unit packs that are coming out as free DLC. If anything, they should be attached to one of the WW2 planes, since you wouldn’t be able to play on the WW2 servers without them anyway. If y’all would have done this, you would probably have gotten more purchases of these planes.

There’s a problem in one of the servers I play on that uses Combined Arms where you can see all unit waypoints (even enemy ones) when you swap slots. I was hoping that disabling spectator view of the F10 map would help, but idk

Just fly dynamic dcs :)

Currently, if you have the F10 map up and swap slots, you will be able to see all ground unit waypoints for both teams. Several questions: 1. How does swapping slots actually work? Upon swapping slots, is the game actually quickly cycling you through to spectators first before putting you in the desired plane? 2. If you join Spectators and open the F10 map, are you normally able to see waypoints for both sides? 3. Is it possible to disable spectator view of the F10 map? Maybe this would help/solve the problem?

title

Fixes to the crashing probably will not be fixed this patch. We need to make a lot of noise about it in the bug section (new threads with specific situations, not just adding on to an old one). From the posts from HB, I’ve seen they are unsure as to if it’s a problem on their end and said it might be a problem on ours. They said they are not able to reproduce the crashes, which makes me wonder how exactly they are testing. If they spent several days in some of the popular MP servers, they would start to see crashing a lot.

yeah i made it after i posted this lol

JF-17 Release Time Frame? Do we have a release time frame yet?

Do we have a release time frame?

I think, at least in my experience, as long as the target is still in the tracking cone, if you switch from auto to manual, the missile should still track to the target. Losing lock is different however. As of right now, upon losing TWS tracking either through changing modes, etc., ALL 54 models will leave their lofting trajectory, go active immediately, and kill the first thing they see. I see a lot of team kills because of this lol. The only difference right now is that the A models have smoke trails with the 60 having a better motor and the C being smokeless. The missile code will change though when HB is given permission to change it.

Crashing in multiplayer seems to be a pretty common occurrence from my experience. It isn't just me, everyone I've played with crashes enough to where it's a problem. It doesn't produce a crash log either, just straight CTD. My question is: What environment does the dev team use to attempt to reproduce bugs/crashes (i.e. how many testers, how long, etc.)? Could the crashing be related to a populated MP environment? Maybe the dev team could play a couple rounds on the Blue Flag and Dynamic DCS (DDCS) servers in an attempt to reproduce?

https://forums.eagle.ru/showthread.php?t=241316 I'm not sure they know what's going on at the moment based on responses to my post in the link above. I'm not sure how they are trying to testing for it (i.e. how many testers, how long, etc), but they said that they cant reproduce it at all. I'm thinking it might have something to do with large, populated servers and the information overload when stt locking? Maybe they need to focus their testing on an environment where many people are involved. Maybe try playing a couple rounds in the Blue Flag or DDCS servers to reproduce?

How are you testing it, if you don't mind me asking (how many testers per session, how long, etc.)? Could it have something to do with really populated servers? i.e. you might not have crashing if you are testing with only a couple people, but heavy servers might be different? A lot of information is calculated when you lock someone, get locked, etc. and it might have something to do with information overload causing a crash when there are many players in a server? As I've said before, there are times where I as well as people I know (people with pretty high end computers) go long periods of time without crashing before it starts to get bad again. Almost everyone I play with has crashing problems in the 14. I've noticed in my experience during the "non-crash" periods that it will sometimes stutter briefly when initially STT locking. Maybe this is an indication of this or information you can find useful?

In MP, do you use a human RIO or Jester? Because I also never crash when using a human RIO....although the RIO sometimes will... Also, how often do you play MP?