Building Blocks Issues

[n122vu]

I am venturing into the great world of station building. However, I'm running into a couple of snags on my first attempt. I'm using the XR5 Vanguard as my launch vehicle and Greg Burch's Space Station Building Blocks. I'm running into an issue before I even get off the ground with the solar array (BP101) and radiator (BR101) components. Any time I try to load either component, whether as a new vessel in Orbiter, or as a payload in the XR5 I get a CTD. (thanks countdown84 @orbithangar for giving us the configs to do this). I can't load them in Kulch's Universal Cargo Bay because, as I mentioned, I can't load them as vessels into Orbiter.

Orbiter.log is as follows...

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Devices enumerated: 3
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
Found 0 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module OrbiterSound.dll [API v.060425]
Module AttitudeMFD.dll [API v.060425]
Module AutoFCS.dll [API v.050206]
Module GPCMFD.dll [API v.060425]
Module ScnEditor.dll [API v.060425]
Module transx.dll [API v.060425]
Module ExtMFD.dll [API v.060425]
Module CustomMFD.dll [API v.060425]
Module Telescope.dll [API v.060425]
Module InterMFD51.dll [API v.060425]
**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 32 bit
Stencil buffer: 8 bit
Render device: Fullscreen 1280 x 1024
Device has hardware T&L capability
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll [API v.041022]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll [API v.060425]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll [API v.060425]
Module Deimos.dll [API v.060425]
Module Galsat.dll [API v.041022]
Module Jupiter.dll [API v.050206]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll [API v.041022]
Module Europa.dll [API v.041022]
Module Ganymede.dll [API v.041022]
Module Callisto.dll [API v.041022]
Module Satsat.dll [API v.050206]
Module Saturn.dll [API v.060425]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll [API v.050206]
SATSAT Mimas: Terms 113
Module Enceladus.dll [API v.050206]
SATSAT Enceladus: Terms 33
Module Tethys.dll [API v.050206]
SATSAT Tethys: Terms 101
Module Dione.dll [API v.050206]
SATSAT Dione: Terms 59
Module Rhea.dll [API v.050206]
SATSAT Rhea: Terms 68
Module Titan.dll [API v.050206]
SATSAT Titan: Terms 100
Module Hyperion.dll [API v.050206]
SATSAT Hyperion: Terms 595
Module Iapetus.dll [API v.050206]
SATSAT Iapetus: Terms 605
Module Uranus.dll [API v.050206]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll [API v.060425]
Module Ariel.dll [API v.060425]
Module Umbriel.dll [API v.060425]
Module Titania.dll [API v.060425]
Module Oberon.dll [API v.060425]
Module Neptune.dll [API v.050206]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Module Triton.dll [API v.060425]
Finished initialising world
Module XR5Vanguard.dll [API v.060425]
Module ShuttleA.dll [API v.060425]
Module ShuttlePB.dll [API v.041022]
Module DeltaGlider.dll [API v.060425]
Module UCargoDeck.dll [API v.060425]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh


Any ideas? I checked the \Meshes folder and confirmed both meshes exist. Could there be something off in the config files? (see attached for each module, changed to .txt for uploading)

Any thoughts/advice here would be greatly appreciated.

Regards,
n122vu

 

[Arrowstar]

It seems that one needs to install the SSBB4 package before one installs the 4.1 package for the whole lot to work properly. Give that a go, it may resolve your issue with the meshes. It did with mine.

 

[Zatnikitelman]

Make sure the name in the scenario file matches the name of the craft's .ini file found in orbiter_base\config\spacecraft

 

[Biscuit]

I've ran into problems like this where when I manually edit a scenario file, I accidentally leave a blank line in the 'ships' section ... it would give me an error similar to what you are getting.

Not sure if that's the problem you have, but it something to check that I keep overlooking.

 

[James.Denholm]

Why not post the scn file here? It'll be something realy simple and obvious, it almost always is (I don't mean this offensively or anything...) Other eyes reveal other answers.

As a side note, I don't think the non-animated modules are sc3 crafts. Anywho.

 

[n122vu]

I did try the installation of 4.0 then reinstalling 4.1 modules to make sure I had everything. And actually, until I installed countdown84's updated cfg files, these two modules were not even available in the Scenario Editor or the XR5 Cargo list.

I haven't manually edited the scenario file (launching the first modules, so no copy/paste action yet). I am simply adding cargo automatically using the built-in XR5 cargo bay or also attempting adding station modules as a vessel and attaching them to a U_Cargo_Deck instance. If there are blank lines in .scn or an .ini mismatch, I would guess it would be caused by one of these addons, but I will verify to make sure.

I'll post the .scn file this evening (at work now). Not sure if the .scn will reveal anything, as the problem doesn't occur until I add a new vessel (the BP101 or BR101 via the Scenario Editor). The scene never gets redrawn and may not get captured by the current state scenario file. I will post it though.

Thanks for the feedback all. I appreciate the help.

Regards,
n122vu

 

[GregBurch]

If you're using the "aftermarket" .cfg files, I can't offer any help, since they are total magic to me. Personally, I never use the native scenario editor, but rather just manually create scenarios by cutting and pasting and manually editing elements ... all very primitive, but it works for me.

I'm also afraid I don't test for compatibility with anyone else's addons. All of which may seem pretty "antisocial," but I'm so caught up in doing my own thing that tha's the way things are ...

 

[n122vu]

If you're using the "aftermarket" .cfg files, I can't offer any help, since they are total magic to me. Personally, I never use the native scenario editor, but rather just manually create scenarios by cutting and pasting and manually editing elements ... all very primitive, but it works for me.

I'm also afraid I don't test for compatibility with anyone else's addons. All of which may seem pretty "antisocial," but I'm so caught up in doing my own thing that tha's the way things are ...

Thanks for replying, Greg. I know the issue is not with your addons, and it shouldn't be your responsibility to make sure your addons are compatible with someone else's modification of them. I don't expect you to solve a problem that someone else created with your work.

I will probably reinstall the building blocks and work on getting the hang of manually editing .scn files. Time has been the major issue in my not trying station building before, and with the addition of the XR5 and Kurch's new cargo deck, I thought I would give it a shot to see if it could be done within Orbiter instead of manually editing.

I'll still post the .scn file later today to see if anyone can see something out of the ordinary.

Thanks again,
n122vu

 

[n122vu]

Scenario File

For what it's worth, I have attached the text from the scenario file just prior to attempting to add the solar panel array BP101. If anyone cares to check for anything you might think is out of the ordinary, here it is. Otherwise I will probably begin manually setting up the file.

I will also try adding the solar panel and see if anything gets saved to the current state scenario file after.

Thanks in advance for any help.
n122vu

 

[n122vu]

Scenario File with BP101 Added

Ok, I managed to get the Scenario Editor to load the BP101 module without a CTD by unchecking the 'Set camera focus' option. Attached is the text from the resulting Quicksave. Can anyone see anything in the BP101 area of the ships section that would cause a CTD?

Thanks again for any help.

 

[ar81]

Use this tool
[ame="http://www.orbithangar.com/searchid.php?ID=3201"]Orbiter diagnostic V0.2[/ame]

 

[n122vu]

Results of Orbiter Diagnostic attached. Did see several missing meshes related to Big Space Plane not being installed, among other things. However, I didn't see anything regarding either of these modules or the scenario I am loading.

I'm still at a loss, as even adding this module manually results in the same issue.

My next course of action will be to install SSBB 4.0 and 4.1 and the XR5 to a clean Orbiter installation to see if the issue persists in that environment. Will post results.

Thanks for the suggestions and help. If anyone has any ideas, please let me know.

Regards,
n122vu

 

[itchythemouse]

in your config file for bp101 instead of having "Module = Spacecraft3"
put "Module = Spacecraft\spacecraft3", same thing with br101
that should fix the problem

 

[GregBurch]

in your config file for bp101 instead of having "Module = Spacecraft3"
put "Module = Spacecraftspacecraft3", same thing with br101
that should fix the problem

Wow -- is that really the glitch?

If so, it's a left-over from a weird little typo from 4 versions ago ... aren't computers GREAT!?!?

 

[James.Denholm]

One day, computers will be able to completley and utterly remove errors and typos.

When this happens, humans will be redundant.

 

[pattersoncr]

One day, computers will be able to completley and utterly remove errors and typos.

When this happens, humans will be redundant.

As my old Captain always used to say "Someday, computers will work for us."

 

[James.Denholm]

As my old Captain always used to say "Someday, computers will work for us."

*snort*

Or, we will become their slaves.

Or, they will kill us all! Fair enough, that's what I'd do.

 

[n122vu]

in your config file for bp101 instead of having "Module = Spacecraft3"
put "Module = Spacecraftspacecraft3", same thing with br101
that should fix the problem

That was it. Thanks for the tip! Now I have something to do this weekend LOL!

Greg - no worries. I'm just glad I was able to track down the problem.

Thanks to everyone for your input and help on this one.

(thanks also ar81 for that tool. I was not aware it even existed. Will save me some headaches, and probably some forum posts in the future )

Regards,
n122vu

 

[ar81]

One day, computers will be able to completley and utterly remove errors and typos.

When this happens, humans will be redundant.

It will be a time when humans have understood how human intelligence works. Nowadays it is mostly unknown. You only have simulation of intelligence, not real intelligence.

Simulation of intelligence is like a bike or a hammer, a tool that multiplies human capabilities, but a tool after all.

Results of Orbiter Diagnostic attached. Did see several missing meshes related to Big Space Plane not being installed, among other things. However, I didn't see anything regarding either of these modules or the scenario I am loading.

I'm still at a loss, as even adding this module manually results in the same issue.

I found these relevant errors. It looks like you have missing modules, and also you do not have BSP4 addon installed

c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]BSP4.ini[/B]. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]BSPC1[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP01[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP02[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP03[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP04[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP05[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP06[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP07[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP08[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SP204[/B].ini. (Do not use this scenario)

 

[n122vu]

I found these relevant errors. It looks like you have missing modules, and also you do not have BSP4 addon installed

c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]BSP4.ini[/B]. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]BSPC1[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP01[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP02[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP03[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP04[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP05[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP06[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP07[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SPP08[/B].ini. (Do not use this scenario)
c:OrbiterSTSScenariosSpace Station Building Blocks 41Station with BSP4 and SpacePlane2.scn
MISSING INI FILE [B]SP204[/B].ini. (Do not use this scenario)

I did notice those. It looks to me like those are all part of the BSP addon. Not the cause of the error, but definitely relevant. I was trying the building blocks and had not yet installed Greg's Big Space Plane. I'll install it this evening and run the diagnostic again. My assumption is it will remove these particular errors.

And since I don't like having any errors in a diagnostic list, i'll track down the others and get them resolved as well.

Thanks,
n122vu