Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Where is my MiG-29 already?
  3. What about the gun ammo panel doors on the nose that is shown in 4 out of the 6 product pics on the 'Details' section of the F-5E Remasterd? I can't find any bindings or find any way of opening those outer panels? Would be a very strange and slightly mis leading selling feature if you couldn't access them when the product pics rely so heavily toward them.
  4. Thanks for your time ! I'll check this later today.
  5. I was wondering if I can use my Bluetooth Bose earbuds for sound...just wondering if the mic will be ok with DCS-SRS/BMS-IVC; I'll have to test. I have an Arctis over-the-ear wireless set that works very well, but it has my TrackIR semi-permanently attached. It won't work with a VR headset.
  6. If you use MB's QV, not the latest one.
  7. DMAS, no loss, they're rather crap. I run my sound through desktop speakers but for when I was recording video I used wireless headphones. They fit very nicely under the OG and ditto with the Super (and perfectly comfortable too).
  8. Are there any active tournaments of 1v1 or 2v2? or any ww2 pure dogfighting events or ladders of any sort? would be great to participate in one thanks
  9. With such a planned route (especially at this map scale), even smaller fonts will blend together. You'd have to use a micro font, which you wouldn't be able to read without a magnifying glass. I've flown many missions on various maps and never had a problem reading the route.
  10. This is the error: "ERROR EDCORE (5132): Can't open file: /shaders/model/fake_omni_lights.fx." Seems you only installed half of the Mod, the VPC Mod has two components: one goes into /Saved Games/ while the other goes on the DCS program folder itself, like this: On my PC those missions do work, just tested one of them: I'm on other projects at the moment, so can't really provide more detailed help on the install of the VPC mod, sorry. Eduardo.
  11. yeah, maybe not lower than fixing L-39, but yes
  12. The sooner the better on this module. I would be happy with just the AI Zeros. Did a small mission with the bat bombs the other day and got jumped by 12 190's and it was epic. Would be even better if it was A6m's.
  13. I’m sure they do. I’m also sure that implementing them is of the lowest priority.
  14. Yep But I am pretty sure that ED knows about toe breaks regardless of our proofs
  15. Good find. Finally, visual proof of toe brakes rather than an assumption based on lack of brake lever on the stick.
  16. The latest from a PIMAX production status email:
  17. Any news on the Mirage F1M?
  18. Mail an den Support schicken. Die sind immer hilfsbereit!
  19. Thanks for the detailed explanation, @GTFreeFlyer This is awesome! Your explanation has filled in a lot of holes in the landing sequence that I'm experiencing. I'll be practicing this incessantly! Thanks again for taking the time!
  20. You might want to cross post in the Wishlist section!
  21. Today
  22. I think it's just a matter of font initialisation sequence. Or font I'd try to make my 777 cdu work now that the a10c -> Mcdu is working , but the lib by default seems to only work for the mcdu airbus. The default lib is searching for a PID ^ VID device that matches productName: WINWING MCDU-32-CAPTAIN vendorId: 0x4098 (16536) Unknown vendor productId: 0xBB36 (47926) The B777 PID is 0xBB37 , so i just changed the PID in the lib code and tried, but nothing was displayed. I also uploaded the font i customised for the A10C ( my 2nd hyptothesis was that the mcdu code refer to a default font name - and they're not the same on mcdu / 777 in the simap pro app. In the process , there's a phase to initialise the device, and as they are physically different i think the mcdu sequence do not work for my b777 . Nothing is displayed So this is the thing to "sort out / sniff " to get something displayed on it ( mcdu lib by default wont work ) - Find the correct initialisation sequence. ( hardest part ) - or just clone the sniffed traffic ? With a customised font it now looks like this
  23. Excellent!
  24. Looks good so far...but need to test in different lighting conditions in-game.
  1. Load more activity
×
×
  • Create New...