VS X3 - nested project files

Davidk · Post by **Davidk** » Fri Feb 19, 2010 7:12 am

I have VS11, and am reviewing a trial version of X3.

Several of my VS11 project files have nested project files - a main one contains one or more smaller ones. Makes building a project easier by assembling it with smaller pieces where that's necessary

On several tries to load such a project file, failure each time in X3, but the same file in VS11 loads up without a blink. X3 doesn't seem to like this technique. So ...

question - does X3 allow nested project files? If so, how?

Davidk

mitchell65 · Post by **mitchell65** » Fri Feb 19, 2010 10:58 am

Hi David
I do not have VS 11 but I have a project with three nested projects in VS 12. This opens OK in VS x3 so I should think a VS 11 project should open OK too. Can only think there is a problem with your VS 11 project file. Have you another or can you make one up in VS 11 and have another go!

Davidk · Post by **Davidk** » Sat Feb 20, 2010 12:31 am

So, it's allowed.

I tried again - must be the 4th or 5th attempt, but certainly the first one in a week - to load a nested VS11 vsp into X3. This time, it loaded up and played fine.

I get uneasy about an application that exhibits this sort of behaviour . . . .

gracias

davidk

Post by **jparnold** » Sat Feb 20, 2010 1:13 am

David
From time to time I too find strange behaviour with VS.
I still run VS v9 - I also have v10 which I don't use unless I need the extra overlay tracks as I have experienced a lot of problems with it and I haven't upgraded to later versions as I don't need their extra functionality yet.

I have never experienced problems with v9 until a few days ago when I was attempting to load a project I had been working on and just before it finished loading the project VS just shut down (disappeared off my screen with NO error message). I attempted to reload 2 more times with the same result. With my 'never say die' attitude I decided to try and load a different project which loaded ok. I then loaded the original project and this time it loaded. Behaviour I find totally strange.
The same problem occurred 2 days later and I overcame it again my loading a different project then loading the original.

I posted this so that others who find strange goings on with any version of VS may try loading something different before loading what they really want.

Maybe its a memory conflict problem I don't know but I have never experienced programs simply quitting without warning or error message before.