Adamski_NZ

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.

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.

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.

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.

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.

OK ... understood ... many thanks.

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.

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.

That's great news, Mathijs. I couldn't help smiling when I read the last part!

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!

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.

Thanks! Another familiar face, I see!!!

I promised Stefan to take a bit of a back seat, publicly ... please check your PM! Lovely pic, BTW!

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!!!