CFG

by RingoStarrreverse on 06/13/2007 15:56, 15 messages, last message: 06/17/2007 03:52, 1119 views, last view: 04/08/2024 00:00

Is there anything different about paradigm's cfg?

Because I am working on a map, and the only way I can get the textures I want without a shader error and sauer resetting the textures to those in default_map_settings is to call paradigm.cfg in my map's cfg, but it still says "paradigm by kaiser".


If I copy and paste that cfg, I get a shader error.

If I copy and paste the cfg into another cfg, then have my level's cfg call that cfg, textures reset (or crash)

   Board Index   

#1: bump

by George HarrisRS on 06/14/2007 00:56

bump

reply to this message

#2: bump

by George HarrisRS on 06/14/2007 00:56

bump

reply to this message

#3: Re: bump

by I_Am_A_Help_Vampire_Slayer on 06/14/2007 02:18, refers to #2

Try _reading_ ...
... like ... the first line ...

*groan@HELP-VAMPIRES*

reply to this message

#4: What?

by RingoStarrreverse on 06/14/2007 03:53

What?

Right now I am concerned about the crashing due to shader errors, not the mapmsg.

This only happens when copying the SAME text in Paradigm's cfg and putting it in my own cfg, and then it either crashes, or reverts to the default textures...

reply to this message

#5: Re: What?

by I_Am_A_Help_Vampire_Slayer on 06/14/2007 05:09, refers to #4

Well that is truely strange;
it might help if you could share the offending files in question with someone.
If posting a link on this forum is too public for you, you might (I emphasize might) find someone willing to look/help on IRC. (irc.quakenet.org #sauerbraten)

I just tested copying paradigm.cfg to other.cfg, removing the mapmsg line and entering sauerbraten. Did an edittoggle, newmap, savemap other, edittoggle, map other ... no crash.
Have you tried that?

reply to this message

#6: I got it...

by George HarrisRS on 06/14/2007 06:40

I got it to work. I suspect it was Windows not reading the line endings correctly.

1) Open up the offending file in MacOSX

2) Copy and paste into a new document

3) Transfer to pc

4) Open in WordPad.



I suspect that it was some weird line endings that mac os x read fine but windows couldn't, but windows can read mac line endings...

reply to this message

#7: ..

by djGentoo on 06/14/2007 13:21

DOS and Unix text files are encoded differently, and as of OS X, Mac OS is based on Unix (Darwin, a BSD fork). Which means that OS X and Linux can swap files...

reply to this message

#8: Yep

by George HarrisRS on 06/14/2007 16:00

Yep, thats why I tried transferring it through Mac os.

reply to this message

#9: ..

by Acord on 06/14/2007 16:17

Try ConTEXT. Just a good text/code editor that doesn't screw around with the formatting/line breaks etc.

reply to this message

#10: ..

by djGentoo on 06/14/2007 16:19

^ Nope. It won't work.

reply to this message

#11: ..

by tentus_ on 06/14/2007 17:11

If you open the file in Notepad and it looks all horrifying, reopen it in Wordpad and hit Ctrl+S. This will windows-ify it, and Notepad will read it just fine. I do this all the time in Windows with HTML documents I receive from clients and coworkers.

reply to this message

#12: Re: ..

by HydraPheetz on 06/15/2007 06:57, refers to #7

DOS/Win32-style newlines use a sequence of one carriage return followed by a newline, UNIX-style newlines are just a newline, and OSX-style newlines are just a single carriage return, IIRC.

reply to this message

#13: Re: ..

by SanHolo on 06/15/2007 18:58, refers to #12

No, OS X newlines are the same as on Unix, a newline, on Mac OS <= 9 it was a carriage return. ;)

reply to this message

#14: Re: ..

by SanHolo on 06/15/2007 19:08, refers to #14

http://en.wikipedia.org/wiki/Newline#History

;)

reply to this message

#15: ..

by GNU--.--Jeffz on 06/17/2007 03:52

if the program crashes, write a patch and submit a fix.

reply to this message

   Board Index