Check Part III P. 4.

max  taxi (MTW) = 221.000 lbs
max take off (MTOW = 220,000 lbs
max landing (MLW) = 198,000 lbs
maz zero fuel weight (MZFW) = 184,000

The best thing I did was print the manual.

It is true that Captain Sim has weights are somewhat different from real world weights.  Since I assume CS would be as able to discover the real weights as you or I, I am also assuming this was a design decision made for reasons I could not even begin to guess about.

I am also assuming that having chosen those weights they designed the aircfraft to operate properly around them.  Since operating within those parameters is working for me, I would have to be convinced otherwise.

I usually make fairly short hops, because with everything else I am doing with this a/c right now, I would need 48 hours every day!  So I'm fairly light, and my vref is surprisingly low, but seems to work.

If you want to edit your weights, you're a braver man than I 

I loaded up this afternoon to find my last load still there.  I thought ACE reset, but I have all my pax still from my last flight, and it wasn't saved -- just the same airplane.

Have you tried starting your right engine even after the artificial horizon tilts on GPU? �Worked for me.

Agreed this is a problem. �Might take a little longer than 20 minutes, because I usually start 30 minutes before scheduled departure and push and start five before, but close enough. �I would pay to register FSUPIC if it would fix it.

If you want, you can try GPU from beginning, just forgetting the APU entirely.  When I did that this morning although the bug struck (I have Flight Keeper, so I get an alarm and the copilot comments) and the artificial horizon tilted, I could still start the engine since I had bleed air and power.  Why that would be, I don't know.  I'll perform the same experiment now just to make sure.

I forget which thread I posted it in (been a busy beaver trying to nail down everything for a review that I know I'm gonna get crucified for if I fail to mention a displaced rivet). �But there was a pilot fired for not flying with an inop APU. �So I don't know if they cleared him at the gate or pushed him somewhere, but he fired up with the GPU.

Frankly this is the one issue that still bothers me a bit. �Not a whole lot, because I am usually done anyway, but it is something hard to excuse at this stage. �And playing with the loader is going to take more time on freight flights!

I have tried to follow the VNAV complaints to the best of my ability and just can't get worked up over them because of the the way I fly. �I rarely find myself changing published approaches at the last minute because I just let Radar Contact vector me, or make the concession to plan the whole route in advance and stick to it, realizing that in real life I would have another person to share the workload with. �"Realism" comes in different flavors. �VNAV is not the only terminal descent automation there is.

Like with anything else, it all comes down to what you like and what concessions you are prepared to make. �If I were really into VNAV all the way and it was that important to me, then I'm sure I would be more sensitive to any complications.

ADDITIONAL:  Using GPU only, you can start engines any time, even after artificial horizon tilts.