Hi Guys,
The new Client 6.2 is at the same link as the 6.1 was yesterday :-
http://flynet.en-studios.de/downloads/newest/flynet.exe
Manual update only, just overwrite your 6.1 client with this one, the libmysql.dll is still the same so no worries.
Rgds
John
Another new Client - 6.2b
Moderators: Guru's, The Ministry
- RAF_Quantum
- The Gurus
- Posts: 2745
- Joined: 04 Jul 2004, 23:36
- Location: NE Lincolnshire UK
- Contact:
Another new Client - 6.2b
Last edited by RAF_Quantum on 03 Dec 2006, 13:29, edited 1 time in total.
- DaveB
- The Ministry
- Posts: 30457
- Joined: 17 Jun 2004, 20:46
- Location: Pelsall, West Mids, UK
- Contact:
Yup.. no problem with the new exe though autoupdate failed again and my Viking remains at 99.7%/zero dollars. I've been tempted to give my long suffering pax a nice 'sideways.. wheels-up' landing but have resisted the temptation thus far
Any news on what is to happen to the affected aircraft??
ATB
DaveB :tab:
Any news on what is to happen to the affected aircraft??
ATB
DaveB :tab:
Old sailors never die.. they just smell that way!
- Chris Trott
- Vintage Pair
- Posts: 2590
- Joined: 26 Jun 2004, 05:16
- Location: Houston, Texas, USA
- Contact:
- RAF_Quantum
- The Gurus
- Posts: 2745
- Joined: 04 Jul 2004, 23:36
- Location: NE Lincolnshire UK
- Contact:
Chris,
I also made an assumption that other things had been changed as you are doing now but DaKurt says otherwise :
Rgds
John
I also made an assumption that other things had been changed as you are doing now but DaKurt says otherwise :
Quantum wrote:It also looks like some other changes have been made to the client that we have not been made aware of.
I've posted at FlyNET forums regarding the problems that we are still having regards the latest Client/s. I've also suggested that the next client 6.3b be a 'roll-back' copy of 6.0b until they can get their act together with updates.Da Kurt wrote:humm, I have to check this. Well, I (at least I hope so) didn't change anything else except the two things written in the news. But I had to make some changes with the uploading of the flight report to the database at the end of a flight in order to be able to write a comment. So maybe that's the reason for the bug. I'm currently at work, so I'll have a look tonight.
Rgds
John