Jump to content

RAZBAM_ELMO

Members
  • Posts

    2093
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by RAZBAM_ELMO

  1. No need for the sarcasm. Instead perhaps try. " Hello Elmo, it has been some time since I submitted my report, is RAZBAM having a look at this possible bug with regards to the emergency jettison on the Mirage?" See how much more adult and constructive that sounds?
  2. Until certain features are added in, it makes it easier to have it off by default for startup. Both for the harrier and mirage. Once certain features are implemented then it will work as described. Right now its a placeholder.
  3. Thanks for the info Tippis.
  4. We are in the process of acquiring the controllers and integrating all of our modules with those. However it may take a while to properly integrate them. MArking as FUTURE IMPLEMENTATION and moving to RESOLVED.
  5. As schmitt correctly stated its for those that want the VTB displayed on another monitor. Marking as USER ERROR and moving to RESOLVED
  6. Alright, lets make some things clear here guys. First, I apologize if things dont work the way you wanted specifically. I have CB access but due to the birth of my child I was unable to thoroughly test ever bug as the internal patch came 3 days before release. Second, the nasty negativity surrounding a bug that was technically fixed but just needs tweaking now is abhorrent. You guys can argue, complain and bug me all you want. I dont mind that, but you will do it without sarcasm and make sure its constructive. The HSI now works both ways as I understand it yes? Alright cool. Now you're saying the values are changing in an odd format? If so can you provide me better clarity as to what you believe the values should be changing at? Rho is changing in 15nm steps and you want it in .1nm steps? Theta is changing in 6 degree increments and they should be changing in 1 degree increments? Also FYI I deleted the off topic and sarcastic posts because they do nothing to add to the conversation and were off topic. So if you're wondering where your post went or why it was edited...thats why.
  7. So this is not a bug per-say than it is more of a request to have our modules function identically to every other modules in DCS if I'm understanding this correctly?
  8. Negative. I cannot get it to appear either and I was showing the devs in a live video how I was doing it. It is being looked at and will report back if there is a solution or you will see it updated in a future patch.
  9. Confirm it is working for you now?
  10. Marking as FUTURE IMPLEMENTATION and moving to RESOLVED. The system is there and the SME was having a look over it and has given us a briefing on how it should function. We have the ability to turn it on but have not done so as to make sure when it is, we have it correct the first time.
  11. Well we dont make the other modules, were a different 3rd Party Developer trying different things all the time and experimenting with new features.
  12. Yup, seems like the game thinks the aircraft is moving when its not but the mirage works fine so its a little issue that we need help rooting out somewhere. IT will be solved though.
  13. Wasn't your suggestion but an amalgamated request from many many users
  14. Fairly certain this is an ED issue, can you confirm the same behaviour occurs in other modules with NVGs?
  15. This is AS INTENDED. While some users may want to see the piot body, a large majority ignore it. Therefore the majority won. I tend to have it hidden while starting up and then once I'm airborne ill show it again. Moving to RESOLVED.
  16. Looking into this. Marking as REPORTED. We're working with ED to see if we can narrow the culprit. As with most new things, and with such a broad player base it wont always work with some users and sometimes with others. Hopefully we can get this sorted soon. Thankfully the TTT/ TOT kneeboard page has not had any major issues to my knowledge.
  17. All of the MPCD pages are currently being converted over to SVG. I'm marking this as FUTURE IMPLEMENTATION and moving to resolved as these will be implemented once conversion has been completed.
  18. F14A now shows up on RWR in latest patch. Marking as RESOLVED and moving to RESOLVED.
  19. HTS mode is working in all modes. Marking as RESOLVED and moving to RESOLVED.
  20. Markpoints are able to be edited now after the latest update. Marking as RESOLVED and moving to RESOLVED.
  21. Behaviour is AS INTENDED. TPOD can only function correctly on the right MPCD, though it may still be displayed on the left MPCD. Moving to RESOLVED.
  22. Issue has been resolved in latest update, marking as RESOLVED and moving to RESOLVED.
×
×
  • Create New...