Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

Adamski_NZ

members
  • Content Count

    119
  • Joined

  • Last visited

Everything posted by Adamski_NZ

  1. OK - I see your problem. Aerosoft changed the way the various models are called via the aircraft.cfg, so *older* liveries won't work without a little bit of work. You may need to check the the forums here for more precise information. There are two things that need to be addressed: 1) From memory, I think the "model=" line needs to point to a specific model: just "model=[blank]" may not work. Either that, or the model entry is pointing to a model that's no longer there (in the new version). 2) More likely, the cause is this: Check the textures.cfg file (in each livery) is the same as any of the ones that do work. Your problematic liveries are probably not finding the common/default textures. I do remember a few posts about exactly this in these forums (which I think Matthias himself answered), so do a search . I seem to remember his post explaining which models default to which. Many of the livery authors have updated their archives to suit the newer version(s), but there'll be quite a few liveries out there that haven't been modified, I expect. Adam.
  2. This is a fairly common procedure - which many of us old-timers do so automatically that we don't realise it could be a stumbling block to some. In your aircraft.cfg, each livery will have an entry - starting with [fltsim.0]. These all need to be sequential, so the next block of values for the next aircraft should start with [fltsim.1] ... and so on. If you already have a fair few liveries added, then your new [fltsim.x] entry should be the last entry plus one. It sounds to me like you may have a mistake in the numbering <?>. If there's a mistake, the sim processes all the entries up to the mistake - so you still get the original ones showing. Adam.
  3. Wow - these topics get closed off super-quick here! Just to say thanks for rushing through the compatibility update so quickly after all. No issues on my system šŸ™‚ The problem with utilities of this nature is that we tend to build our simming procedures around them. I do a fair amount of beta-testing, so the ability to switch configs quickly/easily is absolutely crucial. Thanks again! Adam.
  4. Hi Peter .... Sorry to be so late in replying. I've been doing a series of tests - with and without Primocache running. Basically, when Primocache is running, many of the Simstarter settings don't appear to "stick". I imagine this may be because the config files are being cached and edits aren't being applied correctly. I've disabled Primocache for now - at least for all my P3D sessions! Adam. P.S. Unless there are hundreds of P3D+Primocache users out there, I think you'd be quite safe to mark this "Closed" - even if, technically, it hasn't been "Solved".
  5. I've been experiencing some odd behaviour in SIMstarter lately and wondered whether the cacheing that I have on my system C:\ drive may be interfering - as many of P3D's (and maybe SIMstarter's <?>) files are stored there. Primocache is an excellent little utility - and helps speed up my general PC operations as my main system drive is a standard/old HDD. Any clues, anyone? Adam.
  6. Here's a couple of quotes from Prepar3D_Download_and_Install_Instructions_v4.pdf (I hope LM or Aerosoft don't mind this being quoted here). ===================================================================== You can also update by doing a complete uninstall and reinstall of the entire application, but often that is not necessary or desired. ===================================================================== [However .... Aerosoft recommend a full reinstall ...] Uninstalling/Reinstalling Prepar3D v4 NOTE: This section only applies to those uninstalling/reinstalling Prepar3D v4. Uninstalling/reinstalling the Prepar3D should work as designed, but following these steps will help guarantee success. 1. You will want to back up any additional content or add-ons (models, scenery, configurations, etc.) before uninstalling Prepar3D. To begin uninstalling the Prepar3D application, go to your Start Menu, select Control Panel, and open Programs and Features. Select Prepar3D v4* from the list of programs and click the Uninstall button on the menu bar (the asterisk (*) is the Prepar3D v4 variant (Academic, Professional, or Professional Plus)). Follow the on screen prompts to uninstall Prepar3D. If you are simply looking to restore your Prepar3D installation, select the Repair option. That will fix the majority of user issues. 2. While the uninstaller removes all files that are created by the installer, it does not completely remove content that was generated during program execution. To completely uninstall Prepar3D, you must manually delete folders and files that are created during runtime. Please be sure to back up any changes you have made to any of the files in the folders. Now, please manually delete the following folders: * C:\Program Files\Lockheed Martin\Prepar3D v4 (or the modified install location) * %PROGRAMDATA%\Lockheed Martin\Prepar3D v4 * %LOCALAPPDATA%\Lockheed Martin\Prepar3D v4 * %APPDATA%\Lockheed Martin\Prepar3D v4 * %USERPROFILE%\Documents\Prepar3D v4 Files 3. Now you should restart your computer. After your computer has restarted, if you would like to reinstall, simply follow the Installing Prepar3D v4 section.
  7. Mathijs ... without going down the well-known tweaks "black art" path, are there any *specific* cfg tweaks that you think are the most common culprits? I realise this can be a messy discussion - as everyone runs their system differently (for all sorts of reasons) - but if there any really obviously "dangerous" tweaks that affect the A318/A319 in particular, I'd be keen to know of them. Of course, I understand some tweaks can affect performance in general and that the Airbus gets the blame as it may often be "the straw that broke the camel's back" ... but again - any help as to what to avoid would be most welcome.
  8. For me at least, it happens whenever ActiveSky (or OPUS) updates/injects a weather update. Unfortunately, that often coincides with some cloud redrawing - so it's a bit of a "double whammy" on the system. In other aircraft, the sim stutters - or even (at worst) pauses for a fraction - but manages to pick up the thread and carry on. I appreciate the AS Airbus A/P is particularly sensitive to dropped frames, but I'm not sure what I (as a user) can do about it. My totally unscientific/gut feeling is that I wish there was a way of persuading Simconnect to somehow spread its data injection over a longer period of time. I'm *way* out of my depth though Adam. EDIT: I'll try some [more] comparisons, but I think OPUS is slightly better in that respect, as I think it staggers the data send a little so as not to have a large "jump" in visibility or clouds. I may ask Stephen in the OPUS forums if that is indeed the case.
  9. Great to see you putting stuff up here, Matt ... seeing as OzX is still down <?>. Adam.
  10. Rui - that sounds to me like the model isn't set correctly. It's an old repaint, so the chances are that the [FLTSIM.X] info is out of date. More than likely the "model=" will be blank. I think it's a CFM variant, so try DAIBA (or SHARKLET). Here's a pic of mine (installed manually): For older liveries, there are a few steps you'll need to do: 1) Modify the aircraft.cfg entry. Here's my modified version: [FLTSIM.XX] title = Airbus A319CFM TAP Portugal CS-TTA sim = A319 model = DAIBA panel = sound = texture = TAPPortugal_CSTTA kb_checklists = AirbusA321_check kb_reference = AirbusA321_ref atc_id = CS-TTA atc_airline = Air Portugal atc_flight_number = 1000 ui_manufacturer = Airbus ui_type = A319-111 CFM ui_variation = TAP Portugal ui_typerole = Commercial Airliner ui_createdby = Aerosoft atc_parking_types = GATE, RAMP atc_parking_codes = TAP description = "Airbus A318/A319 - A319 CFM / A319-111 TAP Portugal CS-TTA." 2) From the Aerosoft A318-A319 Professional Base\Tex_FB_VC folder, copy: AIRBUSX_VC_PREPARV4_MAINPANEL_C.dds AIRBUSX_VC_PREPARV4_MAINPANEL_L.dds ... and paste them into the TAPPortugal_CSTTA folder. You can delete the old V2 one. 3) Edit the texture.cfg (in the TAPPortugal_CSTTA folder) to read: [fltsim] fallback.1=..\..\Aerosoft A318-A319 Professional Base\Tex_FB_VC fallback.2=..\..\Aerosoft A318-A319 Professional Base\Tex_FB_A31X That's it! BTW - that's roughly the procedure you'll need to do for many of the "older" liveries. Adam. UPDATE: Do a search - I think Mathijs has posted somewhere in these forums (!) what the models should default to when they're blank.
  11. Thanks, Mathijs. Just to be double, triple sure - that means uninstalling the *main* P3D application as well (the one I did *not* do? Thanks! Sorry - yes - I should have mentioned that. I always do that as a matter of course anyway (old habits die hard)! Adam.
  12. I'd love to know whether this counts as a "clean install" (as recommended by Aerosoft): 1) I removed all three components (Client, Content and Scenery) via the Windows Control Panel. 2) I then installed the three (latest) separate components from LM. 3) Cleared the shaders *cache*. I did *not* remove/reinstall the main P3D application. Are there any other files/folders that need to be deleted? Please advise! Adam.
  13. That's great news, Mathijs. I couldn't help smiling when I read the last part!
  14. Could I please ask for further clarification on this, as this often causes users some confusion? 1) By shader folders - do you mean the shaders CACHE ... or the shaders folder in P3D root? 2) What do you mean by a "full clean installation"? A complete wipe of P3D and all associated add-ons and content? Thanks!
  15. Thanks, Mathijs! I think the strategy for this is already mentioned elsewhere, but could you [please] remind us again what the recommended/correct procedure is for ensuring the cleanest v4.3 update (short of a complete reinstall)? A link will do There may be a people in this topic that have got some leftover "undesirables" that may be affecting this issue.
  16. I promised Stefan to take a bit of a back seat, publicly ... please check your PM! Lovely pic, BTW!
  17. Stefan - I think we're still at cross-purposes. PTA doesn't work like Reshade. Have you tried/used PTA at all? This is what I use it for: As I said, I'm all for more "realism" and not cheap saturation or contrast tweaks. Anyway - this is all besides the point. The Aerosoft models could work perfectly with PTA ... it's honestly just because the lighting parameters aren't applied uniformly to all the textures ... that's all!! If there was something basically wrong with the P3D/PTA combination then NONE of my aircraft add-ons would work properly. Please, Stefan - it's just those "odd" textures. It appears we're getting into percentages and semantics now. Do you not see what I'm driving at? For goodness sake, I worked with on the Aerosoft FSX A320 (PNF sound files etc.) - I'm on your side!!!
  18. Stefan, with the greatest respect, I'm sorry I just don't buy this. Are you telling me the P3D shaders are correct???? You must be joking!!! They contain all sorts of legacy code inherited from FSX. So ... you are saying that just because the parameters aren't applied consistently across the aircraft model that it's somehow the fault of "unsupported 3rd party mods"?
  19. I just knew I'd get this reaction! I repeat - *I'm not asking Aerosoft to support some whacky 3rd party black magic*. All PTA does is well within the P3D SDK. It simply allows you to change certain values within existing shader fx code. *BUT* my point really is that we're only talking about minor anomalies/inconsistencies within the materials lighting parameters that have slipped through unnoticed. No-one's asking any recoding to support features beyond core P3D. Basically - if you look at the surface lighting for the fuselage, it should be the same as the wings (or vice-versa) - it's as simple as that. I think something similar has already been reported (and acknowledged) in an Octopus An-2 thread, started by Matt Levi (Jeansy) I think. If I may take your last comment and turn it around .... we should all be grateful for 3rd party developers that shore up shortfalls to what is really a very old product - and forces LM keep to improving it. Sorry, Stefan -- I totally missed your "physical based shading" comment in my haste to answer. Could you elaborate? It sounds like it could be a solution.
  20. One of the things I like about PTA is the ability to tweak the shaders to fine tune the lighting on both the exterior and VC interior of an aircraft. It allows me to set decent gamma/brightness/contrast for the clouds and terrain then adjust the aircraft lighting to compensate. 99.9% of my P3D aircraft support these lighting tweaks, but every now and again I come across an add-on with what looks like an inconsistency in lighting parameters on certain sections of the model. I get this with the A318/A319 as well as the Aerosoft/Octopus An-2. It looks like the wings have the wrong parameters. Please don't tell me off for using esoteric hacks/tweaks ... I use PTA very carefully - it's a very useful tool for correcting what I believe to be deficiences in P3D lighting functions. I do NOT use it to produce "cheesy" or unrealistic lighting effects. Here it is in action: I'm not expecting Aerosoft to support unorthodox modifications or tweaks. All that is happening here is that PTA is showing up inconsistencies that would not be otherwise apparent - nothing more. These are relatively easy to correct, should the model(s) be recompiled at some stage. I hope these little niggles can be fixed at some stage, as the Aerosoft Airbus exterior model is highly detailed and a joy to look at! Adam.
  21. After some further testing, it appears that I can't get saved Airbus scenarios to initialise the radios properly (no matter how I create or load them). I have to create a default scenario with all the settings (location, flight plan etc.) with a default P3D aircraft, then launch it. I then switch to the Airbus manually. Not a huge deal Adam.
  22. Mathijs ... daft old me ... I found it's the old "Start with a P3D default aircraft" thing again - that usually initialises P3D properly. I think it's recommended for any "complex" aircraft and I should have known better (or not been lazy). I was starting clean/straight in to saved scenario from the startup screen without having pre-loaded a default aircraft. If I load the Maule then either go to the A319 (or load the scenario), all is well. Is this the correct/recommended method for starting up the A/S Airbuses? I did a quick scan of the docs to see what the recommended procedure was but couldn't see it mentioned. Adam.
  23. Please don't laugh at me: I know P3D (and FSX) ATC is an absolute joke ... but I was stress-testing my system to see if simultaneous wav file replay may be a problem (I don't think it is) so I "tuned in" to P3D ATC. The first prompt ("Request Clearance") worked fine ... but after that, it appears that I can tune and *receive/listen to* all the other frequencies (ATIS, Ground, Tower etc.), but it's as if "transmit" is disabled. I get no further ATC prompts or selections - though I can hear (and see the text) for communication between ATC and other aircraft. I twiddled and fiddled everything I could think of to put the radio(s) into transmit mode, but no luck. Hardly earth-shattering in terms of importance, but I wonder whether: 1. Other people get the same issue. 2. Whether it's even worth fixing (LOL!). This was with the A319 - and I tried with and without the F/O doing the checklist, in case he flipped a switch I'd missed. Adam.
×
×
  • Create New...