Random Hits OXP

[Tivva]

And here is my "description.plist"


As I have basically no knowledge of coding...I am completely at the mercy of ignorance to find out what this means.

I get the same too.
When using "get info" of the description.plist file it says it is a plain text file but text edit 1.5 won't open it. Can open all the other .plist files ok though.
(mac os 10.5)

[Eric Walch]

I get the same too.
When using "get info" of the description.plist file it says it is a plain text file but text edit 1.5 won't open it. Can open all the other .plist files ok though.
(mac os 10.5)

The bug is in the part:

Code: Select all

	<string>Ioollia</string>
	<string>Kr¸ger</string>
	<string>Luyten</string>

Delete the line

Code: Select all

	<string>Kr¸ger</string>

It contains an illegal symbol that makes the mac completely ignoring the plist.

And I also could not open it at first. I opened it with "Dascode" and saved it again. After that it did open in textedit.

[Eric Walch]

I have since 1 week an shader capable mac. And since today a cable modem. (Another world started now). So I downloaded the latest version of RH. After entering an anarchy system I had several pages of errors in my log.

Code: Select all

Oolite [shader.compile.fragment.failure] OOShaderProgram.m:231: ***** GLSL fragment shader compilation failed for griff_spacebar_rock.fragment:
>>>>> GLSL log:
ERROR: 0:20: 'diffuse' : syntax error syntax error
ERROR: Parser found no code to compile in source strings.


>>>>> GLSL source code:
#define OO_USER_DEFINED_BINDINGS  1
#define OO_TEXTURE_UNIT_COUNT  4
.....

All came down to two files: griff_spacebar_rock.fragment and griff_spacebar_solarpanel.fragment

When I removed the line:

Code: Select all

   //   diffuse += gl_LightSource[idx].ambient; \

in both files, the problems were over and the "OpenGL Shader Builder" said that the file compiled okay. Don't ask my why as I never looked as shader code and at first glance it just looked like a line that was commented out.

It it a line that can be removed?

[Westwood]

Dascode? What is that?

[Svengali]

Code: Select all

   //   diffuse += gl_LightSource[idx].ambient; \

It it a line that can be removed?

Yes. It is a comment. But I don't see anything wrong with it. Or is it a 'comment-problem' again?

[Griff]

@ Eric, yes it's ok to delete that line, as you guessed it is actually commented out, the bits of code inside that Light macro in the shader are really fussy, there must not be any characters (even spaces) after the \ symbol at the end of each line, I'd better check all those shaders for mistakes in case there's more of them

[Eric Walch]

Dascode? What is that?

It was just the first alternative editor I tried and immediately worked.

It is part of the developer package that is on the Mac installation disk. (Not installed by a default installation but as you are also on OSX it must also be on your installer disk). It is just an editor for easy editing code. That kind of editors often save their text files as plain text.

Griff: I now finally start to fully appreciate your shader work. Can see it now since a week in its full glory. Nice neon sign on top of the spacebar

[DaddyHoggy]

Griff is the god of rooftop advertising for spacebars and Constores!

[Westwood]

I doubt my Mac has shader capability....this is probably not the best place to ask (derailing of the topic and such ) but is there a topic where I can see shader/non-shader images in relation to eachother?

[Tivva]

The bug is in the part:

Code: Select all

	<string>Ioollia</string>
	<string>Kr¸ger</string>
	<string>Luyten</string>

Delete the line

Code: Select all

	<string>Kr¸ger</string>

It contains an illegal symbol that makes the mac completely ignoring the plist.

Thanks Eric
I downloaded a trial version of TextMate (free for 30 days)
Now works fine, but it took some searching to find the string to edit- I changed the umlauted letter to a plain 'u' rather than delete the line altogether.

Tivva

ps
@ LB - Nice touch adding lots of forum members names & forum handles to the scripting
looking forward to doing a hit on me

[LittleBear]

Think that was the problem. I'd just C&Ped a load of text in from lots of internet Elite pages as words for the generator (too lazy to type it all in ) and that one (German format?) u from an FFE system name meant the Mac refused to read the whole file! .


I C&Ped in the Oolite BB Member List as names for Victims and Posters. I then took a few out as they didn't really work as surnames (my handle included), so don't be offened if you are not on the death-list!

I'll put up a 1.3.6 with this fixed over the weekend.

Big thanks to Eric for spotting that one!

[Frame]

<string>who framed [random_hits_guard_name1] [random_hits_guard_surname]</string>

why not.,,,

Who framed Frame & I was framed..

would have made some interesting sentences

[JensAyton]

I know it was fixed in this specific case, but for future reference here’s how to work around the problem without extra tools.

And here is my "description.plist"


As I have basically no knowledge of coding...I am completely at the mercy of ignorance to find out what this means. :?

I get the same too.
When using "get info" of the description.plist file it says it is a plain text file but text edit 1.5 won't open it. Can open all the other .plist files ok though.
(mac os 10.5)

Workaround: use the File->Open… command in TextEdit (don’t double-click the file), set Plain Text Encoding to Western (Mac OS Roman) or Western (Windows Latin 1) and open the file.

If you still get the error, you need to use the command line:

Code: Select all

cd <path of folder>
cp -X <name of file> <new name>

This will create a copy of the file you can open using the Open… command as above. (To get the path of the folder, you can type “cd ”, then drag the folder into the Terminal window.)

Once you have it open, you can save it with Plain Text Encoding set to UTF-8, and then use as many umlauts as you like.

[JensAyton]

@ Eric, yes it's ok to delete that line, as you guessed it is actually commented out, the bits of code inside that Light macro in the shader are really fussy, there must not be any characters (even spaces) after the \ symbol at the end of each line, I'd better check all those shaders for mistakes in case there's more of them

That isn’t valid. Inside a macro, you can only use comments of the form: /* comment */ (with a backslash at the end of the line).

[DaddyHoggy]

Think that was the problem. I'd just C&Ped a load of text in from lots of internet Elite pages as words for the generator (too lazy to type it all in ) and that one (German format?) u from an FFE system name meant the Mac refused to read the whole file! .


I C&Ped in the Oolite BB Member List as names for Victims and Posters. I then took a few out as they didn't really work as surnames (my handle included), so don't be offened if you are not on the death-list!

I'll put up a 1.3.6 with this fixed over the weekend.

Big thanks to Eric for spotting that one!

I think "LittleBear" would work for any name of Native American origins...