Hey Jakg,

when you are in Friedrichshafen (Home of the Zeppelin, MTU and ZF) you will be about 20km south of my Home. Weather is driving mad here right now... Sun, Rain, Rain, Rain, Rain, Sun, Rain and so on. So don´t expect to have good weather at the Lake of Constance (or Bodensee as it´s called here in Germany). And don´t expect to understand the Germans... even if you CAN speak German. Because you are entering the Spätzleland... we all speek Swabian here

World of Padman is a great FPS... it´s based on the Q3 Engine (I think) and has awesome Graphics and some really cool Ideas. Feels great and is tons of fun... if you have time playing LOL

Hi Ian!

Thanks for the Update... downloading now. Time to start up LFS again

@kosyag and errupt: You have PM

@woolfen: Does it work on your PDA? If yes, do you have the Specs (OS Version, Language used) for me? Maybe it helps me finding the Bug which causes the Problems the others have reported. If you want to link to the App you should link to this URL: http://www.buedi.com/category/Live-for-Speed/. Because the URL to the Program itself may change very often (as there are Bugs to be eliminated and new Features to be added) your Link would be dead with the next Version if you link directly to the File.

@YAONNIS: Thanks for the Feedback

@Errupt: Some others reported the same problem you have. And it drives me crazy because I tested the App on 5 different PDAs with different OS Version and Language and even on those damn slow Simulators and everytime it worked. Whatever I do, until now I could never reproduce this if I wanted it. I had this Problem 1 or 2 times, but could not reproduce it. After restarting LFS and the App it worked again.

Since I can not reproduce it it is nearly impossible to debug. Luckily there are other Users with PDAs PocketLFS works on. But currently I have no clue what makes it running / not running on some PDAs.
The Fact that you get the VER and Tiny Message in the Log shows that you receive Data. So I assume you have no "false" Settings in the cfg.txt in the LFS Folder. This gives me a clue where the Problem may occure. I will see if I can build in some more Debugging Information which will show me finally what´s going on.

http://www.warbears.com/
Days of Fun. It´s really great.

Thanks for your Feedback YAONNIS
The Freezer / Crash with some of the Turbo Cars was a known bug I fixed today. It shouldn´t crash again when driving the Turbo Cars and building up Maximum Boost now.
I also added a very simple Shift Light (will make it nicer looking and configurable in one of the next Versions).

The Messages you have seen where showed after PocketLFS crashed and you started it again, right? As PocketLFS should not crash (it does now, I know) it shouldn´t be a Problem when the App is stable... sometime... maybe in this Century

I updated my 1st Post and hope it does not crash again

@Michel 4AGE:
The Date seems to be correct. Somewhere I must have this Videotape of my Camcorder where I recorded them. I remember that the Gye with the Bed drove into the Pitwall.

I even found the Webpage again. Just in case someone wants to buy such a thing:
http://www.cummfybanana.com/

I don´t know from when that Sofa Picture is (and I am too lazy to search for Exif Information). But the Sofa and many other things (a crate, Toilet, Waste Container, Bed etc...) where all at the Truck Grand Prix on the Nurburgring (Grand Prix Course) a few Years back. They where called the Cumfy Bananas or something like that and they had a nice Webpage back then.
And this Sofa was scary quick!!!

Hi Jakg,

seems like you have the same CPU as mine. Since I use the Auto Setting too (I think it´s switching to Turbo itself when it´s needed) that shouldn´t be a Problem.
I updated PocketLFS and implemented a very very simple Log Function. If all goes well it should show you in the Log when a Version or some other Packet is received by LFS. This should show us if Packets arrive (or at least if my App recognized that it received Packets). Maybe that helps me a bit to localize the Problem which occures on your PDA.
I will update the 1st Post in a few Minutes.

Aaaah, the P-34. What an incredible Car. I saw one live racing at the Oldtimer Grand Prix at the Nurburgring a few Years Back. It looks really stunning and the DFV Sound is really nice.

A very good Site for the P-34 Interested is here:
http://www.project34.co.uk/

Quote from Jakg :

Did that, hit start and get a "InSim - UDP : already received ISI" twice and then a "OutGauge : enabled", then i get the same error message on the PDA as it crashes

