[kalnaren]

Playing on FS2NetD. I'm playing with 1 other, I'm hosting. My friend is unable to change his loadout. It's not because of the "lock" button. He can change his ship, but over on the left where the weapons are usually listed he has NOTHING, and any weapon he drags from his ship over there disappears and cannot be re-assigned.

Any thoughts?

[captain-custard]

try creating another pilot , is he using a mod , what are you trying to play, check in your setup that you havent got host modifies loadout ticked ..... shouts  for real help



lobo


fubar

[kalnaren]

try creating another pilot , is he using a mod , what are you trying to play, check in your setup that you havent got host modifies loadout ticked ..... shouts  for real help



lobo


fubar

We're using the mediavp's, runing 3.6.10. Happens on any mission we try. "Hosts modifies Loadout" isn't checked.

[FUBAR-BDHR]

New pilot file would be my first guess as well.  After that have him run the debug build and attach the fs2_open.log from the data directory. 

[karajorma]

We're using the mediavp's, runing 3.6.10. Happens on any mission we try. "Hosts modifies Loadout" isn't checked.

Which 3.6.10 build?

shouts  for real help



lobo


fubar

* karajorma feels left out.

 

[Aardwolf]

Umm... tell the host to click the 'lock' button?

[captain-custard]

We're using the mediavp's, runing 3.6.10. Happens on any mission we try. "Hosts modifies Loadout" isn't checked.

Which 3.6.10 build?

shouts  for real help



lobo


fubar

* karajorma feels left out.

 

sorry , you were not online when i saw this but fubar was and lobo was probably hiding somewhere....

but if it makes you feel better if you had been online you would have solved this problem in seconds

[kalnaren]

Which 3.6.10 build?

5063

Umm... tell the host to click the 'lock' button?

As I stated in my OP, it's not because of the lock button. Clients are able to change their ships, just not the loadouts.

[karajorma]

And everyone is on the same build?

My only suggestion is that you run the debug builds and post the fs2_open.log from both PCs. That might turn up the cause.

[kalnaren]

And everyone is on the same build?

My only suggestion is that you run the debug builds and post the fs2_open.log from both PCs. That might turn up the cause.

Yea, there's just the two of us at the moment and we're both on the same build. I might try a more recent build and see if that helps, if not I'll be running the debug.