so ive taken out the cockpit, removed the camo panels and a few other bits to reduce complexity/scaled parts/parts in general, it now boots up quickly on my pc so should be ok for tablets / phones (ive left the merlin engine alone), Ag1 to close engine doors and activate the props, Ag2 for increased speed. 
Specifications
General Characteristics
- Successors 2 airplane(s)
- Created On Windows
- Wingspan 44.5ft (13.6m)
- Length 31.5ft (9.6m)
- Height 10.2ft (3.1m)
- Empty Weight 7,618lbs (3,455kg)
- Loaded Weight 8,297lbs (3,763kg)
Performance
- Power/Weight Ratio 4.062
- Horse Power/Weight Ratio 0.421
- Wing Loading 5.9lbs/ft2 (28.7kg/m2)
- Wing Area 1,411.1ft2 (131.1m2)
- Drag Points 7797
Parts
- Number of Parts 715
- Control Surfaces 0
- Performance Cost 2,248
@RamboJutter I hope you don't mind... I carved it down to 586 without touching the gear. HERE
@Type2volkswagen mby another 100 parts off but I've gone off the idea as is will look naff with stock undercarriage etc
@Rodrigo110 when I say it crashes at 2500 parts, it's actually on high physics. I refuse to put physics down lol
A mid-range device now is around the same as a high end device 4 years ago or even earlier. I found the 7-10FPS good enough to report and give feedback to Johndfg, though you are right; it’s oretty much unplayable. However, it’s not about being unplayable; it’s about being able to be playable up to around 1200 parts low physics (800 parts high physics) and even 2500 parts all low settings without crashing like your PC. @LiamW
How low do you think you can get the part count?
I count 7-10 FPS as unplayable but you are still right. It kind of works on lowest settings. My point however was that mid-range devices can’t do very much at 40fps and high physics @Rodrigo110
Alright, I tested Johnsfg’s B24 before it was released and I could run that at the lowest settings at around 7-10FPS. here it is. @LiamW
My PC with 8GB RAM, GTX1060 3GB, 2.7GHz dual core (8 years old lol) crashes with 2500 parts. Give me an example of a 2500 part creation you can run with 2GB RAM. My IPad Air 1 barely manages 200 parts on high settings. @Rodrigo110
A high end device from anywhere in the last 4 years is a reasonable assumption for the average mobile device. I can run 800 parts on high physics and highest graphics, but when I get to the limit (1000 parts - 1200 parts) I have to turn it to low graphics, but leave everything else up. I can get up to 2,500 part planes on all lowest settings at about 10FPS. @LiamW
@Rodrigo110 I specified mid-range and mid-age. Not everyone can afford high-end devices. Besides, I very much doubt many mobile devices can run a 1000 part build on high physics at 40+ fps
That’s not true at all. There’s a difference between mobile friendly and terrible computer friendly. A decent mobile devices from 4 years ago to the present will run the original just fine. A mobile device from that period that is decent will run up to about 1300 parts being ok. @LiamW
For it to be truly mobile friendly (40fps and higher on high physics) you’ll have to give it stock landing gear, delete minor aesthetic details, delete Merlin engine and use simple circular fuselages instead of angled mini pieces. Even then it will run slow on most mid-age or mid-performance devices but it would look terrible. In short: don’t bother making it mobile friendly, just make the best stuff you can @RamboJutter
@Rodrigo110 thanks for the info, im glad it works, saves me having to delete the more interesting bits.
This is mobile friendly, as long as you have a decent device from 4 years ago - present. People make it seem like mobile devices are terrible just because a lot of people own very low performance devices. My iPad Air 2 from 2014 runs the non-mobile friendly version at high settings just fine with over 30FPS.
@RamboJutter loads for me
@MaxToTheVolt ok, does it just not load or what? i can delete the engine and undercarriage to save another 100 parts ish
Still not mobile friendly.