Today I got the InSim - UDP... Message too. But I didn´t know why because I used the App a few times before. When I did a Reset on the PDA and restarted LFS it worked again. Strange... at least I got it one time. Now I only have to find out how to reproduce it every time to find out what it causes. But my PDA never crashed... this is really strange at it drives me crazy. I am so sorry that you have so much Problems :-(

Can you tell me how fast your PDA is (MHz?). As I write this Post I have a small Idea what it could be. When you press start I fire up a few Threads. Each of them has it´s own Tasks to do. Maybe they do not start in the Order they should. You send the ISI Packet, LFS sends the Version Packet back but my App is not ready... although it should start the needed Threads before sending the ISI... but maybe that´s the Problem. I will look into this.

Quote from kosyag :

New release has the same problem as I reported before: connection established, but there is no info on PDA screen. Ping between PC and PDA is stable and not so large (~40). Firewall disabled.

That your Ping is working is nice, it shows that there goes Data in both ways at least. Maybe your problem is similar to the Problem Jakg has. If it is I can solve 2 Problems at once... IF I solve this

Quote from kosyag :

What about I think I will implement a Function which shows this Version Information so we know if PocketLFS get´s Packets from the LFS Box. ? It will really help me.

This should really be the next thing I have to do... after I fix the next Bug you mentioned...

Quote from kosyag :

P.S. New release very unstable: recconnection attempt (Start -> Stop -> Start) causes crash, but process is not unloaded from the memory, and LFS got multiple UDP connections from it.

This Bug existed before. The last few times I had a few "Minutes" to work on PocketLFS I was really trying to fix that Bug. Until now it still exists, but I have a few Ideas. When there is time I will try it out and I hope I get it fixed soon. This one follows me since the first Build of PocketLFS.

Quote from dreas911 :

what about this one!? in black ;D

This is a Audi 100 (Type 44)

Quote from Jakg :

Axim x51v, WM5 - i run the latest version and i press start, i get a crash box saying:

This drive me crazy. I tested on 5 Devices now and it worked. But whoever from the Forum here runs it does not get it running. At least we have a Error Message now
I searched in the MSDN and maybe I found something which could help debugging this (since I don´t get an Error on my Test Devices I currently can only speculate what it is). I will test it tomorrow and see if I get something.

Maybe it´s working for me because I do something "right" everytime. If I remember correctly these are the steps I do to start the whole thing:

1. Start LFS and stay in Main Menu (sometimes I start Hotlapping, it doesn´t matter)
2. Startup the PocketPC and Connect to WLAN
3. When WLAN is connected, start PocketLFS
4. Check the Network Settings in PocketLFS
5. Press Start in PocketLFS
6. Get a smile because it works
   

There IS a issue right now when you use PocketLFS, press stop and start again it can get slower because I have a Problem in the Code. But when you 1st start it it should run fine... but it isn´t in your case
I WANT to figure that out

@Anik360: No, it contains only the .exe and a nice Readme.txt :-)

Quote from anik360 :

Umm can this work on my T-mobile DASH with Wm6 smartphone edition in it?

I doubt it. WM6 generally shouldn´t be the Problem, but the T-Mobile Dash has a Square Display. And the Application is designed for Non-Square Displays. You can try if it runs, but it may look strange because of the Screen Resolution

The Original Need for Speed was the best IMHO. And it had many Simulation Aspects back there and the Graphics and Sound where unbelievable good. I will never forget the Viper Sound they did when you fully accellerated and then went off the Accellerator. It sounded really great. And the Multiplayer Mode over Modem was absolutely Stunning. I can´t count the hours I spent with a Friend "Online".

The Cars in NFS 1 behaved at least similar to the Real ones. The Testarossa with it´s Mid Engine was a real beast when the Back stepped out. When you drove the Porsche you could get that lift of Oversteer in Corners. And Accellerating / Braking was very good too. You could not stop in 5 Metres from 250 to 0 like in the later Games.

I loved that Game and I still have my Original NFS SE Version here in a box... maybe I should try if it runs under XP

:bump:
Updated 1st Post

Maybe it´s me or maybe it´s LFS.

Scenario:

1. I send an ISI Packet to LFS and set a UDP Port as Reply Port (i.e. 9063) and an Application Name (i.e. PocketLFS).
   
2. LFS Displays that Insim was initialized for PocketLFS with UDP Port 9063.
   
3. After that I send a IS_Small to start Outgauge.
   
4. LFS says that Outgauge is Enabled and my App receives Outgauge Data.
   
5. I send a IS_Tiny to close Insim.
   
