FoolTrottel

Thanks Arthur!

yeah, those were them words I was looking for! Thanks!

This is an old one, but I had never watched it before... MH434 and Ferocious Franky at Duxford in 2009... http://www.youtube.com/watch?feature=player_embedded&v=HOm4nOTHMlc

Well, did some testing yesterday, with Sweper and Tolwyn. Whatever version used (HSFX Expert/Non-Expert, 4.12.2m stock) every other bomb drop results in weirdness... Even with Bomb Fuze diff setting off (4.09m timing) Also tried the Instant fuse... At moment of dropping, a viewer does not see the bombs drop, does not see any splash of the bombs hitting water, does not see the explosion, or, explosion occurs at a different moment. Even when I saw Sweper flying through Tolwyn's bombs-explosion-water-fountain, Sweper him self did not see/feel that explosion. (That was just after one explosion/splash of Tolwyn's bombs took me out ) It's all a bit weird. Could it be packet loss? The moment/fact the ordnance is dropped is missed by the client, and thus it does not see the bombs drop/hit/explode? Could be, but why can't I remember seeing it happen on earlier versions? (like 4.09m-ish?)

As of - not sure - some HSFX version based on - not sure - 4.1x.x, we've seen weird things when dropping bombs on targets. - Explosion timing differs for player and for viewer - Bombs do not visually drop, but disappear in view of a viewer - No Explosion at all - So, here's what I'd like to suggest: Let's try for a while on non-expert mode... Now, apart from looking/sounding more interesting than non-expert mode, I could not really tell what the differences are between them two. Me thinks we started using it because of an SEOW? Anyways, what do we think? Shall we give it a try? Anybody aware of anything that will be significantly different when running non-expert mode? (No, I did not want a poll, I want a discussion! )

Funny! Thank you!

Bristol Centaurus, Midland Air Museum

P12E!

Yeah, send it in, and then find out we still won't have you, you ... you ... you ... GIT!

W0t? Kelly? Is that you? Well well, the end must be neigh! Is it really now, is it? Can't believe it, kinda... You could just try and use Checkmods to update your install.... Your IP address hasn't changed, and I bet you haven't either! (Sure, you could also go the way of installing a stock 4.12.2m, then installing the HSFX 7 stuff, up to 7.02m.. Go for it!) Looking forward to hearing you on TS, and - yes, I always look at the bright side - looking forward to walk the beaches of Normandy with you, ie. piss off some Frenchies along the way! Edit: Yeah, just follow Crash's advice, better than mine, as in more complete...

(Sorry, can't get on TS right now.... maybe in an hour ...)

Run JSGME, disable all mods, enable stock 4.12m Try start the game. Quit game Run JSGME, enable history and expert. Fire up game again...

Announcement: we are changing to 7.0.2 officially Swep, check the contents of the file HSFX_Client_Updater.ini , the one that is in the folder where your game is installed in... It should mention the same folder name as is being used in the shortcut you start the game with...

yeah, check contents of HSFX_Client_Updater.ini file....

Got it.

Me neither. Then again, I've never used it...

Nothing too much out of the ordinary here. Differences with my conf.ini OpenGL: TexMipFilter=2 TexFlags.UseDither=0 TexFlags.TexAnisotropicExt=0 You must realize this was a very special occasion: 1. Host was running 7.02, where most of the clients were running 7.01 2. From the very start of the mission, the moment Fen pressed 'Fly', my eventlog.lst file got filled up with java.lang.nullpointerexceptions, at com.maddox.il2.objects.trains.LocomotiveVerm.place(LocomotiveVerm.java:147), over 25 of these messages per second were generated.Resulting in a log file of over 500Mb's. 3. Crash's game also hung itself, albeit at the end of the mission. (And, I think it happened to some else too...) 4. I could not really use track recording, switching it on resulted in a massive pause - about 4 to 5 seconds. 5. ... I would not be too worried about this one occurence.... I have checked the mission file running 7.01 and 7.02, the error that occured on Tuedsday did not occur during my test. Sure, it was a limited test, me hosting, with no clients. But it shows that there are no basic compatibility issues with the mission file. Me thinks the large map, long mission + the 7.01/2 combo did it, and maybe even one of the clients was still 'in between' them versions... (Starting the autoupdater, it ending prematurely due to a connection issue or whatever error...)

Too bad Pooka, we did have a great time... apart from the one's who's computers were crushed under the heavy mission load, and / or some weird issues regarding some people were on 7.02 already, others weren't and some even had 7.015-ish versions... In the end... typical Dogz night... Half show up prepared and ready, the mission is fine, though it does not load fine, we need a restart, half of the ones who thought they were prepared now find they are not, the others find they are, and somehow the mission happens, gets done with, lots of things happening that no one ever thought could (Friar navigating succesfully to a Rendez vouz Waypoint!), and vice versa, (Sweper getting swept by the Luftwaffe without killin' half of them first..) I could go on and on...

MMAPRPI's: A blue dot marks where a bomb may have hit.. (Mid Mission Action Packed Recon Photoedited Images) (Recording track did not work out, once I pressed 'R' I got a massive pause of multiple seconds, then had to try and gain control/hading/whatnots back... Oh well)

Very good show.... Very cool mission. Thanks Fenrir !! Scores: (Can you send me the mission Fen, so I can do some testing and research on it? Compare it with the logfiles? My Log.lst file is over 500Mb's... )

(I may have to bail out at any moment, depending on a phone call, but, I'll be there!)

You have something wrong.

No, that's not what he said. Tolwyn said we should not need using it at all. AA was designed to get rid of 'steps' at low resolutions (ie like 640x480) At the high resolutions we are running nowadays, there's no longer speak of 'steps', but mear 'jaggies'. Hence, acccording to theory, we can do without AA... What it boils down to in my opinion, is that we are all so 'spoiled' in not wanting to see any jaggies at all. (Me thinks there's people that'd even use a magnifying glass to make sure there are none left after the latest new HW upgrade, driver and settings tunings...) Just think about the huge task AA has to perform, for each and every pixel drawn, it has to analyse whether it is part of a straight line, and if so, it has to change contrast and whatnots of pixels around it, to try and solve the jaggie issue. To smoothe it out, AAx4 does it probably with double the amount of work ('depth'?), even more for the x8 etc. Now, remember, we are running high resolutions... so, for each and every pixel...yeah. Sh1tloads of work... performance will go down .... alot...