Jump to content

FoolTrottel

1. DDz Quorum
  • Posts

    7,113
  • Joined

  • Last visited

  • Days Won

    332
  • Country

    Netherlands

Everything posted by FoolTrottel

  1. Short report of what has been goin'on today, pics ánd details: Three Spitfires in formation: IL2 Pilot and his rear gunner: Junkers 52: Ánd it took to the air, it's on Video. (Please have patient, within 12 months from now, the Dogz-At-Duxford DVD-set will be released)
  2. there's also this: KeepVid. Copy paste the youtube link into that, chances are you can save it to .mpg, mp4, mov ... whatever!
  3. Good Job! And thanks a bunch for that PPL disable thingy tip, I just realised my system did the same thing! Switched PPL to disabled, and yes, it boots normal now!
  4. Ooowwww ... just has I had the impression I won this one, comes Jedi raining on my parade! Oh well...
  5. Sure, but that wasn't World War... there's always a war going on somewhere...
  6. Never EVER believe the French commentator Well, I'd like to suggest to take it a step further: Never ever LISTEN to the French commentator.... (I wish I could be partially deaf, to the French only, when they're in the UK, speaking frenglish...)
  7. Oops.... my bad... (but ... in my defense... that French commentator talks about the Fury! Silly guy I guess...)
  8. Me thinks WW2 started september 1st, 1939. If you think it started earlier, then I'd suggest to include 1914-1918, the period in between being just a cease-fire...
  9. We've seen the Three Kestrels last year! (Three Kestrel powered aircraft: Hawker Fury Nimrod II, Hawker Hind, Hawker Demon. Video of their display at Duxford Flying Legends, July 10th 2010.) Edited: It's not a Fury in there, it's a Nimrod II!. Thanks BlueBear!
  10. Silly stuff this, I just discovered that another bug that was in 4.10m and was fixed in 4.10.1m is present in UP3 RC3 (maybe in RC1 and RC2 as well) It's the one when in a coop a static ship is being hit and sinking, after it sank completely, it simply re-spawns. Found this while looking at the Pearl Harbor alternative mission, the Japanese do sink them battleships, and the USA do sink a carrier, but if you let it run long enough, battle ship row looks like nothing ever happened there, and the Blue Carrier is happily sailing along again... As for that PH alternative mission that failed to work in 4.10.1m, I found out it had an invalid height for the second waypoint of the F4F3's (0m). Fixed that, so we can still use it some other time ) (BTW, that PHA mission with the waypoint error in it does run fine on UP3 RC3, no issue there... This stuff is now very close to make me go crazy)
  11. It's not that we'll be ignoring UP3... but for now we'll have to switch back to 4.10.1m for the regular coops. There's too many issues popping up, taking out the fun, frustrating all of us 'cos a member can't join, missions can't be loaded, the gunner issue, weird things happening, as an invisible Artie, but only for Pooka... (or was it vice versa?) scoring is messed up... It's too much at the moment!
  12. Have tried several missions of the Desert44 campaign, no problem here...
  13. Could have several causes... what mission is it?
  14. Looks good Friar, mind if use them today?
  15. I'll be 'round, and see if there's any others 'round to host for... and then maybe host some... Brando, both bits ánd pieces... wow... sweep 'm together, drop the lot in a box, connect it... My controller's inside look like I did just that, and it works... (I've tried some soldering yesterday, for my bodnar board, failed miserably, old stuff I wanted to use appeared to be rather 'incompatible', so I will have to buy me some new switches... oh crab, should've done that today, too late now, stores have closed by now... silly me... oh well)
  16. fit the circumstances? You mean it was dark outside? Or the laptop is black too?
  17. That is a very nice laptop... especially the 7200RPM disk and the 1920 x 1200 screen resolution.
  18. Have been looking into the (Rear) gunner issue, and it's definitely very much broken. RC3 appears to not have had this fixed. Could not get a client to become a rear gunner. Whenever the client presses 'fly' he ends up in the list as being a pilot in some randome aircraft, while not showing 'Ready' status in the ready screen. Next, I tried to swap the roles: Host rear gunner, client the pilot. Very special effect. Outside view on the client/pilot pc did not show the host/gunner firing when he really was. Even, the gunner was shooting at the wingman's aircraft. But, no dice. No visible damage to the wingman (viewed from the client/pilot computer.) If the host is a gunner in an AI flown aircraft, it all works fine as it should, damage cán and will be done. Should report this as a bug, but: looking in the bug report thread for RC3, Hades states regarding the Coop mission scoring issues (ie. Host not in list of scores) "The co-op log problem is know. The eta for fixing this is un-known. Best is to use a DF server. Moreover we will support DF Server environment even more an move away from the old co-op one as we will announce a big Open-Source project for the DF Server, the UP Advanced DF Server that will change multi-player once and for all and utilize the full Df Server potencial combining Advanced Features like MDs, resource-management, AI trigger, Dynamic weather, etc... So, that's pretty bad news, if this stays that way can throw out over 2000 coop missions as they can no longer be used with UltraPack. Jippie, hosting DF's, rinse & repeat all night long! 4.11m FTW!
  19. So that's the reason I saw a big Canadian flag hanging from a house in my hometown! I get it now... Thanks Canada, Happy Happy !
  20. Thanks for the info, any idea how I can get this to work on my Nokia 6310i? Oh wait, I ám going to Legends.... never mind...
  21. Flaky? Hm. I can relate to that. Somehow. I've recently built a new system quite like yours: Asus P8P67 LE, 8 GB, GTX 580. I haven't touched that TPU switch. But, my system would boot very very slowly, the Bios part of it. Started happening after I had connected my USB devices. And, once in Bios, the cursor/pointer/menu selector went scrolling continuously, as if the down error was pressed constantly, or the mouse was moved downwards. Turned out it was one of my game controller devices, one that used to be a game pad, but of that I now only use its electronics for some 12 buttons. No switches/pots are connected to the X/Y/Z axis of the controller. And that is something this Bios cannot handle. It recognizes it as some kind of USB controller and accepts its constant inputs... Old bios never did that, but that one was much older, and did not have mouse control. I've solved it by only connecting that specific controller whenever I do need it. And have it disconnected at boot. Am already working on a Bodnar-board to replace that weird gamepad thing... They still manage to make stuff more 'intelligent' and thus more complex. More of a challenge for us to troubleshoot issues...
×
×
  • Create New...