Jump to content


Founders [premium]
  • Content Count

  • Joined

  • Last visited

Community Reputation

194 Excellent

About kendo

  • Rank

Profile Information

  • Gender

Recent Profile Visitors

396 profile views
  1. kendo

    DD today?

    The sale ended on Monday 29th.
  2. kendo

    American Iron

    Yes, too much pedantry.........but I think what you really mean to say is aluminum
  3. kendo

    Developer Diary 209 - Discussion

    Yeah, I did see that. Looks great too. Regarding the the censored swastika kill markings, i expect we will get them 'fixed' in a mod - maybe the existing authentic national markings mod for German aircraft. iirc they already included a 'fixed' skin for the A20B in that pack yes, just checked - the 'Dashing Hitler' skin actually has a restored swastika on the Hitler motif beneath the cockpit.
  4. kendo

    Developer Diary 209 - Discussion

    What I was thinking too. The metal finish on all the skins is really good - very realistic looking. They seem to have perfected it now. Definitely seems to have taken another step up. And as for the pilots...WOW!! Looking forward to seeing RAF pilot soon (and hopefully Luftwaffe + Russian pilot updated to same standard) I can't resist anymore. BOBP pre-order (and new gold bar) coming very shortly.... Nice......
  5. kendo

    Developer Diary 207 - Discussion

    Can only echo what everyone else has said - that does look extra special.
  6. kendo

    Would You Purchase?

    To the OP - a resounding 'No' from me as well
  7. kendo

    BOBP Premium and FC Drawing 1200 US Central

    Many thanks for the generous gesture Requiem. Put me down for Bodenplatte please.
  8. Looks close enough to me. And no farther away in realism than BOX clouds are from real clouds.
  9. I use the throttle for advance + reverse, and the rudder pedals for left/right turn. Works well. I have also mapped the main weapon fire controls to the joystick which again works ok. Have tried to find a way to have joystick axis controlling turret/gun elevation, but so far I can't see a way to do it. So, partially there.
  10. Thanks. Quite a relief.... 😂
  11. Yippee!!! Found the solution. Unexpected and surprising but posting it here just in case anyone else faces similar issue. It was caused by a new setting in Windows Defender Security Centre. It is Windows Defender Security Centre > Device Security > Core Isolation > Memory Integrity checkbox. It was unchecked by default when Win 10 1803 first installed. That's when I tried out BOX and all the CH controllers were working. Later, I was investigating the various new options and checked the tick-box for the Memory Integrity option. Didn't notice until I tried today that it had the effect of 'breaking' my CH controllers. Upon unchecking the option and rebooting everything is back to normal. Had to re-calibrate controls in CH Manager, but everything is now working fine. Probably my PC is a little less secure, but I have good AV so will have to live with that.
  12. Unfortunately I can't go back to previous version of Win 10 - when I saw yesterday that everything seemed to be working ok, i deleted the previous version files as they were taking up ~30GB of space. All seemed ok at that point.... And unfortunately the other option in the link doesn't work either. Does anyone know: If i uninstall Control Manager and Combatstick and Throttle, then plug CombatStick and Throttle back in to USB port, will Windows run them using some kind of default Windows driver? I know I will have to remap everything in BOX, and i will lose calibration capability in Control Manager. But will that at least get me functioning inputs again?
  13. Thanks for the link, but I have already seen that thread. None of the simple tweaks listed there worked, and for now at least i don't want to try joytokey or similar - prefer to try solving the root issue here if I can - which basically is that Windows is saying the drivers have problems. In Device Manager: Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39) {Bad Image} %hs is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0x Have tried to update driver using the option in Device Manager but doesn't work. What I don't understand is how/why it worked yesterday, then today is listed as errors???!!