6. In my App I change the UDP Port to i.e. 6070.
   
7. I send a ISI Packet to LFS (this Time with UDP Port 6070) and my Application Name (PocketLFS).
   
8. LFS Displays that Insim was initialized for PocketLFS with UDP Port 6070.
   
9. After that I send a IS_Small to start Outgauge.
   
10. I get not Packages. When I look with Wireshark I can see that LFS still sends to 9063.
    

So, maybe I am doing something completely wrong or there is a Bug
This "Bug" seems to only occur if LFS is forced to send Outgauge Packets. If I play through this Scenario while in the Main Menu and after Step 7 go into a Replay I receive the Outgauge Packets. But when I am watching a Replay and doing the above thing I only get Packages in the 1st try and not after I changed the UDP Port and reinitialized Insim.


Edit: It was my Bug. I did not close Outgauge before closing Insim. So LFS seems to "remember" the Outgauge Settings even if Outgauge is opened again. So it isn´t a Bug, but maybe a Feature as with the cfg.txt (if you set Outgauge there the Insim Parameters are ignored). If this is how it should be I will shut up now :-)

Last edited by buedi, Mon 18 Jun 2007, 19:41.

OK, first here is a link to the Newest Version of the .NET Compact Framework (SP2). .NET CF 2.0 SP2 Download
Thank you very much @kosyag for testing and solving the PocketLFS Startup Problem with installing the newest .NET CF Version

@kosyag: The Messages LFS shows to you indicate the the Communication from your PDA to LFS works fine. This is very nice. When I connect over Wifi I can ping my PDA from my LFS Box. Is this possible with your BT Connection too? Is it possible that your Windows Firewall blocks the outgoing UDP Traffic to your PDA? When the PocketLFS Program connects to LFS via Insim it gets a Version Information back to LFS. I think I will implement a Function which shows this Version Information so we know if PocketLFS get´s Packets from the LFS Box. Maybe I can do this today, but I can´t promise. Thanks for testing so far

@R1K89: I don´t have one of those Devices. But I think I read something about them... maybe the Forum Search helps. Implementing Analogue Gauges is one of my future Plans. But since noone could get PocketLFS running now (except me LOL) I think I have much problems to solve for now

Hi all :-)

Yes, I was away for a few days. But those of you who sent me a PM with an E-Mail Adress got the Program a few Minutes ago. Since you all use WM 2003 I will try to get the WM 2003 Emulator from Microsoft to test the App there too. Kev reported a Problem while starting the App. The Config File can´t be created and currently I am not sure why. But I will investigate that.

When I have news I will send you the new Version. But as my time is very limited, please be patient with me
And thanks to all who are testing and providing me with Informations

Quote from f1r3b4ll :

I'm a little unsure how I would get the PC to talk to the PDA without active sync...

Just plugging the USB Cable into the PC won´t work, because you do not have a "Network" then. Activesync does that job but sadly it doesn´t support UDP.
The only way I tested it is over WLAN. If your PDA does not have WLAN maybe you could try it with a Bluetooth Connection. But as I don´t have Bluetooth in my PC I can´t test it. AFAIK you can make a Network Connection with Bluetooth, but I am not 100% sure. Maybe somebody with Bluetooth in his PC can test this?

Maybe I will implement TCP at a later time. But now I have to speed up the Application first. I am sure there is much room for Improvement in the Packet Handling which should run the Application much faster... but who knows. Maybe I am wrong

It seems like you are doing the same Mistake I did until riskredruM showed me how it works
I reinitialized my UDP Socket everytime I sent a Packet. If you do this every UDP Packet you send is sent from another Source Port. Because of this LFS does not know that the UDP Packet came from the same Program which opened the Insim System.

Use a Tool like Wireshark and if I am right you will see a increase of 1 in the Sourceport of each UDP Packet you send.

Edit: What I wrote is what hackerx wrote before... just a bit longer LOL

Nice! You got it working finally. Congratulations and happy coding

Are you 100% sure you disabled Outgauge in the Config File? This was my fault when I tested with Insim V4... I enabled it in the Config File.
Maybe you can install Wireshark on your LFS Machine and watch if LFS even sends Outgauge Packets (you then will see too to which IP / Port they are sent).
For me it´s working perfectly in Patch X with my PocketLFS App. And I enable Outgauge via Insim too (and leave the Config File untouched now).

A little Update. See 1st Post.