Jump to content

Pete Dowson

Commercial Member
  • Content Count

    2,439
  • Donations

    $50.00 
  • Joined

  • Last visited

Everything posted by Pete Dowson

  1. It will be loading it up automatically if that specific aircraft is actually assigned to that profile. Why do you think that is not happening? There are many variants of the NGX installable. If you want the profile to cover them all you have to do a small edit to the settings file (FSUIPC4.INI). There is ample coverage of this in the documentation, and even user examples. If you think you have a problem or further questions on thist, please come to the proper FSUIPC support forum. I do not do FSUIPC support here. Pete
  2. Surely it is dependent upon whether you run any other processes on the same PC. Obviously (?) it is not really a good idea to restrict P3D's use of processors when there's no need. The use of AM settings really only comes into its own when there are other processes running which could conflict. You then need to split them onto different processors. Pete
  3. Yes, it is FS9, with FSUIPC + WideFS + WidevieW. The forward view is provided by 3 projectors via mirrors, to give a better illusion of depth to the image. There is another PC linked via WidevieW to give a different view, and a 4th screen on the main PC which is a copy of the centre projection, via a DVI splitter. WideFS is used to link two other clients providing "Instructor Panel" type facilities, mostly operated by a custom lit push button panel. One or two screens are used with FS Commander in order to show the position on a map, though I must admit the map resolution was pretty poor. Just a series of straight lines. To run the same number of screens with FSX or P3D with, say, FSLabs Concorde X, would probably need a much more powerful PC. Also the links to and from all the instrumentation (MIP, and centre console are pretty much completely working, the overhead and engineers panel only partly, at present). The software for all this was custom made by an external consultancy, and I would guess converting to Concorde X would be a large job, and maybe not even possible unless FSLabs would provide assistance or at least an SDK (like PMDG do for their 737NGX and 777X). Pete
  4. FSUIPC patches G3D automatically if it needs it, but it's only one crash out of many possibles. If you are getting consistent crashes it is likely you have bad or corrupted scenery files. And they would crash in P3D too. You might need to eliminate scenery layers. I do things like that by halves -- last half, then first half (excluding the default layers of course), then half again for the half in which I get the problem, and so on, until you get the one layer. Trouble is if you have more than one problem scenery layer that don't work. Incidentally I've never actually had a G3D crash -- I had to get others to test my patch for me. And I have almost all the payware airports you can get for Europe! The only ones I've had have been in other places, like TERRAIN.DLL. Pete
  5. There is no harm in always disabling controllers in FSX. If you are assigning at all in FSUIPC you should always do so. The only thing you need to be careful of with some add-on aircraft, like PMDG in particular, is to assign to the regular FS controls (names Axis ....), not "direct" to FSUIPC, nor the older more versatile controls like "ThrottleN set" and so on. That's effectively identical to assigning in FSX itself. Also the PMDG ones will not take well to you calibrating the throttles in FSUIPC. Just do the assignments. Pete
  6. In fact it only traps ONE, the most common one. I looked at some of the others but they were much more varied and in parts of the code I really couldn't do anything about. The G3D error FSUIPC traps was fixed in FSX-SE and P3D2.x and 3.x. It still existed in P3D1.x. Pete
  7. Okay, I've found out what was dragging P3D 3.2 down at EGLL. It was Orbx FTX England. I've now installed UTX 2.1 Europe and put that on top (higher priority) of Orbx FTX Global. FTX Vector is disabled completely (but I did that a while back). I've disabled FTX England, Wales, Scotland, Ireland and N.Ireland. It's actually a bit of a relief. I was dreading finding problems at the UK2000 airports of which I have all. With that arrangement, performance in my benchmarks at Heathrow is up there with FSX-SE's, or maybe slightly above, and definitely looks a "go". I even tested it with autogen a notch up at both 'dense' and it didn't deteriorate much, and with MT6 traffic slider back up to 55% it's still not much down, though I'll normally use 30-40% along with UT2. No time for flying at present though! That'll need to wait will I'm back from holiday. Pete
  8. I must be in deep trouble then. I've never invented a different name. Yes, 4.949k was released on Sunday. Pete
  9. I know, but your name? What's in a name? Pete
  10. Yes, I'm getting better performance EXCEPT in the circumstance I described: Heathrow with heavy (ie realistic) traffic and weather. I've always noted from your own and other reporters on P3D's excellent performance that you have either zero traffic or very low settings. I'm afraid that is not an option for what I want from the simulator. I'm not really interested in add-on aircraft such as the PMDG 777. I use Prosim's own 738 which has no cockpit, no gauges, nothing to distract from the outside view on screen. I did a clean install for 364.43 and that one was awful -- that was the latest one at the time and was the reason for me going back to 361, which fixed stutters and the awful ~1 sec hesitations. I'm reluctant to try any other 364.xx release at present. When I get back from my imminent trip, in mid April, I may see what's on offer then. 1. Find a way to operate your display at 30Hz Did that. No difference but looked worse. 2. If 1080p then use DSR or SGSS AA 2X with MSAA 2X Tried all those. No difference, except DSR at 2x and 15-33% smoothing makes things look too soft. 3. If MT6 then anything above 40-50% AI traffic will results in unrealistic levels of AI traffic, I use MT6 in combination with UT2. MT6 is turned down, to 30%, but isn't the ful thing anyway, just filling in all the missing airlines from UT2 and provideing the charter and military flights I fly airports I know very well and know what sort of traffic levels I would expect to see, It's good everywhere except in the circumstances I mentioned. It's much better, for instance, than FSX-SE at EGCC, my home airport. I'll be trying other dense airports like Paris De Gaulle and Schiphol when I have more time, but my "benchmark" has always been Heathrow. I've tried no tweaks, and some tweaks recommended here -- mainly AM to keep it off core 0 but still give it 4 cores, one of them HT, and use a new facility in FSUIPC to set the AM of other EXEs to avoid those cores. To do this I enabled HT for the first time since I had this PC, 2.5 years ago. I've also enabled Windows Aero mode for the first time, after someone recommended it here. It did help a little. As I say, and keep saying, it is very good everywhere excepting only in the circumstances i stated. A lot of the time it would far exceed 60 fps if i let it. Pete
  11. I didn't get time for any actual flying, I hope maybe to get one in tomorrow. But we're off on another holiday early the next morning, so ... Tests without actual flying still give me poor performance at Aerosoft Heathrow with decent (realistic) levels of traffic and real weather. And that's with settings turned down so things look almost the same as in FSX-SE, which is definitely faster on my system in those situations. Elsewhere, especially in the countryside, P3D does look better, and performs better too. But I fly A-B in a 738 and most of the countryside gets viewed, cloud layers permitting, from FL200 or above. My main requirement is for good performance on approaches and takeoffs, and decent scenery at and around airports. I don't need good looking cockpits because I have a real one and none on screen, and I don't need shadows, so those are off. The whole screen at 1920 x 1080 is just the outside view. I'll try test flights to and from Heathrow, maybe tomorrow, maybe when I get back. I have both FSX-SE and P3D3.2 set up with identical scenery layers now, and settings to make both of them look pretty good. Pete
  12. It's been reported by many folks on the forum already, myself included, and the answer is that, yes, they are aware of it and it is in hand. There are a lot of fixes pending this year's hoped for and much anticipated release, but there's no known date for it. It'll be released "when ready". Meanwhile, to avoid getting the problem whilst still tuning radios yourself, just be sure to acknowledge quickly. I've assigned a button on my Yoke for this purpose and it is now pretty much automatic for me to do this. with the copilot reading back the instructions too you get the detils a second time and can double check you have them right. On the name thing, I've always been bemused why so many folks want to hide behind invented on-line names. Why is that? I can understand for things which might lead to some sort of insecurity, but a person's name? Makes no sense to me. Pete (aka Pete Dowson, real name).
  13. I think the the bad one I had was .47. Maybe they fixed things in .51, but I for one am not in any hurry to find out! Pete
  14. You can select any number of charts to print in one go. Just select the first with the mouse, when with the mouse over the last, press Ctrl & Shift together, then left click. When you then select print at the bottom it will actually tell you that you are about to print N charts ... Of course to convert to PDF you need a PDF-producing "print" driver to select. Pete
  15. That occurred to me when I tried running P3D3.2 with nVidia "DSR" mode set to 2x and selected the higher resoltion in P3D. Some sort of graphics problem I think. Might be related to video driver. Didn't like DSR mode though. It looked okay, but didn't help with smoothness nor performance as some have suggested. Pete
  16. Yes, that's the way I want it and the way I had it, till I installed the OrbxLibs update and it moved FTX ENGLAND etc to the top with the LIBS as the very highest priority. All the rest remained down where I wanted them, just above the FS Global layers. Pete
  17. There's no FSUIPC version for P3D3.3 yet, because there's no P3D3.3 yet. The current version, from the main download places (www.schiratti.com/dowson and the Support Forum at SimFlight) have both carried the correct version for P3D3.2 since the day it was released, and than on the day after when the hotfix for the subscription account changes. One of those must have been where you got your current version from, so why not check the same places? The link on the purchase page (you said you bought it) also still works correctly and takes you there. Please bookmark these download sites because that is where you should always get FSUIPC updates, not just on a new P3D release either. Only the latest version can be supported in any case. Pete
  18. That's good and okay, but I don't have any Orbx airports. It's moving my OLC ENGLAND, WALES, SCOTLAND and IRELAND scenery group, the ones involved in the hybrid working with GLOBAL. Thanks, yes, I like SceneryConfigEditor for things like this. But I just didn't expect it to happen just because I updated OrbxLibs. It doesn't seem right, and why does it do it? Makes no sense to put LC layers like FSX ENGLAND above my local add-ons. It doesn't do it with FTX Europe LC layers. Pete
  19. Yes, I can use that, though it seems to have only one FTX insertion point for everything even though there are separate batches of layers. And it messes my nice orderly numbering up as it only changes the priority not the section. I use SceneryConfigEditor to move and renumber. That works fine and doesn't take long. My point is that it should NOT damned well move them. I didn't find out till after I loaded up FS and saw what a mess the surroundings to my Aerosoft EGLL were! Pete
  20. Just installed them. Why oh why does their Installer (AND "FTX Central" maybe?) move any FTX local areas to the top priorities of the SCENERY.CFG? Installing the ORBC libs update has moved the 4 FTX England layers above all my add-on airports, and this has wrecked a lot of them! So, every time there's any sort of update, I have to edit the SCENERY.CFG and move the damned FTX layers back down, below all the non-FTX addons, just to get things back to normal. Doesn't anyone else think this is bad? Pete
  21. It is an additional feature in the RUN and RUNIF parameters, yes, but it isn't released yet. I wanted to get the documentation updated first, but I won't have time before I go on holiday next week, so I'll release it for now as an interim update (4.949j) over the weekend. Then the documentation update will only be in the Change notes document included in the Zip. I've extended the number of RUN and RUNIFs it can cope with to 16 each, instead of 8, and the additional parameter is in the form AM=n for the Affinity Mask being set to 'n' (a decimal number), or AM=Xn for the same but given in hexadecimal (which I find clearer to see which cores are enabled). Check for the update (DLL and change notes in the ZIP only) in the Download Links subforum on my Support Forum, maybe Sunday afternoon Pete
  22. I unchecked the Vector layers early in my tests. I'm going to try UTX2.1. Not all layers, just some important ones. My earlier installation with FSX had just FTX Global (the first release) and UTX installed (but not all layers enabled). That was fine. I'd not used FTX Vector at all -- it did badly affect FSX performance too. Pete
  23. I always install with the option to completely remove previous drivers. I'm pretty sure that removes the saved settings. At least they are always reset when I go backto them. Pete
  24. Not so many microstutters, but I still get the longer (1 sec or so) hesitations. They're the only annoying things. But I found the problem See later ... No. 3.2 is the first version I felt I should try on my cockpit system. All previous versions of P3D have only been on my development system for FSUIPC work. Answer to the first -- no, not yet. I'll see about making an new release this weekend. Some other stuff to do in it yet. To the second. Hmm, I've thought about it. Nothing more yet. ------------------------------------------------------------------------------------- Anyway, the ANSWER to my originally posted problem: It was the video driver. I installed the latest from nVidia, 364.xx. My friend Thomas told me that the 364.xx series were bad on his system -- lower frame rates and bad stutters -- and that he'd gone back to 361.43 and it solved all that. So I tried that ... and it made all the difference! More testing to do, but I’m no longer getting the hesitations where I was before, the microstutters are all but gone, the frame rates are much better, and I can even re-enable MyTraffic6 traffic alongside UT2, the way I've always had it in FSX-SE! Still some things to solve, and I'm still not convinced I'll stay with P3D -- the performance with heavy traffic, heavy weather and dense airports is much better in FSX-SE. But I'll try a couple of test flights over the weekend. Pete
×
×
  • Create New...