Small problem. If I start my InSim prog (which is ATM console program and doesn't create window itself) with /exec command in autoexec.lfs, LFS loses focus. Tried to use "/exec start /MIN prog.exe" to start it minimized, but then I get "Parameter is not valid".
Perhaps would make sense for /exec command to run programs in such way that LFS doesn't lose focus?
New InSim is so good that I just had to finally start coding. So far everything I have tried works as InSim.txt says, no bugs encountered. Had a little idea though.
How about making interval of LFS sending keepalive TINY_NONE customizable? Perhaps max (and default) 30 sec as it is now, min 1 sec, set with small packet if needed. Lazy me would like this a lot. This way InSim client could have timing without any extra effort, just with packet reading loop. I think it makes sense if "master" program provides timer for "slaves", no?
Edit: well, I guess it's silly suggestion, caused only by my lazyness... Have implemented nice timer myself now.
This not directly related to InSim, but driver can't see RCM while being shown yellow/blue flag? Blue flag can be on for long time, so basically there's no guarantee that message will be seen?
Well it's simple really... Why? Cause the law says so. If citizenship goes by jus sanguinis, then there are reasons for that. Citizenship is not one of human rights.
I'm quite sure it's not much different than here in Estonia, and you can ASK for citizenship and get it proving you can speak language, know something about laws and culture and are loyal to Latvia. Have you problem with any of that?
Anyway, your position as second generation immigrant is of course unfortunate, but you cannot blame latvians for that...
(All this assuming you don't have citizenship - as what other rights you can be demanding?)
Anything you may call "discrimination of russians" is direct consequence of this kind of attitude. Latvians are at home in this country. You are not. You can't just demand same rights as they have. Do you even speak latvian?
You wouldn't be posting to internet forums then...
But obviously you have no respect for country you live in! In your post you just repeat what Russian propaganda is telling you, i.e. (Soviet) Russia liberated Baltic states and also brought culture etc. All lies...
Unfortunately Scawen thinks that you're not supposed to actually drive in this view. I still hope he will change his mind on some nice day, and add mirror/look back.
I get rather odd results when trying to run following script, like "A new guest is connecting" messages appearing, and that in single player mode.
ai AI 1 ai AI 2 ai AI 3 ai AI 4 ai AI 5 ai AI 6 ai AI 7 ai AI 8 ai AI 9 ai AI 10 ai AI 11 ai AI 12 ai AI 13 ai AI 14 ai AI 15 ai AI 16 ai AI 17 ai AI 18 ai AI 19 ai AI 20
Also, if script has just 20 times "ai" (without names), only one AI driver is actually added.
Edit: Tried once more, now also crash with this, address 47ec4f (W10).
Hmmm... I still have drive through if I got 30 sec penalty in first place? Kinda doesn't add up.
Anyway, thought about it again looking at InSim, now we have time penalties carved into stone as 30/45 seconds everywhere (translations, InSim, etc.), but wouldn't do any harm to have penalties more flexible, and possibly configurable? Like have 2 types of penalty, time & pitlane. Time penalty could be any number of seconds (in reasonable limits of course, one byte enough), and pitlane penalty would also have time value (possibly same byte?) - the time to stop. If that's zero, then it's drive through, otherwise stop'n'go.
I'm not InSim programmer (at least not yet), but had a quick look. Some things I noticed...
struct IS_NLP // Node and Lap Packet { ..... word NumNodes; // total number of nodes in the path word FinishLine; // the node number of the finish line .... };
So I understand two words NumNodes and FinishLine are sent in each IS_NLP/IS_MCI, but those cannot change during race? Why not have a special packet for track info, including there also nodes for split lines, possibly some other info about track (total length comes to mind)?
// RaceLaps (rl) : (various meanings depending on range)
// 0 : practice // 1-99 : number of laps... laps = rl // 100-190 : 100 to 1000 laps... laps = (rl - 100) * 10 + 100 // 191-238 : 1 to 48 hours... hours = rl - 190
Dunno, is there really need to squeeze this into one byte and also limit possible race lengths? Just word for laps and/or minutes would seem more logical. This is same also in replays so is it also what LFS internally uses?
Hmmm no, it's one of ugliest cars I've ever seen. But agreed that it's not suitable for racing at all. I guess it's very likely that its real life version drives as bad, as it's designed & built by some amateurs in backyard or something.