• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Vox-tm

  • Rank
  1. Thanks for the further replies and for the suggestion to increase the number of times VoxATC-X prompts for 'Last aircraft say again?'. At a setting of 5 or more, it's much better and far more usable now. @agood... I think you mis-understood, I was not levelling a criticism at the product, but rather looking for a way to enhance the way it works. All I was hoping for was for the product to respond appropriately to a 'mis-heard' or garbled response, even affer a couple of attempts, rather than just automatically move on. Obviously sometimes the PTT button gets pushed by accident or a readback is mis-spoken and some greater flexibility i felt was needed. With the .XML setting provided in the linked thread i now feel that it's just fine.
  2. Thanks for the reply. So, if I understand this, VoxATC-X/Microsoft Speech Recognition will try to understand what I say and the words I use, and if they do successfully then the prompt will move on the first time. However, if I just mumble something unintelligible, then based on the setting in the .XML file you discussed in your thread I should get that number of "Last aircraft say again?" responses until it automatically moves on, e.g. 5? That being so, I'll try this out.
  3. Not having used VoxATC-X 5.63 for a long time, I'm surprised at how it doesn't seem to respond correctly to the things I say. To test this, I'm running the default tutorial VFR flight from Kansas International - Eppley. If instead of reading what I'm supposed to say I just mumble any old mumbled sound into my microphone, then the first response I receive back is "Last aircraft say again?" - which seems a completely natural and proper response. However, if for a second time I ignore what I'm supposed to say and just mumble some more unintelligle sounds into my microphone, then the dialogue is accepted as correct and the prompt moves onto the next stage. Is this because the Microsoft Voice Recognition hasn't yet learned enough to operate correctly? I would have thought that the opposite would be true, i.e. the more incorrect voice response I make the more "Last aircraft say again?" responses I should get until it learns to distinguish the correct words or not.
  4. Vox-tm

    Button On X-52 Not Working

    Ok, this has now seemed to have rectified itself. Running the 'Joystick Setup' program again, clearing all assignments and re-assigning the button seems to have been the thing that did it.
  5. Hi, I have re-installed VoxATC 5.63 on Windows 7 and everything seems to be working ok in FSX. However, when assigning a joystick button on my X-52 to my 'Press to Talk' function in VoxATC's 'Joystick Setup' application, the button detects just fine and shows correct operation of pressed/released. But when I am in FSX and press the button, I don't hear the static click of the radio when the button is pressed and I cannot talk to ATC. I am able to do so by using an assigned keystroke. Anyone have any suggestions as to what the problem might be? Thanks!
  6. >Well even though I've defeated the issue on my system I'm>just trying to help find solutions for those who do still have>to deal with it. Due to the lack of interest by both Microsoft and Nvidia to rectify this issue, I've given up with MS Flight Simulator completely and moved on. More time is wasted trying to tweak and keep the game stable than actually flying.However, I for one appreciate folks like yourself who keep coming back to these issues to help others, even though you're happy with the operation of your own setup. I sincerely hope you, or someone as equally benevolent as yourself finds the answer to this problem eventually.Good luck,Vox
  7. Yep, tried the beta 169.28 drivers... still the same old crashes. Yada, yada, yada. Unistall 'Acceleration' and use it as a doorstop is my suggestion.Vox
  8. Worth a try, didn't work. Sorry, but this isn't a confirmed fix I'm afraid.Vox
  9. >I have been told that this problem is a Nvidia driver problem.This is the general belief, yes. However, what I fail to see is how SP1 doesn't cause the same CTD that SP2/Acceleration does, with the same NVidia driver? MS changed something in SP2, but because they refuse to provide any further patches, they're happy to blame NVidia.It's all quite sad really.Vox
  10. Mmm... none of those settings appear in my BIOS. I'm using a dual core AMD CPU, so this might only be a fix for you Intel boys. Glad it works for you though - the battle is gradually being won!EDIT: Tried disabling the AMD equivalent - "Cool'n'Quiet" - in the BIOS and it made no difference. SP2/Acceleration is still the same crock of crap that it was before. Oh well, worth a try I guess.Vox
  11. In the end, the only solutions that have improved, but not eliminated this issue are:a) Install SP2. However, this causes a different CTD error (d3d9.dll) and has resulted in me uninstalling the worthless crock of s**t.:( Convert all FS9/FSX 'compatible' textures to 32bit. This elimiates most cases of the 'mvcr80.dll' CTD which I only seem to get on non-pure FSX aircraft (i.e. other than the defaults and RealAir aircraft). Unfortunately some transparent textures stop working when converted to 32bit.So it's swings and roundabouts... neither is a complete solution. Ho hum.Vox
  12. I've tried the display.cfg edit and so far things are looking good! Generally an fps increase, smoother play and best of all no apparent crashes as yet. I'll monitor the situation of course.Great suggestion, seems like a winner - thanks!Vox
  13. Vox-tm

    FSX slow to load all of a sudden

    Hehe, yes I realise :) All I meant was that I had found out what was causing the slowdown. I intend to keep the line in there.Vox
  14. Vox-tm

    FSX slow to load all of a sudden

    Thanks Phil, and I appreciate that you can't speak on behalf of their product, that's fine. It would be a question of detail loss then, that's all I wanted to know really and thanks for taking the time to reply in this thread.Cheers,Vox
  15. Vox-tm

    FSX slow to load all of a sudden

    Phil, I know this has been covered before and you are probably blue in the face already from explaining it... but why is there a 4.5 tile setting? Can the engine not be tweaked to set this lower? And what affect would it have on Horizon's scenery if they authored it at a different QMID. They must have done it the way they did for a reason surely?Vox