@Dustin: I'm not a leecher but neither am I a programmer as such. I did NOT copy and paste this but I changed it to suit my InSim application. And if this is just because of my previous repuatation this really does make you look idiotic. Even Jakg has changed his opinion slightly of me.
@Mikjen: For the last time I NEVER had a go at you, I just told elmohellno his thread wouldn't help you fully, since you don't actually program.
Dustin, Shaun really has done a lot for a 9 year old, ya have to give him that He may not fully understand everything relating to programming, but he's a lot better than some other 9 year old who was here who shalt remain nameless
I understand, sometimes I just get grumpy, because of that "other thread" about "certain boring servers", and people constantly going "OMG! CAN I HAVE INSIMS" that I guess I expect more of people sometimes.
Sorry Shaun, I guess my 13 hours of Metal Gear Solid 2 + 3 have gotten to me.
I've come across a problem with this...When assigning the MCI packet's values to the player list values, there comes a time when MCI.Info[i].PLID is 0. But the players list then says it doesn't have a player with PLID 0, and then dies. But I don't understand how that can be...The PLID values n the MCI packet have to match up with the ones in the players list. If that's the case, then why does the MCI packet have a PLID that the players list doesn't have?
Help would be smashin on this, I can't get my head around it...Also, when I do a check to make sure that the MCI PLID is above 0 (debugger says mine was 1 at the time, and I was the only player), then it doesn't die. but it doesn't assign anything to the player's list, as MCI doesn't have a PLID 1. And that makes it even more confusing
The problem is that the players list doesn't match up with the PLIDs in the MCI packet. There is only PLID 0 in MCI, yet only PLID 1 in the players list
Ah, that'd be if PLID != 0 Haven't ever looked at VB
I've tried checking if it's greater than 0, but then it doesn't set anything, as MCI only has PLID 0. Everything else in the packet matches up, as in the speed and locations shown for PLID 0 match up with my own, but my PLID in the players list is 1
How i can add this thing to my server? It gives me there 12 same errors:
Error 12 Cannot modify the return value of 'LFS_External_Client.clsPlayer.CompCar' because it is not a variable D:\lfs\lfs_external_csf11\Form1.cs 1947 21 lfs_external_csf11
hi guys i have got the open source cruise insim and modified it and added the MCI code to allow more people on the server:
Originally posted by 'mcgas001'
for(int i = 0; i < MCI.NumC; i++) { Players[GetPlyIdx(MCI.Info[i].PLID)].position = ++MCI.Info[i].Position; }
when i start the insim and someone leaves the pits/ already on track i get a error saying:
if i click ok the insim will start but theres features not functioning properly like the money payout i dont know what to do i also added the following code to the clsPlayer.cs file:
MCI and NLP packets are snapshots of the state of play on the track that the LFS server takes at a constant rate (set in the ISI packet under Interval [50 - 65536 ms]). The LFS server sends these snapshots to the InSim clients. Network packets take a certain amount of time to travel between the InSim client and the LFS server (i.e. the ping time). This means that the InSim client time is always a little bit behind the LFS server state. Furthermore, InSim client input packets are also delayed on their way back, so the server is processing temporally delayed InSim commands. In addition, each InSim client has a different network delay which varies over time due to other background traffic and the InSim client's connection speed. These time differences between LFS server and InSim client can cause missed information, becoming worse with increasing network latencies. It is up to you, if your application requires it, to tween between these snapshots to get a better picture of where the car has been. In racing games, even a delay of a few milliseconds can cause reduced feedback and make it hard pin point cars at any given time. Besides bandwidth limitations and network latencies, information can get lost due to network packet loss. Keep all of this information in mind when your setting your Interval for your MCI or NLP packets.
[I'm starting to write documentation for PRISM, so I thought you could also use this information here.]