Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. Good. Only the latest, 4.517 -- but i don't think there are any new changes since 4.50 which have anything to do with settings. From your previous postsI had assumed, evidently incorrectly, that you must be using an old, unsupported version, but to my knowledge 4.50 is fine with all things settings-wise. The only change which could even remotely be affecting things is this one: 3. Fixed a problem in the new Profiles facilities which occurs when aircraft titles contain [ or ] characters. These are converted to ( and ) characters for use in Aircraft-Specific titles, as [ ] are disallowed in [section] names. The same conversion is now done before adding the aircraft name to the relevant [Profiles] section so that the match will be found okay. But I seem to remember that you said you were not using Profiles -- in fact that you weren't even aware of this facility!? I think we ought to start looking at the INI file, as I actually asked quite a few messages back if you recall? Regards Pete
  2. All offsets a listed with full descriptions in the documents included in the FSUIPC SDK, availble from the www.schiratti.com/dowson web page. Sorry, I've no idea what that means. Regards Pete
  3. I don't have a website (well no operational one) -- only this Forum. Interim updates are always provided in the Updates Announcement at the top of the Forum, along with notes about what has changed. The Schiratti "Dowson" page is not mine, but, as it states there, a collection of all my FS programs put in one place by Enrico Schiratti for general convenience. Only Mr. Schiratti himself can update that page, and it contains the last main releases -- so version 4.50 at present, which you already have. According to Captain Sim's Forum it appears that the 757 is officially working correctly with 4.50 as that is what is installed by their update. And i notice several users are adamant that it all works okay. Regards Pete
  4. The log file will be correct. You can also look in the options -- FS Add-Ons menu, select FSUIPC. The version and date are on the main About page. You can also right-click on the DLL itself, select Properties then Version. Incidentally, I noticed there's an update for the Captain Sim 757 for FSX (see http://www.captainsim.com/products/x757/sp43.html ) The 757 Captain version 4.3 (FSX) The 757 Captain (-200, -300, Freighter) upgraded version 4.3 for FSX is available and includes the following new features, fixes and enhancements: Among the fixes it lists: - Autopilot A/P disconnection fix So maybe you should update your 757? Regards Pete
  5. Further to this: I just checked. The other report of this Captain Sim problem said: So there's apparently some discrepancy going on anyway. You say it works okay till after 4.50, the previous chap said till after 4.323! If you are, in fact, using a version earlier than 4.50, then there's no way I can even investigate your "settings disappearing" problem. There have been a number of changes in this area in any case and whatever problems you have may well be fixed now. Regards Pete
  6. Sorry, but that makes no sense. The fuel quantity can be changed -- it refreshes each time you load a flight, for instance. Fuel quantity and engine running time have no defined relationship, therefore -- the engine running time is cumulative from when you installed FSX unless you remove the files containing the data. Also there is no change at the value when fuel flow changes. It should be I think. Sorry, I've no idea when the value updates. Check the STATE.CFG file for the aircraft in the SimObjects subfolder in the same place as your FSX.CFG file. I think that's where the values are kept. Regards Pete
  7. Sorry, I've not the foggiest idea -- but obviously a heading of 1019 is nonsense in any case. Get the code right first then compare. And please try using the tools (like FSInterrogate) and the documentation provided. Regards Pete
  8. The beginning of the log shows FSX teling FSUIPC4 that the weather at NZCH was as follows: "NZCH&A36 252028Z 20907KT&D304NG 34711KT&A877NG 34811KT&A1791NG 34812KT&A2706NG 34816KT&A3620NG 34926KT&A5449NG 33531KT&A7278NG 32642KT&A9107NG 33546KT&A10326NG 32049KT&A11850NG 100KM&B-1536&D1994 CLR 14/09 08/-3&A877 07/01&A1791 03/-2&A2706 -1/-4&A3620 -12/-26&A5449 -24/-39&A7278 -37/-46&A9107 -48/-52&A10326 -62/-73&A11850 Q1020 ... that's wind 209 at 7kt and QNH 1020. At the end of the log, the nearest airport was NZDN with: "NZDN&A1 252306Z 21007KT&D304MG 32622KT&A912MG 32824KT&A1826NG 33028KT&A2741NG 32029KT&A3655NG 31827KT&A5484NG 32041KT&A7313LG 32362KT&A9142LG 31974KT&A10361LG 32181KT&A11885NG 100KM&B-1501&D1958 CLR 14/09 08/-3&A912 06/-6&A1826 02/-4&A2741 -2/-12&A3655 -14/-25&A5484 -26/-33&A7313 -39/-48&A9142 -49/-49&A10361 -49/-49&A11885 Q1020 ... i.e. wind 210 at 7kt, QNH also 1020. Whilst the weather at the aircraft, at the end of the log, was: "????&A0 252356Z 21207KT&D323LG 100KM&B-1500&D1959 CLR 11/04 Q1019 " showing wind 212 at 7kt and QNH 1019. FSX never provided any weather response for NZQN -- it sounds like it didn't have that listed as a weather station. The log shows this as: 2974110 WX Error: timed out, WX request type 3, ICAO=NZQN and it is consistent, so not a fluke of timing or anything. [NOTE: I just checked the weather station list for FSX -- it's the file called "weatherstationlist.BIN" in the same folder as your FSX.CFG file. There is no FSX weather station at NZQN! ] RealAtis could get the weather AT NZQN by supplying the Lat/Lon instead of the ICAO ID -- the problem with the ICAO ID method is that it has to be sure there is a weather station with that ID. It sounds like the program is getting the default weather (standard QNH 1013, etc) when it fails to read a weather station (and presumably it isn't checking that its request even worked). This would be the GLOBal weather: "GLOB&A0 000000Z 04004KT&D915NG 06614KT&A1830NG 06314KT&A3016NG 09024KT&A5490NG 33524KT&A6028NG 33731KT&A9150NG 14KM&B-500&D1000 14KM&B500&D100 80KM&B600&D100 32KM&B700&D100 48KM&B800&D100 48KM&B900&D100 64KM&B1000&D100 64KM&B1100&D1000 80KM&B1200&D1000 80KM&B2200&D1000 80KM&B3200&D9000 3CU050&CU000RLVN000N 2CI350&CI000FNVN000N 06/04 -2/-4&A904 -11/-13&A1828 -22/-24&A3014 -44/-46&A5448 Q1013 ... showing wind 40 at 4kt and QNH 1013. That, according to FSX, is the nearest weather station -- you'll note the word "nearest" in the log. Regards Pete
  9. Aircraft specific facilities have been in FSUIPC3 and FSUIPC4 for many years, but the streamlined Profile facilities were added in 4.50 and have proved very popular because they are so easy to use. What, you mean the interim updates, 4.517 for instance? Why is this aircraft not working? Why haven't Captain Sim been on to me about it then? Don't they care, does it only affect one or two people? Soon, 4.517 or its successor will become version 4.52 or later and be released as the new full user release, and at that time support will be withdrawn from 4.50. This must occur before I go away on holiday in less than two weeks, so someone should start thinking about getting any such problems sorted, or Captain Sim users will be left hight and dry. There is no way i can or will support old versions. One other person reported that -- from what he said it sounded like a bug in the aircraft which by pure luck didn't have any symptoms before because of a bug in FSUIPC. But I cannot maintain bugs -- they must be fixed. If someone from Captain Sim would only discuss it with me we might be able to resolve it. :-( Getting back to the main issue you have, I'll need to know a lot more about what you are doing and what the differences are in the INI file before and after you make settings, because absolutely no one else has the assignment problems you appear to be reporting. Pete
  10. 22 for a 32-bit float? No factional parts? It is read direct from SimConnect, with "hours" stipulated as the units. So, SimConnect says it is hours, and it appears correct in my experience. Why do you think otherwise? What values are you expecting? There's absolutely no manipulation of this value in FSUIPC. Regards Pete
  11. I'm not answering you in three threads. Please stick to one -- see my answer in the other, which summarised is that you aren't reading the descriptions of what you are reading. Pete
  12. What on Earth is that all about? You'll end up with a right mish-mash of meaningless bits! If you are trying to put approximate values into 10 bits apiece, then, since they arrive as 32 bits (and make full use of that 32 bits), you'll need to convert them all to integers first! Okay. Using my calculator that gives pitch = +4.448 degrees, bank = +1.089 degrees and heading 358.304 degrees, to 3 decimal places anyway. You ARE reading the description of these offsets, aren't you, and not just wasting my time? Pete
  13. Please refer to the offsets lists for their descriptions. It does say clearly that pitch and bank can be positive and negative, for different directions -- how would you accommodate signs in a UINT? And as far as headings are convcerned -- what do you think? Do you like negative headings? They are still meaningful (eg -6 = +354), but are not generally used. Please do read the actual write-ups. And please use FSInterrogate to help you understand variables -- you can see how they behave in real time then. Pete
  14. Well, that's up to you, of course. Incidentally, Squawkbox is actually mostly a separate program -- SB3 can be run as a WideFS client, and SB4 can be used with a SimConnect remote connection. Regards Pete
  15. You just run the Installer again to enter Registration details. Assuming you did actually purchase FSUIPC4 + WideFS7 keys, not FSUIPC3 + WideFS6 keys, then you are most certainly making a mistake. All three parts -- name, address, key -- must be exactly correct. If you aren't sure, use cut-and-paste. Ahso you have fixed it? Pete
  16. This is from the Installer? There are no registration facilities in FSUIPC4 itself, it is done by the installer as is made clear in the User Guide. And you certainly do not need to run the FSUIPC4 installer "as administrator" in any case -- as an installer it has enough privileges. There are no provisions in the registration code in the Installer to grey any fields out. If you have any problems with the Installer please show me the Installer's log file. Pete
  17. The problems you will face trying to get a Managed program module, with all of its encumbrances, running inside a native C/C++/ASM environment such as FS will be pretty horrendous. Quite honestly, I wouldn't know where to start -- and I've been a programmer for 45 years! You don't say WHY you don't want it to be an "external" program. Apart from the ease of language choices, there are two other significant advantages of it being so: 1) Easy to take advantage of multi-core processors, as the program will be a separate process to FSX. To achieve any efficiency in a in-process module you have to take great care to offload much of your processing to other threads, and then try to manage their priorities well. 2) If your program uses the FSUIPC interface only for its connections to FS, then it would be capable of running on a separate PC too, via WideFS. Regards Pete
  18. The version to which the issue of the Manual is applicable is clearly shown on the very first page. It will certainly say "4.50", as version 4.50 is explicitly dated 27th February in its "About" display, in its Properties-Version, and in the Announcement above concerning currently supported versions. So, please tell me, how is your confusion arising? If you mean you assigned an Axis in FSX to the control "STEERING SET", that I think you must be mistaken. There is nothing in FSUIPC's calibration system to even intercept this control let alone calibrate it. The most FSUIPC will do with it is Log it (if you select Axis event logging). The calibration facility in FSUIPC for a tiller works on the axis assigned in its own axis assignments for a tiller, and it uses the FS RUDDER control to operate -- at low speeds, on the ground, with gradual transfer to rudder axis input. This is exactly the same facility provided in FSUIPC3 for FS9 and before, which versions of FS never had a "STEERING_SET" control built in. Yes, I assumed then that Microsoft must have implemented a true steering control, though, sorry, I've never tested it in place of the FSUIPC provisions -- which I am very happy with in my own cockpit. No one so far has provided any feedback on the FSX provisions, but they may be in use by non-FSUIPC users. This most definitely indicates that you are using the FSUIPC provisions, then, not the FSX ones. As it sounds like you've not actually tried the FSX built-in provisions, I'm not sure that can be accepted as a valid statement. No idea, but please understand that this is in no way a "kick-in". The changeover operated by FSUIPC is progressive. If the limit is 60 then at 30 knots the Rudder and Tiller each have 50% of the control. As you accelerate you are using more rudder and less tiller. You only have full rudder control at and after that speed, and you only have full tiller control at 0 knots (;-)). I think this is reasonably realistic for most aircraft, but I've only tried in in a real Cessna. Regards Pete
  19. Yes. The problem is that compatibility mode makes Vista lie to programs, telling them they are running on XP. This makes FSUIPC use the XP registry keys to find data, like your joysticks. These keys are different between XP and Vista. Well, I wouldn't recommend it, but either way I did change FSUIPC4 to check both sets of registry keys -- that mod is in the interim update in the Announcements above. Regards Pete
  20. Does FSX? Are you running FSX in WinXP compatibility mode by any chance? If so, don't (there is no need -- FSX is fully Vista aware). Or download the update for FSUIPC4 in the Updates announcement above, which does get around this mistake by some users. Regards Pete
  21. Offset 255 is undefined in FSUIPC3, it is clearly documented as new in FSUIPC4 -- all the entries in BLUE are new. Please do refer to the documentation! If your only guide is FSInterrogate data, which is a data file put together by many folks over the years, you should be more cautious. However, in this case it explicitly only checks FSX in the list of applicable FS versions for that offset!! :-( Pete
  22. Er, 0225 is within the 256 bytes assigned for the current flight plan in FSUIPC4. Before FSX it was never assigned for anything. 0256 is clearly denoted in the FSUIPC4 offsets as new for FSX, and is also checked against FSX only in the FSInterrogate data. Evidently you aren't looking that far? Did anything before FSX have thermal visualisation? 0C44 is documented in both FSUIPC3 and FSUIPC4 documents. And it is clearly marked in the FSUIPC3 programming documentation as not working in either FS2002 or FS2004. You need to go back to FS2000 to get that. However, it does work in FSX. It is clearly marked in the FSInterrogate data (the checkmarks for different FS versions) as being for FS98, FS2000 and FS98. Please do check the documentation AND the FSInterrogate data a little more thoroughly before such reports. ErI have it down as not working at all in FSUIPC4. I've checked the code, and there is nothing populating that offset, so whether it says 4 or 64 is irrelevant. It doesn't work. I'm surprised it isn't zero -- some other application must be writing there? How? There are facilities in SimConnect to create and control cameras, but no provision at all for reading about them. Regards Pete
  23. Really? That must be a function somehow of the video drivers, because the sizes and positions of each of the undocked windows get saved explicitly when you save a flight. Wait a minute -- you aren't running your full screen at a different screen resolution to your windowed setup, are you? That would certainly give such symptoms, as obviously the pixel count would be different. You should ALWAYS run FS full screen at the same resolution as Windows, and that should also be the screen's own default resolution. Else you will be losing performance and quality. Regards Pete
  24. Not specifically. As many aircraft as you like (but really those are best assigned to the new Profiles system, much better to organise and assign). There are limits on how many buttons, keys and axes you can assign, but these are very generous, running to the thousands. There's never been anyone anywhere near any limits yet. Sorry, I don't know what you are doing there, then. You need to check that the INI file has indeed been updates when you OK out of the FSUIPC options screen. Also, please check that you ARE using the very latest version of FSUIPC. Note that for FSX, FSUIPC 4.50 is the oldest which gets support. There is a later ones in the Updates announcement here which might be better for you. D No, never. Best to use the Profiles facilities in any case. They are much more user-friendly and convenient. Pete
  25. No, it is easy.Ssimply follow the steps in the User Guide first, to get proper max/min values and, for aileron, elvator and rudder a null zone in the centre so that when you let go you know definitely that the control surfaces neutralise. Then click the slopes button and select a slope with a flattened centre -- not too flat or it will make it harder to fly. (For a jet fighter or stunt plane you'd probably have the reverse -- much fiercer control -- but certainly not for airliners). Regards Pete
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.