Find the Node number (!node) at the point you want the message to appear, then use that number in a RegisterNodeAction script, with sub-routine to open private message.
There's an example to display speed in the original lfslapper.lpr file. You just want to change the speed to a message. Alternately, look HERE for example on this forum.
Have been playing around with Win 10 in VirtualBox for about a week now, and don't like it, especially the metro buttons in the Start menu, and the privacy issues.
At the same time, I've also been playing around with Linux Mint in VirtualBox using downloaded iso. Problem with that is that it has been laggy, freezes constantly, and keyboard (and especially) mouse are both unresponsive.
To really test Linux, thought I'd install as dual-boot with my current Win7 Pro, but having problems.
I've burned the working Linux Mint iso onto DVD, and it loads fine on booting up pc. But when I try the 'Install Linux Mint' from the desktop, it freezes after only a couple of steps...
Eventually, after few minutes, all clears and small command window opens up with error message about 'failed to idle channel', some numbers and something about 'nouveau'. Then computer hangs, and I have to reboot.
However, if I reboot, Windows finds disk errors and goes thru disk checks, and has to fix a number of errors.
Tried this 4 times now, all repeating same issues. Don't want to try it again in case disk errors muck up my windows installation or data.
According to what I've read, I should just be able to boot, run and install fairly easy, with Linux sorting the installation, disk partitioning (was going to set 100Gb aside on my 2Tb disk), and dual-boot.
Assuming no problems with the iso or the burning of it to dvd, any ideas what's going wrong, or what I'm doing wrong?
Doesn't seem to make a difference, even when using add-on scripts. You would have thought that the CatchEvent's and CatchSub's would slow things down, but they don't appear to.
If you have something that updates all the time, you get the performance problem.
I made a little bit of code to let me see the overall distance for some of my layouts, which showed distance updating as I went round...
... and I left this code in when I loaded a new layout on one of my servers - it only needed about 5 or 6 people to be on the layout, and lapper 'lagged' by in excess of 10 seconds - such as trying to get !top command, open or close a button, etc.
Another time, I had my drift scoreboard working giving live update of drift angle and score on one of my servers (without the distance code), and same thing happened when a few people on track at same time.
Fortunately, no problems if I use something like your pitboard, which only updates at sector splits.
Does it matter? Nothing to stop you putting something like "opb", then search and replace this with "openPrivButton". Realise this isn't exactly what you want, but...?
Its quite good, but it needs tidied up a bit, and some of the corners are a bit tight and constrictive. As are some of the straights.
Because the course is so long, you need more arrow marker boards to show which way to go, and because some of the roads are quite long, and you can reach a high top speed, so will need longer braking zones, you need more distance markers.
There are road signs dotted round the course - nothing to stop you using the Z function and putting marker boards up in front (sometimes the back) of the existing signs or on lamp-posts. Or sit them on top of things (railings, bales, etc), so you can see them from longer distance.
You need to add checkpoints to get rid of the error message when you first load layout, I would suggest at least 2 (press 1 to place first, then < > arrows to change direction, and W or E to change width, then press 2 for second checkpoint, and 3 if you want 3rd).
I'd probably put some marshalls in various places - not because they're needed, but they're the closest you can get to spectators. And you can use the ones that point to give drivers an idea of which way to go.
The one place you have used lots of marshalls (after the bridge, shortly before the finish) - lots of people will get spec'd here for hitting the marshall circles - you should make the marshall circles bit smaller (use W and E keys). People hit marshalls a few times in same spot, and they don't think they're doing wrong, and they give up.
Where you have long line of same objects, I would have broken it up a bit. For instance, instead of say 100 barriers in a row, I might have went barrier - bale - barrier - bale ....
And to finish....your finish line; its facing the wrong direction - you need to turn it 180 degrees (use < or > key). Move the tyres on the left onto the fence - needlessly constrictive here. Give people a big flourish when they finish - put up some concrete posts and hang a coloured wall between them up the top to make it look like a banner.
The penultimate solution would be to do clean install of windows - see here for guide if you have Windows 7 - then re-install all drivers, including the Logitech wheel drivers.
Not uncommon problem - "This issue is caused by a conflict with some of the files in the 2008 version of the C run-time libraries. These libraries are part of the Visual Studio 2008 release, the version numbers start with 9.0. These libraries may be installed with several different Microsoft and third party products"
Look HERE for steps to follow (ignore that it refers to MS Access - happens to other programs too).
There's only a few places where I've found this to be true (and I've made a lot of layouts using the access roads [example1 / example 2], some of which I've used on my servers) and that's if you make ramps to get over the fences and use these 'out of bounds' roads, and also some of the grass areas, especially the areas marked on this image;
Maybe you could mark where you're having problems?