Menu
▾
▴
#2478 Carrier MP dialog broken
Hi there,
I was trying to set a carrier for MP, but when entering the multiplayer menu and selecting the carrier dialog, nothing happens and the console reports an error:
Nasal runtime error: No such member: carrier_dialog
1679.89 [ALRT]:nasal at /sim/bindings/menu/binding[527], line 6
Actually, it seems that it is currently impossible to set a MP carrier (at least as explained in the wiki), maybe this menu entry is obsolete?
Cheers,
chris.
I've been seeing tonight a MP-carrier, not set by me. But it was invisible to me, in spite of setting AI traffic on, adding the carrier in the list of scenario. So may be the menu is actually not functioning in 2020.3.4?
One for Richard to look at I think.
One issue solved, I was using:
--fg-aircraft=to match a directory where I have installed some devel version of the f-14b. Of course the mp-carrier was in the .fgfs/Aircraft/org... standard directory and that was the culprit, but not only.
Last edit: eatdirt 2021-01-10
Well, even it that works, it may need a bit of love though. I've tried vinson, works, but a lot of nasal errors pop out of the console:
Ok, I've been playing mp-carrier tens of times now with 2020.3.5. That's randomly working and most of the times, it is unusable.
The main issue is that the carrier model is not appearing on the pilot session. The mp-carrier is visible (as the little blue plane), so network seems to work. But the model visible remains the one of the AI, not the one of the MP, it is usually located nearby. When it works, I can see the AI model disappearing and replacing the little blue plane, and when this happens, the MP-Dialog indeed shows the carrier to be present.
Sometimes, I can make the MP carrier model appearing on the pilot session by forcing multiple times the reload of the AI-traffic, of the carrier (ticking/ unticking the relevant boxes), AND, I have to fly a few times very close to the location of the MP-carrier.
What I don't understand is why there is no other bug reports about this. I cannot believe it is only a local problem. May be other users confuse the AI model and the MP-model? Especially if you just start a session, they're located on top on each other...
Cheers,
Chris.
Was the MP carrier named Nimitz+Number, sch as Nimitz2?
The latest fgaddon master branch's Aircraft/MPCarrier has some improvements to multiplayer carrier behaviour, please see: https://sourceforge.net/p/flightgear/fgaddon/5309/
Would be good to know whether this improves things.
It's only been tested with Flightgear "next" branch, on which the new behaviour is enabled by default, with the multiplayer dialogue having a checkbox to enable/disable.
Hope that helps,
Hi guys,
I am editing this bug with some more tests and feedback done on the mailing list.
On 2020.3.9, in spite of a lot of Nasal crashes in the console, the crucial point to make the AI carrier fusing with the MP is to have AI/MP LOD details set to "High". Without it, it just fails 99% of the time I've tried. With it, it works all the times I've tested so far.
Cheers.
I've just pushed some fixes to FGData that should make the carrier appear regardless of LOD.
I'm working on making all of the carriers available as MPCarriers;
@cgdae This seems to work well with the auto select logic.
Hi there,
I have been off from carrier landing since a while. But I went watching top gun 2 at the cinema, then I could not resist to do some carrier landings again :)
All that to say that I gave a try on 2020.4.0 to set an MP-carrier, in vain. The infamous blue plane is there, but the model never gets loaded. I've tried all combination of the new options in the menu (latch, automatically enable AI etc...), toyed the LOD, tried High definition only, no joy :)
The MP session runs fine, I do see the plane of my other session on the radar, just no model loading. The Vinson AI model is a few miles a way and never get merged to the MP's one.
Maybe 2020.4.0 introduced some regressions?
I do see some errors
others on LOD
and a bunch of AI traffic errors (not related I suspect)
Cheers,
Chris.
Last edit: eatdirt 2022-06-24
I think i used MP carriers a couple of months ago and it all worked fine with a build from next .
Could the errors in the log about not finding .nas files, indicate that your fgdata is not from the
nextbranch?Also, is your fgaddon folder also from the
nextbranch (or maybe svn's equivalent, istrunk)? - this has quite a lot of the code that supports MP carriers, so needs to match the fgfs executable.- Jules
Damned... Copy paste of the old command line, you certainly right, I was calling the old carrier MP from my local folder... What a fool...
Tonight, I am redoing a full range of tests with proper arguments!
Last edit: eatdirt 2022-06-25
All right, woo! That works quite fine actually!! Well done!
I've noticed only minor things, happy to help fixing if I can:
- the MP radar display is no really clickable anymore, to set course recovery for instance. Still doable from the AI menu though.
- Something weird, my radar (on board F-14b) was still showing Vinson at 1.9 nm away, always. I mean, I tried to see what was there, but that virtual Vinson was moving with me, ahead of me.
- A slightly less minor issue, I did not manage to get the TACAN working at all (old version with the infamous blue bird, the TACAN was ok).
Check the console log on the F-14 for Nasal errors. It sounds like the radar stopped running.
F-14 develop has a new radar. This will be released soon. You might want to try using this.
When you say the radar shows Vinson 1.9nm away, that suggests that the AI and MP carriers are not "latched" (AI carrier's velocity is periodically changed to make it approximately coincide with the MP carrier), which would be a significant problem. Note that latching seems to go wrong if one pauses flightgear or replays then resumes.
BTW what do you mean by
MP radar display?The TACAN property values seemed to be set correctly for me with MP carriers a while ago, so i'm not sure what's going on here.
- Jules
Note that latching seems to go wrong if one pauses flightgear or replays then resumes.All right , I did no have the "always latch" option activated, but, you're right, I did a resume after a replay (trigger the replay by accident). I also did a resume of a session in which I crashed in the water by just repositioning the aircraft onto the carrier
It happens that I've found the logs of that session, and that is indeed nasty:
Then there is a long list of repeating messages:
they do end with some overflow it seems:
and ends by
Then I started flying again, the MP-carrier was there. For the radar display, I meant on board the F-14b, activating radar and picking up targets. In the logs, this appears like this (check out TGT Vinson 1.69nm, always at the same distance independently of my position). Note that this is after all the above errors: