What's there to hate? Looks perfectly usable, bit stiff maybe but no drama.
It's likely to be identical to DiRT2, but I don't have it so I can't make sure.
I'd volunteer if my situation were any different from Boosted's 
What I would like, though, is try myself at some (genuinely useful) plugins, so if you've got any ideas just pitch them my way
Already made one that starts a storm and makes you poop cocoa beans upon crouching (sneaking), but I wouldn't call that useful, apart from the brown dye.
What I would like, though, is try myself at some (genuinely useful) plugins, so if you've got any ideas just pitch them my way
Already made one that starts a storm and makes you poop cocoa beans upon crouching (sneaking), but I wouldn't call that useful, apart from the brown dye.
Fixed
On topic; If you opened an existing file, such as a bodykit template or any other template, a simple "Save" would overwrite that. If you worked with layers, it's almost certainly going to be a .psd, so searching for .psd modified today should yield the desired results.
€: Meh, completely redundant, sorry -.-
Well if the DWM is actually the cause, that explains why it didn't restart
You should be able to bring it back by restarting the Desktop Window Manager. Task Manager -> Processes -> dwm.exe -> End Process
It should restart automatically.
E: And no, I don't experience any issues with it on either of my W7 (x64 Ultimate) machines.
It should restart automatically.
E: And no, I don't experience any issues with it on either of my W7 (x64 Ultimate) machines.
wine 1.0.1 on CentOS 4.5, Uptime: 982 days(!), 12:24:41
But to the players with just a subset allowed, only the ones they're actually allowed to drive would show up coloured in the car selection screen, right?
Couldn't you just set /cars to the race cars and then use PLC to allow the safety car for just the safety car driver?
With the text dialog open, press and hold CTRL and select the desired colour via mouse.
This works for all text input dialogs by the way, including setup names, replay names, chat messages,... everything really
This works for all text input dialogs by the way, including setup names, replay names, chat messages,... everything really
The fuel system being the limiting factor wasn't an excuse for it being slow, but an explanation for why it doesn't produce more with a huge turbo.
The restart-at-deleted-start bug needs clarification. All is well when the actual race is restarted, but a per-person restart (i.e. Shift+R with more than 1 player on the track, which really is spec+join) will put you back to the deleted start, unless a new one was placed. The same applies to pit/re-join and normal (non-Shift-R) spec/re-join.
toUTF8 and fromUTF8 are already part of my LFSString class prototype, but that's far from ready. Note, however, that the multibyte charpages LFS uses are not UTF8 or UTF8 related and are indeed very likely to use 2 byte wide chars at most, I just haven't confirmed that yet.
I've done some prototyping as well, no actual splitting yet though.
trim_sequences passes all the test cases I could think of.
optimise also does what it's supposed to do, but does not detect redundancy over the full string width, it's limited to a sequence chain. This is because I wouldn't know how to achieve it with regex assertions and didn't want to iterate over the string, because the actual splitter is going to do that anyway. Put simply, it will correct: ^L^B^H^HSomething to ^HSomething, but ^L^B^H^HSome^Hthing will still have that redundant ^H between 'Some' and 'thing', i.e. ^HSome^Hthing
isMultiByte is completely untested, but it should work under the unconfirmed assumption that all multibyte codepages LFS uses do not have characters wider than 2 bytes. If your split point tests positive with isMultiByte, split one earlier and you should be fine.
As I said initially though, all of those are prototypes and haven't undergone any actual testing with PRISM / LFSWorldSDK, or raw captured strings from LFS for that matter.
<?php
php
/**
* Trim reset, default colour and default charset sequences from
* the beginning and end of the string (or strings, if an array is
* passed, in which case it will return an array instead of a string).
* This does not trim whitespaces or any other characters trim() trims.
*/
function trim_sequences($string)
{
return preg_replace('/^(?:\^[89L])*(.*?)(?:\^[0-9LGCJETBHSK])*$/', '$1', $string);
}
/**
* Strip redundant or chained sequences.
*
* Example:
* '^H^S^4Stuff^8^9Other stuff'
* becomes
* '^S^4Stuff^8Other stuff'
*/
function optimise($string)
{
$patterns = array(
'/(\^[012345679])+/', // colours and colrst
'/(\^[LGCJETBHSK])+/', // charsets
// full reset (col and cp) sequence ^8
'/(?:\^[0-9LGCJETBHSK])*(\^8)(?:\^[89L])*/',
'/\^8(\^[0-7]\^[GCJETBHSK]|\^[GCJETBHSK]\^[0-7])/',
);
// strip redundant / chained sequences
return preg_replace($patterns, '$1', $string);
}
/**
* Determine if the given character is the lead byte of a multibyte
* character in the given codepage, passed as LFS language identifier.
*/
function isMultiByte($char, $cp)
{
$char = (int)$char;
switch($cp)
{
case 'J':
return ($char > 0xE0 || $char > 0x80 && $char <= 0xA0);
case 'K':
case 'H':
case 'S':
return ($char > 0x80);
default:
return false;
}
}
?>
optimise also does what it's supposed to do, but does not detect redundancy over the full string width, it's limited to a sequence chain. This is because I wouldn't know how to achieve it with regex assertions and didn't want to iterate over the string, because the actual splitter is going to do that anyway. Put simply, it will correct: ^L^B^H^HSomething to ^HSomething, but ^L^B^H^HSome^Hthing will still have that redundant ^H between 'Some' and 'thing', i.e. ^HSome^Hthing
isMultiByte is completely untested, but it should work under the unconfirmed assumption that all multibyte codepages LFS uses do not have characters wider than 2 bytes. If your split point tests positive with isMultiByte, split one earlier and you should be fine.
As I said initially though, all of those are prototypes and haven't undergone any actual testing with PRISM / LFSWorldSDK, or raw captured strings from LFS for that matter.
I have the sneaking suspicion that Lancia1.6 is Ivan-R32 in disguise
There is no host by that name, are you by any chance trying to host a server for cracked S2?
You never know, sometimes they're actually that stupid.
You never know, sometimes they're actually that stupid.
You re-uploaded it, presumably without permission, even though it's publicly available on YouTube and for download.
On topic: One of the best LFS videos, despite its age, is still this promo by yuzhou / mc.og.
On topic: One of the best LFS videos, despite its age, is still this promo by yuzhou / mc.og.
Besides, video is far from accurate, it's a rough approximation. Video cameras do not record a series of events, but a continuous stream of visual information at a set frequency. Events can happen between frames and even mid-frame.
To get to the point though, in this case it recorded mostly pitch black. I don't know about you, but to me, pitch black looks the same in real life and on video
To get to the point though, in this case it recorded mostly pitch black. I don't know about you, but to me, pitch black looks the same in real life and on video
I didn't mean in comparison to the BMW, I meant in comparison to many much smaller cars with 2ltr petrols. I also know how reliable old Mercs can be, but at 260k it'd have to be a diesel to make me consider it against a 150k bimmer.
In a rally car, you sit pretty much upright and tightly strapped back/in. I haven't used RBR in a while, but from what I remember the camera position was spot-on.
It's a big Merc with a relatively small petrol engine, done 260k and it's an automatic, how much clearer does it have to be? Take the bimmer.
A specialised LFS String class is the proper way to do it. The magic method __toString can be used to make the class (or rather, instances of it) behave very elegantly within a normal string context.
Dealing with coloured and/or non-default charset strings is tricky though.
Basically what you need to do is strip unnecessary escape sequences (^L, ^8 or ^9 at the very beginning of the string).
If the string still exceeds the maximum length, scan MAXLEN-4 for escape sequences.
If there is a pair (charset AND colour), split at the first (from left to right) sequence and repeat.
Else, scan through the entire chunk (from 0 to MAXLEN) for a charset and/or colour sequence (which you store) and make sure the last char is not part of a multibyte character or special character escape sequence (^v, ^a, ^s ...).
If it is, split before the first byte of that character. Make sure to carry the charset/colour over to the next chunk.
Else, split normally and repeat, carrying over the last charset and colour.
Perhaps some gifted regular expression expert can find a way to achieve this with preg_split() which would certainly be the most efficient approach.
Dealing with coloured and/or non-default charset strings is tricky though.
Basically what you need to do is strip unnecessary escape sequences (^L, ^8 or ^9 at the very beginning of the string).
If the string still exceeds the maximum length, scan MAXLEN-4 for escape sequences.
If there is a pair (charset AND colour), split at the first (from left to right) sequence and repeat.
Else, scan through the entire chunk (from 0 to MAXLEN) for a charset and/or colour sequence (which you store) and make sure the last char is not part of a multibyte character or special character escape sequence (^v, ^a, ^s ...).
If it is, split before the first byte of that character. Make sure to carry the charset/colour over to the next chunk.
Else, split normally and repeat, carrying over the last charset and colour.
Perhaps some gifted regular expression expert can find a way to achieve this with preg_split() which would certainly be the most efficient approach.
Two things:
- I'm quite bonkers and waste a lot of time on a lot of things (such as writing this), but not on researching or even estimating how "realistic and serious" remarks about my Minecraft creations sound. Partly because that'd be silly, seeing as an objective conclusion cannot be reached, and partly because I really don't care.
- If you had followed the thread, which I'm obviously presuming you did not, you would have realised that it was merely a statement confirming that lighting does indeed destroy flammable structures, as implied by hp, and not me whining about the loss of my forest, which by my interpretation of your post is what you thought it was.
The very first thunderstorm on the server burned down my huge artificial forest. I was on the server, perhaps 60 blocks from where it struck, but underground, so I missed it -.-
@Boosted: please do pull the map, just in case. We'd probably start from scratch anyway, but you never know, better safe than sorry.
@Boosted: please do pull the map, just in case. We'd probably start from scratch anyway, but you never know, better safe than sorry.
FGED GREDG RDFGDR GSFDG