Multiplayer model not loading #20
Comments
|
Yes, this helps a lot - it's basically not finding everything that has a relative path. |
|
Note, that yesterday I didn't see your model. |
|
That's even weirder, since yesterday I didn't change anything ! |
|
Oh and if it helps: |
On which commit were you yesterday? |
|
I don't know ? But I just changed the paths for the landing lights and flashing beacon, so the errors for those should not appear anymore - can you test this please, if it fixes this problem I'll do the same for all the other files. It looks like the paths inside the submodel XML files have to be relative to that XML file ( |
|
Meh, you have a version from 4 days ago … since then there were at least 10 commits, including the one introducing the custom model for the Silver Eagle, so it can be that very well. (Or wait, did you test with the P210N or the Silver Eagle ?) |
|
Okay, I just tested this locally with two instances at SAWH (where the scenery is light) with the Silver Eagle in one instance and the UFO in the other and for me the model was loading fine, including all the interior, lights and effects. I did not get any errors either, so I think it was due to you having a too old version installed. Please update and see if it loads normally after that. Oh, and you did make sure you have this repo in |
|
Tested again with 1e9cded, branch p201n: Silver eagle however showed no errors. |
|
Ahh … I tested only with the Silver Eagle ! :oops: |
|
I just tested using your command line parameters, and both the P210N and the Silver Eagle do load fine for me over MP and without throwing errors. I just checked - we are both on the same commit. So I really don't know what is going on here. The last thing I can think of is to try and delete your $FG_HOME/aircraft-data/p210n.xml file and see if that fixes it (I don't think so though). |
|
Wait - what aircraft did you use as observer ? The UFO, the C182 or the same aircraft as in the other instance ? The reason for that you did not get errors for the Silver Eagle could be that at that point, you had the Silver Eagle loaded in both instances where there are no problems ! I tested with the UFO in one instance and the P210N / Silver Eagle in the other. |
|
Hmm, now I tried it with the C182 instead of the UFO and got these errors: along with the interior not loading. |
|
ARGHHHH … Now I know why I could never reproduce your issues … I was always running FG from within the c210-family folder (for convenience, to be able to just type in |
|
So, with the last commit this should be fixed - can you check please @benih ? Works for me here. |
Console of the P210n instance: Console of the C182s instance: |
|
Neat ! That means that I got all paths right, except for the effect textures which I will further look into. The errors on the P210N instance come from the C182S, so that's something for you to fix @benih ! ;) |
|
Honestly, in have no clue what that line should tell me, but it’s the first time i have seen it. |
|
Meh, the effect textures have to be specified as `Aircraft/c210-family/Models/Effects/p210n-reflelction-px.png´ to be found properly over MP. So the last commit should fix the remaining errors - it's working for me. I've no clue though why the glass of the instruments became opaque when I changed those paths … |
|
Oh, looks like I messed something up because it's not finding the effects now either (over MP). So some more path changing … :roll: |
|
The metal control parts suffered from the same problem … should be all fixed now, and works for me. @benih, can you check one last (hopefully) time ? If you do, take a close look to the exterior - it should be reflecting, and to the metal parts of the interior (throttle, mixture, etc.) should also be reflecting. |
|
@TheFGFSEagle Surfaces are reflective. Tested both variants.
|
I get a bunch of error logs. May be related to the glider issue.
This was with two local MP instances, on commit acae356
The text was updated successfully, but these errors were encountered: