Building Blocks Issues

[ar81]

What the diagnostic tool does not do is:
-Detect addons for older versions of Orbiter
-Detect missing files that are hardcoded inside DLL modules
-Detect text entries that apply to older versions of Orbiter

It can detect some problems within CFG and INI files.

 

[n122vu]

I now have another problem. Since neither of these modules initially had config files supplied with them (I reinstalled just to make sure, they are not there, which is why I could not find them in Orbiter until using the third-party ones), I am forced to use the config files that allow them to be used by the XR-5 cargo bay just to have them show up in Orbiter. I am assuming these were derived from config files that were supplied with the building blocks in an earlier version, as they contain the typo that Greg indicated was from such a version. The problem is, these config files have no docking ports or attachment points defined other than the one for the XR5 compatibility. As a result, I can't get them to attach to the rest of my modules for my station when on orbit.

Can anyone supply me with the config files from an earlier version that have these points defined? I searched Orbithangar but can only find v4.0 and 4.1.

I would work on adding the docking and attachment points myself, but I barely had time to get 4 station components in orbit (and discover I could not use two of them), let alone modify an addon. If I had such time, I would be developing my own addons which is what I eventually want to have time to do...

Trying very hard to contain my frustration as I love this addon as well as Kulch's URMS & UCD....

Regards,
n122vu


-----Double Post Auto-Merged 2/8/2008 at 08 : 53 : 19-----


Well, this space station is definitely going to be a labour of love. I have successfully attached the BP101 module. To do so, I created a docklist in the BP101.cfg, and used the docking port information in config\spacecraft\BP101.ini :beach:

Once I did that, went back to the scenario, released the solar array from the URMS and poof! We have power! :speakcool:

Now, just need to do the same for the BR101 radiator panel before my components overheat lol.

 

[itchythemouse]

Well i've been using greg burch's building blocks for a while now and i've configured docking points for almost every block so if you want any config files, pm the ones you need and i'll send them.
I'll also be happy to help with any other questions you have

 

[James.Denholm]

Whoa... wait, you're saying that your SSBB zip came without a bunch of configs? Damn, that's strange. Have you tried re-downloading it?

 

[itchythemouse]

no the normal SSBB.zip you download from orbithangar doesn't come with config files for the animated blocks, don't know why so i just made them my self it not that hard

 

[James.Denholm]

Ah. Did you install 4.0 BEFORE you installed the 4.1 patch? That's all it is, a patch.

 

[pattersoncr]

no the normal SSBB.zip you download from orbithangar doesn't come with config files for the animated blocks, don't know why so i just made them my self it not that hard

They're spacecraft3 vessels. They don't need config files. They have .ini files instead. These are located in the config/spacecraft folder. You would need config files to make them usable with the XR5 or to make them "addable" with the scenario editor otherwise, the .ini files are all you need.

 

[n122vu]

They're spacecraft3 vessels. They don't need config files. They have .ini files instead. These are located in the config/spacecraft folder. You would need config files to make them usable with the XR5 or to make them "addable" with the scenario editor otherwise, the .ini files are all you need.

...which is why they were a problem for me as I am using both of these methods

NBD though as I am getting the hang of adding the appropriate info to the config files. The information in the .ini files is the same that is needed, just in a different format. I need to get the hang of these anyway if I eventually want to create my own add-ons. Been brushing up on my C++ in my spare time at work, but haven't messed with the SDK yet. It does me some good to get my hands dirty on the real thing.

Again, thanks to Greg Burch for his great add-ons (Going to take the next load of components up on the BSP, kind of like a "joint venture"), as well as Kulch for the URMS/UCargoDeck and Doug Beachy for the XR-5.

Regards,
n122vu

 

[n122vu]

Still having problems

Ok, so I've managed to get the solar array and radiator attached. However, I am not able to deploy either module. I am guessing it is because they are using cfg files rather than ini and spacecraft3 functionality is being lost? But if I go into the scenario file and define them as, for example, array:Spacecraft/spacecraft3 vessels, then I get CTD with orbiter log showing that it could not find meshes. Very puzzling. Any thoughts?

Regards,
n122vu

 

[Cobalt]

Are you using multiple BP101 pieces?

 

[itchythemouse]

if you define them as x:spacecraft/spacecraft3 then orbiter is not going to know where to find the config,ini,mesh files to load that specific piece. you have to put it as BP101:spacecraft/spacecraft3 because orbiter looks for the name of spacecraft3 vessels in the first half of the semi-colen.

 

[n122vu]

Are you using multiple BP101 pieces?

No, only using one BP101 at this point.

if you define them as x:spacecraft/spacecraft3 then orbiter is not going to know where to find the config,ini,mesh files to load that specific piece. you have to put it as BP101:spacecraft/spacecraft3 because orbiter looks for the name of spacecraft3 vessels in the first half of the semi-colen.

Makes sense. I'll make the change this evening and give it a try. Thanks for the tip!

EDIT: This did work, sort of. I got animation ability back, but for the modules that are already docked, they became docked at weird angles. I am going to try again, this time using BSP and ar81's scenario generator for BSP, with the modules in spacecraft3 format as intended.