OHM Blue Streak Woomera Patch

[OrbitHangar]

Author: algol

As a patriotic brit I like to download anything related to british space programmes.
If like me you downloaded Notebooks Blue Streak F2 (SC3) add-on, only to find that it CTD's (Crash To Desktop) if you go anywhere near it. I have patched both the bases. (Pity, is a good add-on!)

Something in Notebooks add-on  causes the Woomera 6A addon to CTD also.
I've just spent two mornings sorting through both base .cfg files to get it all working again.
Just re-install both add-ons and then this patch over them, following folder hierachy, of course.

(Orbiter doesn't like a lot of multiple blank lines in it's .cfg files, had to delete a lot. And had to hide a perfectly good mesh (In section 10) before it would behave.)
  
Hopefully a few less frustrated British Orbiteers will thank me.

DOWNLOAD

 

[Notebook]

Very nice, wish I'd thought of it...

Edit:
Had a play with a clean Orbiter install with F1, F2, ImpactPoint and 6A addons, with SC3 and Velcro Rockets as required.

Works fine as far as I can tell, I have a Presario R4218E (XP SP3) laptop and a PC box (Vista). I could never get ImpactPoint to run on the laptop at the same time as any of the others, but would work ok on its own. Sometimes it would all work on the PC, depending on the tide.

Always thought it was a memory or graphic card problem, as removing modules, and sometimes swithcing off Cloud-Layers would fix it.

Looks like its the .cfg, well done to Algol for editing.

I'll try and keep it shorter next time.

N.

 

[algol]

Well, It could have been. the thing is that Woomera 6A worked fine before 6B was added gaps and all. The main culpret seemed to be a mesh is section 10. I divided up the CFG file into small sections, then added the sections until I got a CTD. then picked through that section. The weird thing is that the mesh in question appears elsewhere in Woomera 6A with no problem at all, the syntax in the .CFG file is fine and the mesh checks out also. It could be a memory thing lie you said, you've got a load of small individual meshes in the base, it might be making the pc work too hard, I don't know.
The funny thing is that when I tried to mask the launch pad on 6B just but adding a block (Cut and pasted with a small bit of edititng.) it would CTD again, confusing!
Apart from that keep making those add-ons.

Algol.

 

[Notebook]

Yes, lots of small meshes, I got carried away with the railings! Made a choice early on to make a selection of railings, rather than big meshes in 3DS Max. Thought it would be more flexible. With hindsight that was wrong. ended up with a very large .cfg and very confused. Nearly dumped the whole thing.
6A is a bit of a mess, dosen't need the two decks, and I can't think of what structures to put in-between.
The lessons will be useful for Spadeadam and Kourou when I get around to those.

Going back to the F3(DLL) now, so lots of C++ questions in the future. That should make me popular...

N.

 

[Scruce]

Good that someone remembered the UK's "shelved and forgotten" space program

 

[8bitgamer13]

Still doesn't seem to work. I'm using the legacy Orbiter 2006 P-1 mind you- I kept it for Project Mercury 5.0.

 

[Notebook]

Sorry about that, it was my earliest attempt, and I wouldn't do it like that now. If you see #2 and #4 above, the comments still stand.

I'm afraid I won't be doing anything with it soon, got a thread to finish, and then I'd like to get into Orbiter 2016 tile format.
Eventually, it will re-appear as its fundamental to the Blue Streak story.

N.

 

[Notebook]

I've tried Woomera6A on three machines, and its working ok.

Have you tried installing just 6A on a clean Orbiter2010P1?

N.

 

[IronRain]

Just to confirm (as someone who uses this add-on regularly); it works for me too on 2010P1.