kronovan
-
Posts
27 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by kronovan
-
-
I started up FSX:SE last night and discovered that my CH PRO PEDALS USB are no longer mapped. When I accessed Addons > FSUIPC and clicked [Axis Assignments] , nothing was listed when I moved my pedals - same for the toe brake axis. Even when I did a rescan nothing is detected for rudder movement. So I checked the FSUIPC.INI in my ..\FSX\Modules\ folder and noticed that my CH PRO PEDALS USB aren't even listed in that file's JoyNames section. This is what's listed:
Quote[JoyNames]
AutoAssignLetters=No
3=Saitek Pro Flight Throttle Quadrant
3.GUID={B32171A0-7A3C-11E8-8002-444553540000}
4=Saitek Pro Flight Yoke
4.GUID={B5B80690-CB75-11EA-8001-444553540000}
1=T.16000M
1.GUID={5F9FFE80-C37D-11E9-8005-444553540000}I created a backup copy of that INI file a weeks back, as I was considering editing some of my profiles, but never did make any changes. This is what the JoyNames section looked like then
Quote[JoyNames]
AutoAssignLetters=No
0=Razer Tartarus V2
0.GUID={5F9FFE80-C37D-11E9-8005-444553540000}
1=Saitek Pro Flight Yoke
1.GUID={6A324B00-C37D-11E9-8006-444553540000}
2=CH PRO PEDALS USB
2.GUID={B32171A0-7A3C-11E8-8001-444553540000}
3=Saitek Pro Flight Throttle Quadrant
3.GUID={B32171A0-7A3C-11E8-8002-444553540000}
4=Saitek Pro Flight Yoke
4.GUID={B5B80690-CB75-11EA-8001-444553540000}Note the error though, in that the CH PRO PREDALS USB and Saitek Pro Flight Throttle Quadrant are listed with the same GUID. I did disconnect my Thrustmaster T.16000m around that time, as I'd just gotten my Saitek Pro Flight Yoke and was short a USB cable, which is why it isn't in that list. Not sure why my Razer Tartarus V2 is no longer listed, but I never configure it internally within any flight sim anyways. I also found a file in the \Modules folder called FSUIPC4.JoyScan.csv and opened it. I noticed that my CH PRO PEDALS USB are listed in each of the 3 sections and have confirmed via the Windows Registry that the VID and PID values for the CH PRO PEDALS USB are correct. I'm not sure of the other long hex value (I'm guessing that's the GUID), as there doesn't seem to be an equivalent of it in the registry.
I should probably mention, that all of my USB devices (including rudder pedals) are working correctly when tested from the Windows 10 - "Devices" > "Devices and Printers" > "Game Controller Settings" > "Properties". As well my CH PRO PEDALS USB are being recognized and working correctly with X-Plane 11, IL-2 Cliffs of Dover and the IL-2 Battles of Stalingrad flight simulations.
So I'm wondering what I need to do to get FSUIPC to recognize my rudder pedals again? Could it be a simple as renaming that FSUIPC4.JoyScan.csv file and then stating up FSX?
Any help in getting this resolved would be much appreciated.[Edit] Just realized, I should have also mentioned that with FSX started, I can access Settings > Control > [Axis] and successfully map my CH PRO PEDALS USB to the rudder axis - which I then immediately delete. I checked axis mapping from that same FSX form for all of my USB devices and none of them have any axis mapped.
-
2 hours ago, Pete Dowson said:
It sounds like you want to use the throttle with a full forward thrust to full reverse thrust range, and a centre (or offcentre) idle zone.
To do that you need ot assign calibrate on the 4 throttles tab ieither by using the map to 4 on the first tab, for a single throttle, or by assigning 2 or more levers to separate engines in the first place). On the 4-throttles calibration page you can make sure "No reverse range" is unchecked, then simply do yuor proper calibration for a max reverse, centre, and max thrust position.
If by 'To" you mean trying to calibrate a specific place for Take Off thrust, surely that's normally max, or very close, with a desired N1% which varies by conditions (weight, weather, runway length & condition).
Pete
Many thanks for the reply Pete. I didn't really grasp all of the explanation in the manual about the different throttle tabs, such as 4 throttles, so I'll go back and reread that section. Indeed the To for the Throttle Incr (full forward thrust) would be the max for the particular lever.
I'd dearly love to assign more than 1 lever for engine control, because some of my aircraft such as Aerosoft's DHC-6 Twin Otter are next to impossible to fly without 2 quadrants. Alas I only have a single throttle quadrant with 3 levers; throttle, prop & mixture. I also use a joystick instead of a yoke, as I also fly a number combat flight sims and keeping my GA configuration similar helps me be more effective in those. That of course means I don't have many levers on my stick to use and the 1 throttle axis I have gets assigned to elevator trim.
I could afford to buy an additional quadrant or replace with a 6 lever quadrant, but they're all out of stock in my city and web-stores that have reasonable shipping to my region in Canadian appear to be all out of stock too. I'm guessing that this is a result of the pandemic disrupting supply chains and forcing some manufactures to temporarily shut down.
-
Hello all, 1st time posting here. My apologies if this has already been covered somewhere else in this forum, but my search-foo didn't come up with anything.
I have a single Saitek ProThrottle (model with red, blue and black handled levers, w/6 rocker switches & 3 detents) which has increments of 0, 25, 50, 75 and 100% marked on its levers. I've gotten Throttle Decr working via a button assignment to the detent button below the throttle lever, but what I'd instead like to have is Throttle Decr be controllable in a range beginning at the 25 increment mark and ending at 0. I've tried this by creating 2 ranges for the throttle axis; 1 for Throttle Incr with a From at the 25 increment and a To at 100, and 2 with a Throttle Decr with a From at the 0 mark and a To a the 25 mark. It doesn't seem to work however, with the Throttle lever still effectively having Throttle Incr from 0 to 100? I did notice that the From and To values flipped for the 2nd Throttle Decr range I set. I didn't find much in the manual about the "Up" and "Down" check boxes and I'm not really sure what they should be set to for these 2 ranges; wondering if that's where I'm going wrong? Or is this just not possible to do for such an input device as ProThrottle?
If anyone could give me any feedback or suggestions for doing what I hope to achieve, I'd appreciate reading about them.
On another note, I have FSUIPC version 4.794 installed with FSX:SE, but I'm not running the beta branch. Do I need to upgrade to 4.795a? I'm nervous about any upgrading procedure that's done by installing over the top of an existing version - too many problems with other such approaches to updating in the past. So if my version is current enough please let me know.
-
Ummm.... where did you read that? Freight Dogs news now is 2 or 3 years old I'm afraid :oops:
LOL..OK :) I found that reference on the FSAddon website under the 'Freight Dogs' section on the "Downloads' page. It mentioned that the Cessna livery was being designed by Ruud Faber. Unfortunately, I didn't notice the date on the right side of the page. No problem if it never happened or is no longer available, if I want liveries to enhance the immersion I could always join 1 of the VA's in my area.
-
I noticed on the FSAddon website that a Freight Dogs livery will be coming soon for the Cessna. I'm taking it that it's for the stock Caravan that comes with FS9; right? When I click the current link I just get directed to the FS Cargo Tutorial doc. I really like the sence of immersion I'm getting flying for Freight Dogs co. and quite frankly I'm sucking at landing the Beaver on ground strips, whereas I'm much better with the Caravan. Is there any idea when the new livery will be available?
-
Well, I bought Freight Dogs this weekend and as expected I'm enjoying it very much . Well worth every penny that I paid for it...umm...how do I say that in Euro's? :wink:
-
Gary, many thanks for the feedback and all the links. :)
Regarding the "Maule" for FS2004 (FS9), are you referring to Mikko Maliniemi's outstanding Maule?Yes I was actually referring to Maliniemi's Maule; I must have been thinking about old movies when I wrote Maude. :roll: I agree that it's an outstanding aircraft.
Reportedly Milton Shupe's Freeware Twin Beech 18 is better than the Aerosoft model included, but generally the included Beaver models are regarded as "good" quality.Out of the 2, it's the Beaver that I'm most interested in so it sounds like Freight Dogs will be worth it for me.
-
I'm looking to purchase the Freight Dogs package and was wondering about the quality of the included DH Beaver and Beechcraft. I orginally posted my query in the FS Cargo forum and Francois suggested I might get more responses if I posted it here. So here it is:
I prefer to do my VFR/sight seeing flying with amphibious aircraft. I currenlty only have the Caravan included with FS9 and the Maude; both of which I find more than satisfactory. What I was wondering is how do the Freight Dogs included aircraft stack up against the 2 I already have, in terms of flight models and the quality of the 3d cockpits?If anyone could give me some feedback on these 2 aircraft, I'd greatly appreciate it.
Cheers,
Kronovan
-
Yes, it is a 'light' version of FSCargo, i.e. without the option to make your own missions.
But if you download the FSCargo Upgrade from our website after installing Freightdogs, you'll automatically get the full version :wink:
As for the aircraft, that's a matter of taste. I find them not bad. And the scenery that Bill Womack included is superb.
Thanks for the response Francois.
I prefer to do my VFR/sight seeing flying with amphibious aircraft. I currenlty only have the Caravan included with FS9 and the Maude; both of which I find more than satisfactory. What I was wondering is how do the Freight Dogs included aircraft stack up against the 2 I already have in terms of flight models and the quality of the 3d cockpits?
-
I'm looking to get the Freight Dogs package for FS9. A question I have; is the version of FS Cargo that's included in the bundle the full FS Cargo product or a scaled down version?
Also, if anyone could comment on the quality of the DH Beaver and Beechcraft aircraft that come with the bundle, I'd greatly appreciate the info.
Cheers,
Kronovan
-
No worries. Do post somewhere how you resolve the issue ...
Jon
Well...problem was resolved by getting the correct version. LOL! I originally downloaded the v.1.2 from vancouverlandings.com, but in fact the most recent version is 4.1! I still encountered a problem with the CYYJ installer -install button wouldn't appear on the form- but I was able to work around it. Airport looks great and appears to be perfectly compatible with Victoria+ v.06
-
You can get support for CYYJ at http://members.shaw.ca/cyyj2007/, click on Support, check out the comments there. There is a link to email near the bottom that'll get Don's attention.
Alternatively, Don is known to visit:
viewforum.php?f=231&st=0&sk=t&sd=d&start=0
Jon
Thanks Jon, will do.
-
I'm not sure if this is the right forum to post this in or not. I did notice another member had posted here before me regarding Don Grovenstine's CYYJ addon scenery. And since members here were very helpful with my previous Vancouver+ problem, this was my 1st thought.
My problem is that whenever I enable the 2 CYYJ v1.2 scenery libraries and attempt a flight from Victoria International, FS2004 crashes to my desktop. I don't own the Ultimate Terrain package but I do have the Victoria+ scenery installed and I haven't had any problems running it. I also have Vancouver+ enabled and after resolving a problem with a missing landclass library it's also been working perfectly. In addition to the 2 above, I also have the World Extreme Landscapes mesh installed which is really a repackaging of the FS Genesis mesh.
I've gone over the CYYJ doc a number of times and it appears that i've done everything correctly. I have noted that the version of Victoria+ I have installed is 1 version more recent than the 05 that's referenced in the doc. I've also tried enabling the 3rd library for the CYYJ scenery which is designed to enable compatibility for owners of UT and Victoria+, but I get the same result; CTD!
If anyone could give me some suggestions or direct me to another more appropriate forum, it would be greatly appreciated.
-
Well I manually added the Vancouver+ landclass libary tonight and I'm pleased to say that the Tsawwassen area scenery is now correct. And gee... a number of other things look better now too. :lol: If anything, all of this has proved that Vancouver+ is indeed compatible with World Extreme Landscapes.
-
Seadog aka Doug,
Thanks for answering my query. I haven't looked into the Vancouver+ repair tool much, so I'll likely do that tonight with the object of getting the landclass library in place.
Good to know I installed the WEL scenery correctly. Biting the bullet and reinstalling it has been worth it, only because I now have at least a little knowldege of FS9's scenery management system.
-
I may, or may not, have found a problem, but when reading through the install doc for Don Grovenstine's CYYJ addon I noticed that the Vancouver+ installation shown in the scenery libray screen shots also included a landclass libary. The installation I performed only insalled a scenery and landscape library. Is this the possible cause of my problem?
-
Just to let you both know, I've now reinstalled the WEL terrain mesh into a custom folder and have manually created a WEL entry in my scenery libray listing. I'm hoping I did it correctly, but I have a few doubts. Perhaps either of you can confirm something for me.
When I reinstalled I chose a custom path of: 'C:\Games\Flight Simulator 9\Addon Scenery\WEL'
During the installtion the following subfolders were created: 'C:\Games\Flight Simulator 9\Addon Scenery\WEL\World\Scenery'
The above scenery subfolder is filled with many, upon many. files with a BGL extension. When I used the Scenery Library [Add area] button FS9 would only let me specify a path of 'C:\Games\Flight Simulator 9\Addon Scenery\WEL\World'; wouldn't allow me to include the scenery subfolder. Is that correct, i.e. is FS9 automatically aware of the Scenery subfolder and know that it contains the terrain mesh files?
When I exited FS9 and restarted I did get the scenery generartion screen, so I'm assuming I was successful. I named the new scenery entry "World Extreme Landscapes' and it's now located in the #1 spot in the scenery priority listing. If either of you can confirm that what I did is correct, I'd greatly appreciate it.
-
Never mind, I remembered I had an old trial intall of PSP8 on a CD=ROM, so I used it to convert them to JPG's. I've got 2 screen shots of before and after the uninstall of the WEL terrain mesh. In each set there's a screenshot of the cargo dock north of the Tsawwassen Ferry terminal and 1 of the ferry terminal.
BEFORE:
AFTER:
-
Jon,
The only screen capture utility I have is FRAPs, but it's unregistered and therefore only captures in BMP format. I tried uploading my screen captures, but this website refused the BMP format. Do you by chance have an FTP site or email address I can send them to? Failng that, if you can refer me to another screen capture app, that would work too. Just to let you know I removed the WEL terrain mesh, but still encountered the same problem as before.
-
Incorrect, Francois. Gong!!! Global meshes should be at the top of the scenery order in FS9. However if this is a 38m mesh with aircraft included, it should not have any effect on Vancouver+. The uninstallation of that product would also confirm it had no other goodies in it.
kronovan, can you provide us a screenshot of the problem?
Jon
Jon, I had full intention of getting you some screenshots last night, but a curve ball was thrown may; my Logitech mouse bit the dust. Without a spare in the house and it being to late to get to a big box store, it was a no go. I'm going to bring home a mouse from work tonight, so I'll be able to get a FS9 flight going and post some shots.
-
Oops, by "check out" vancouver+ I meant after uninstalling the mesh, try Vancouver+ in the sim. If you still see the issue, we can quit blaming WEL, or at least its prority.
LOL Now that I read it again it's quite obvious what you meant. I think it was more a case of me not seeing the forest through the trees due to being a bit too focused on the technical details.
Abacus support is correct: the higher resolution mesh will have priority. However if the mesh resolution is the same (and I don't know what they provide for this area, Vancouver+ is 19m if your TERRAIN_MAX_VERTEX_LEVEL (“TMVL”) is set to 21 as you've done), the one that is LOWER in the scenery priority list overrides, unlike normal scenery. (This is true for FS9 only).So here's a question: what resolution is the WEL mesh? What else besides mesh does it provide? Landclass? Aircraft?
Jon
The WEL mesh is 38 and 78 meters. I'm not sure about Landclass, but it does install a Vans RV-6A aircraft as well as a series of pre-saved flights. Apparently the terrain mesh used in WEL was created by Justin Tyme at FS Genesis.
-
In regards to the tv set you seem to be using: how do you get the program bar at the bottom of your window to display then?? :shock:
Most ATI and Nvidia video card drivers, begininng about 3 years ago, include what's called underscan compensation. Which means that the video card can be configured at a special resolution to compensate for the HDTV screen border clipping. I.e. for my Nvidia video card, what should be a 1280x720 resolution (standard HDTV 720p) becomes a special underscanned resolution of 1136x664. After underscan is set, the Windows desktop is outputted to the HDTV such that the task bar and the top of the desktop are positioned correctly on the viewable area of the HDTV while no portion of the desktop is displayed on the horizontally and vertically clipped portions of the screen.
The problem arises for me when I have an application that contains a non-resizable window or form that's wider than 1136 pixels or taller than 664 pixels, which unfortunately is the case with the Vancouver+ config utility. Unfortunately there are many, upon many, PC games that don't support widescreen, let alone custom widescreen resolutions; thank god FS9 does! Of course almost every current gen plasma or LCD HDTV comes with DVI or 15 pin D inputs and support proper PC native resolotions, so it's likely no longer an issue.
-
Before I uninstall and reinstall I thought it might be worthwhile for me to email Abacus support and inquire as to whether World Extreme Landscapes will only replace the default scenery. So I'm currently awaiting a response back from them; who knows how long that will take. :roll: Just for clarification of the following comment:
BUT I thought of something: after you've uninstall the mesh, and BEFORE you reinstall, check out Vancouver+.Do you mean remove the checkbox beside the Vancouver+ entries in the FS9 scenery library listings?
I wasn't able to do any flying last night so unfortunately I don't have a screenshot; will try to get one tonight.
In regards to temporarily changing my screen resolution. I could do that, but the bottom portions of my windows desktop would still be offscreen and inaccessible. As I mentioned before my HDTV is of the older tube variety that didn't support native PC resolutions or even VGA or DVI inputs. Like many HDTV's of it's gen it clips a border consisting of roughly 8% of the image around the edges when receiving a HDMI signal; something to do with the early progressive scan DVD players distoring the edges of images sent through HDMI. So in a nutshell it won't auto scale my PC desktop like newer HDTV's do. The image quality on it is great, so I'm not complaining too much. :wink:
[Edit] I got a quick and informative response back from Abacus; so I've had to eat a bit of crow regarding my above comment. :oops: The first part of the response just confirmed what I more or less already knew about FS9 and what's stated in your Vancouver+ manual regarding 3rd party terrain mesh:
Our World Extreme and USA Extreme tanke advantage of what is called the Adaptable Mesh Terrain Technology of Flight Sim. This technology allows Flight Sim to load only the terrain files that are at the highest reolution for any given area. So if you have 76-meter data and 32-meter data being loaded for the same area, FS knows to load the 32-meter data. This is Flight Sim technology, not ours ;+}The 2nd part of the response is really confirmation of what you've both already suggested:
We simply install our files right along side the default files of Flight Sim and Flight Sim automatically loads the higher resolution terrain. There is no way to seperate the files, at least not easily that I know of... I suppose you could uninstall and re-install to a new folder, then manually add every new scenery folder from WEL to the Scenery Library, but we've never tested that.Changing the folder during the install will put the scenery in a new location, but then Flight Sim will not load it nor the aircraft that comes with it.
So the way I read that, please correct me if I'm wrong, is that it's possible to do a custom folder install and then use the in the FS9 scenery library [add] button to individually activate and create scenery library entries for the WEL terrain mesh. My only concern is just the sheer number of separate libraries I might have to add. I'm think I'm just going to bite the bullet and do it anytways, only because it will give me more control over all scenery libraries and aid in resolving any library conflicts.
-
Many thanks Francois and Jon for some further suggestions.
My default 'Addon Scnenery' folded has a subfolder named 'Vancouver' which contains the CYVR42+ addon and a subfolder named VicPlus -I was too much of a newb to know that I could have pointed it ot the 'FSAddon folder- which of course contains the Victoria+ scenery. Both of those sceneries appear to be working fine. It does look like World Extreme has taken over the default scenery as I really can't find any reference to it in my FS9 folders other than a folder named 'World Extreme Landscapes', which just contains a readme and a flight manual PDF. Currently my default scenery is at the very bottom of my library list. When I tried moving it above the Vancouver+ entries everything got messed up badly.
I'll follow your suggestions of reinstalling the World Extreme mesh in the Addon Scenery folder. Of course since it comes on 4 CD-ROMs it isn't going to be a quick process. :(
[Edit] Another problem I didn't mention earlier is that because the PC that I run FS9 on only outputs to an older gen HDTV, I have to run at a special resolution of 1136x664. At that resolution, not all of the Vancouver+ Configuration utility is visible and because of the mode it runs it I'm not able to move it to view the bottom of the form. As well, since the utility doesn't contain scroll bars I'm unable to access any of the checkboxes located on the bottom portion of it. I'd be the 1st to admit that my gaming setup is a bit unsual, but any other user who has a 720p HDTV that needs to enable what's termed underscan compensation for their video card would encounter the same problem.
What's the possibility of scroll bars being placed on the main form in a future update?
Suddenly Lost my CH Pro Pedals for Rudder Control
in FSUIPC Support Pete Dowson Modules
Posted
Thanks for getting back to me Pete.
I resolved the problem and it turns out it was being caused by the Razer Tartarus 2 - not a total surprise because I've found its driver and software on occasions to be problematic. Once I disconnected the Tarturus keypad, ended its Synapse applet and ran FSX, the CH PRO PEDALS USB were correctly enumerated and written into the FSUIPC.INI file. However, when I reconnected the Tartarus and ran FSX again, the Saitek Pro Flight Throttle Quadrant and Saitek Pro Flight Yoke were incorrectly written into the INI as Razer Tartarus devices!? The solution was to reboot my computer and run FSX again, whereupon all of my input devices were written into the INI correctly - including the Tartarus.
I had disconnected and reconnected all of my HOTAS devices recently, so maybe that explains what triggered this. As well, the Tartarus' Synapse software got updated this week, so maybe that was the cause. All my USB devices with the exception of the Tartarus are connected to a single, powered USB 3.0 hub. Situations where I encounter a problem with a USB device not being recognized have been far more rare than common.