Don't worry about fixing the models you already have up. The XSI scene can be scaled easily enough, and if the mod tool can do batch conversions that should make dealing with that easy enough.

Perhaps I did not told you it myfist0 but I have intentions from upload them by packs or at least many at one week but not when I convert them. I have a long list of priorities but always I finish all them.

Let me disagree with you:

The main problem of Sins of a Galactic Empire (iam use R955 version for my SoseRebelion 1.04) ,

 massive errors in files .galaxy

Because of the above problems with Sins of a Galactic Empire , I chose to base my Mod on SoSE:Rebellion Requiem 4.2.(I am interested mod's in the universe StarWars)

This mod works fine when playing VS 2 or more AI opponent's on Large Map (250+ Planets).

And i not have  problem with the computer's performance.

Please understand me correctly.
I like the idea of Sins of a Galactic Empire , but at the moment, an avalanche of large and small bugs make it almost not playable.

Just curious, how can you test the amount of errors with dev.exe? is there any guide?

About the re-scale I´m not sure if I like it, first it needs a lot of work, not only on models, the particles must be made with the new scale, second I do not know if it is a zoom problem or what but nothing look equal of great than before. Third the re-scale clearly affects to the game speed because units movement is faster and specially the proyectiles. all these things go faster. 

About MAXSHIPSLOTS0, it was my first change at game, I have made it for build big fleets and I have increased the default fleet from IA for each type of IA (agressive...). Only one comment, at the IA settings, better do not use a high amount value of units or specially at small maps you will not be able win to the IA. Other changes from me are the resources but it is a small trouble because if you increase them, at big maps you will have a lot of resources. Probably it can be made better because if it is low, at small maps you have low resources.

Your mod? If its just for your own use that's no problem, but if you're wanting to make a Star Wars mod to release too you really should get permission.

But I don't think you understand my point. The great difference in size between a tie fighter and an Executor class Star Dreadnaught means you cannot have the Star Wars ships to scale in the same way the Sins ships are. That means you have three options.

1. Make the planets bigger and greatly increase their gravity well radius so that the Star Dreadnaughts can fit. However, larger gravity wells hurt gameplay performance, and just looking at Nomada's screenshots you'll see that he would need to make planets several times larger to just allow them to make turning somewhat manageable. And from what I've understand people who've tried it say the lag this creates makes it unfeasible.

2. Scale down all the ships, so that a TIE fighter is significantly smaller than a fighter from Sins. This is what SoGE did, and it has nothing to do with the .galaxy error messages, and is really the only valid option if you want to keep things to scale.

3. Abandon having all the ships to scale. This is what Requiem did, both because some of the mods it had were not to scale with each other and because the Executor was the only ship that caused problems, therefore it made more sense just to have it much smaller than it should be rather than change everything else in the mod.

I think you mean this.

Interesting, I have seen how dev runs and clearly it can not be trusted at 100% because probably it compares the original lines with the new lines (position of lines) and it gives errors when a different line is at a different position. 

About the re-scale............I recieved a run time error and I´m not sure about if I go to use it. There is a chance that I ignore the scale realism with planets, at the end, there is one thing very true, the planets can not be conquest, they can not be destroyed at 100% and they are not no more than a simple beautiful object.

No, it usually can be trusted. The error it may be giving might not stop your mod, but if it gives a warning at a particular line it is expecting something in your modded file that isn't their, or it found something it is not sure about. It does not have any knowledge of the original files.

This is just the Dev.exe recreating the settings file, if you just played the normal game or if the game updated.

This is an actual error. Sins files are not like XML (I think EaW had that). You can't just put which lines you want, if you skip a line, even if it is just to leave it blank, you can screw up the entire file parser.

In this cased, it is expecting the line "requiredShip" at line 22, but it is finding "randomShipCount 0" instead.

Same thing with this one, the meshes in Rebellion added an extra line "maxDiffuseMipLevel". It will not crash the game if you leave this out in txt but if you convert it to bin to improve performance you will have issues. You're probably doing this if you used an old version of convertXSI to get your models into .mesh. If you have python installed on your PC I have a script that can fix it if you really care that much, but its pretty trivial.

Just add the line it is expecting. Just look for an original file that uses the same syntax and use that as a reference. In this case (indentation did not save unfortunately, but that is also important), you just didn't label your required ship section.

instantAction
buffInstantActionType "SpawnShipsAtPlanet"
instantActionTriggerType "OnDelay"
delayTime 0.000000
spawnShipsLevelCount 1
spawnShips
minFleetPoints 50.000000
maxFleetPoints 51.000000
requiredShipCount 1
requiredShip
type "InsertShipHere"
minCount 1
maxCount 1
randomShipCount 0
spawnShipsArrivalDelayTime 1.000000
spawnShipsHyperspaceSpawnType "FleetBeacon"

No problem. I wrote above - for my personal use.

I think the size of the Executor is relative value (not absolute) in the games.
It must be larger than any other ship. This is implemented in the Requiem.

IMHO the performance issue - the main to create mods. If the for maximum performance must
sacrifice aspect ratio (within reason), I think it should be done.

Technical Data Length Executor  was 19,5 killometer, I think in the game  do so unnecessarily.

SoSE strategy and not a space simulator )
Enough to make it large visual.

A lot of games that are very interesting, have low performance on very powerful computers.
And for this reason it is not popular.

I repeat - in my opinion, the performance is what counts!
Lags ,delay , freez no one delight

 If dev.exe gives assert in this place you have a problem.
And on some computer configurations can be crash.

 Just some errors are critical to the program, and others are not.
But ideally there should be no "assert" at all.

 If a 1st Mod gives a lot of "assert" and the other Mod does not, then perhaps in the first mode is the problem - or am I wrong?

You do not need to scale UVs, texture or tangent.

In XSI explorer, expand the rootpoint, then I select the 1st mesh point, shift select the last mesh point, then I ctrl select the mesh. 

Select scale and scale the model on all 3 axis at the same time.

once it is in the final size, select the mesh only and left click in Transform, freeze all transforms.

Select all the mesh points as above, left click Transform, Freeze Scaling

Select mesh, Freeze M (M is Model, near bottom), Freeze is the whole scene, I usually do that before export.

Export and test

Save Scene 

Be nice to see the error, ahh, same as above I assume.

requiredShipCount 6
requiredShip
type "CAPITALSHIP_PHASERelentless"
minCount 1
maxCount 1
requiredShip
type "CAPITALSHIP_PHASEISDII_Escort_R"
minCount 2
maxCount 2
requiredShip
type "FrigatePhase_Wombat"
minCount 3
maxCount 3 
randomShipCount 0

 i think

requiredShipCount 6 is the groups

requiredShip
type "CAPITALSHIP_PHASERelentless"
minCount 1
maxCount 1

is a group

it uses the 6 to count lines down to the next section, you only have

requiredShipCount 3