![]() |
Quote:
Bill |
I've tried everything. It just does not seem to work. I might try downloading the next release and see if that works. Thanks for the help.
Scavone |
Quote:
Bill |
[/quote]
Are you running Vista? It occured to me that some people had problems with the speech engine vs. Vista. I think it's resolvable, but you might want to hunt through this thread to see how they fixed it. Bill[/quote] No, I'm running XP. I've checked all the forums and the only post I could find dealing with a problem like mine was the on the Ubisoft forums. Scavone |
Are you running Vista? It occured to me that some people had problems with the speech engine vs. Vista. I think it's resolvable, but you might want to hunt through this thread to see how they fixed it.
Bill[/quote] No, I'm running XP. I've checked all the forums and the only post I could find dealing with a problem like mine was the on the Ubisoft forums. Scavone[/quote] Hmmm, I have to think on this one... |
Question is this mod/program compatible with RFB mod and the PE v1.5?
|
Quote:
The same with PE v. 1.5. I have neither of these, so I cannot say for certain... Sorry! Bill |
Quote:
To get it working in Vista, I had to jump through some hoops but nothing had to be changed in shSpeech. Basically I had to configure Vista to get Speech working. Unlike XP, where my program can invoke it on a whim and it's always available, in Vista it is only available if you launch it. When it's running, you'll see a very distinctive control panel widget at the top of your screen that says "listening" or something like that. When this is running, you've made huge progress toward getting shSpeech working in Vista. That's basically all I remember doing and it was fine at that point. I wish I could be of more help, but it's been so long since I've worked on this, I've forgotten everything and I feel as I'm coming into it as a newb like everyone else, in a weird sort of way. |
Coolhand,
Your problem certainly seems to be resolution based. Here is what I suspect is happening. You have set the game to 1024x768 and the shSpeech to 1024x768. However, on some video cards with certain displays, especially televisions or widescreens, it's possible that the video card is doing some sort of scaling to fit the window to the physical display. As a result, the game is pumping out 1024x768 data to the video card, and then the video card is changing it to be something else before it reaches the display - say 1055x755 for example. shSpeech will then click the mouse pointer based on an offset from the upper left (0,0) and miss it's mark, since the far right side is actually not 1024 and the bottom isn't 768, but in fact it is something else. This is usually due to some kind of overscan or underscan compensation that the video card driver is doing, perhaps automatically on your system. The biggest indicator that something like this is happening is that your round dials are not really round, but are in fact ovals. One way to find out the actual resolution is to use your monitor's physical button controls to pull up an info window to see what the current video resolution is. Most monitors have this (my Plasma TV, for example, has an info button on the remote that tells me what mode I'm really in.) Another possible way is to use the SH4 screenshot button to get a BMP file, and then open it in an image editor to determine the resolution. This *might* show 1024x768 and so if that's the case yet you have ovals, this is not to be trusted, and you would want to use the monitor info button method. Unfortunately, if you have ovals, even if you figure out the actual pixel width/height and put it into shSpeech, it might still fail because I'm not sure if the algorithms take non-round controls into account. It might just work but my sense is that it will not. The only possible solution is to experiment with different resolutions supported by SH4 that provide you with perfectly round, non-oval controls and then try that resolution in the shSpeech BAT file. I hope this helps. Hi everyone. Wish I could be here more. |
The tube issue where W cycles only the fore tubes is in fact something I experienced with Trigger Maru's config file changes. There could be other issues if your config file is based on TM.
I'd also warn that the shSpeech BAT files that run in Trigger Maru mode may not have kept up with the changes in the last several months in TM. Anyone could feel free to modify the TM CSVs I provide and send them back to me once they're confirmed to work, and I'd be happy to release a refresh update to include these. Personally I play pretty much stock (when I play, which is never) and I make sure that I'm always using the stock keyboard configuration file (which I believe is cfg\Commands.cfg but I could be mistaken.) Good luck! |
Quote:
Bill |
Quote:
I have alway's had round dials no matter what resolution I'm running and the monitor menu shows the same resolution as I'm running in the sim. If I alt-tab out it shows the resoluton of my desktop. My monitor is a Sony Trinitron model G520 21" flat screen. Again, thanks for the help....CH |
Quote:
That's a CRT and should directly support all modes it says it's capable of. What happens if you play at its max res of 1600 x 1200? Besides slowing to a crawl, that is... ;) Bill |
Same -O-same-O....I've tried every resoluton I can and get the same results, unfortunately....CH
|
Quote:
Bill |
All times are GMT -5. The time now is 01:33 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 1995- 2025 Subsim®
"Subsim" is a registered trademark, all rights reserved.