Jump to content

longbreak754

Registered Users
  • Posts

    1,455
  • Joined

1 Follower

Personal Information

  • Location
    Pontefract, West Yorkshire, UK

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

longbreak754's Achievements

Community Expert

Community Expert (6/7)

  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter Rare
  • First Post Rare

Recent Badges

10

Reputation

  1. Hi Charlie.... Thanks for the heads up.... Been away from the forum for a while and playing catch up on what has been posted....
  2. Hi Ahmed.... When you say 'all of these did not solve my problems' are you just referring to the specific items that you have quoted from my original (and very old) post or have you tried ALL of the processes outlined in the complete thread.... As this is a very old thread and you have not given any details regarding your actual problem I would suggest that you start a new thread with FULL details of your issue(s) so that the community can better respond to help you... Another option would be to use the search option on the threads to find info specific to your issue(s - many have been resolved and there is plenty of info out there.....
  3. I understand your frustration but IMO its not really the fault of VRS...MS updates seem to have knack of breaking things, and for VRS to chase every issue that an MS update creates may be problematic, time consuming and may only be updated when they release new updates.... That said, as I have indicated in my first post, I have mostly only experienced issues with TP after a windows update and having had a look back as some of the more recent issues (last encountered it in Aug 2022) it always seems to happens when a .NET Framework V 3.5 and 4 update has been installed....both are perquisite requirements for TP to work (V3.5 and V4.6.1 to be specific) so it might be worth checking that you have both installed...If you haven't got them or you want to simply reinstall them, you can download 3.5 from HERE and V4 from HERE - remember to download and save the ,exe files and then run the installer using admin rights...install V3.5 first followed by a reboot and then V4...If you already have the versions installed, the new install process will check for what files are there and will only install or replace any missing, corrupt or out of date files...
  4. Without any details of the crash it is hard to provide help.... Look at the Windows event viewer to any errors occurring at the time you try to run FSX. and post the entire entry into the thread - for info an entry will look like this example but obviously with different details.... Faulting application name: couatl.exe, version: 2.0.0.2356, time stamp: 0x52702856 Faulting module name: couatl.exe, version: 2.0.0.2356, time stamp: 0x52702856 Exception code: 0xc0000005 Fault offset: 0x00002956 Faulting process id: 0x1fd8 Faulting application start time: 0x01cf97d662b274dd Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe Report Id: 2cd0a798-03ca-11e4-aaf3-d43d7ee230d0 Another quick check to carryout is for non TacPack related issues that may cause such errors - namely a corrupt flight or logbook entry....do the following checks ONE at a time and in the order given - i.e. do the corrupt flight check and then test FSX.... Corrupt flight - locate the FSX.cfg file located at C:\Users\<AccountName>\AppData\Roaming\Microsoft\FSX (NOTE the AccountName element is the name of the account you log onto your computer with)...Open the file using Notepad and find the SITUATION= entry located in the [UserInterface} section - it will look similar to this example SITUATION=C:\Users\Brian\Documents\Flight Simulator X Files\<Name> - the <name> could be anything or blank depending on what has happened and if you have saved any flight... Simply delete every thing after the = sign so that the entry now reads SITUATIOM= Close the file ensuring that you save the changes and start FSX....FSX will load the default flight (the ultralight over Friday Harbour) - let it run for a minute or so and then exit the flight and close FSX so that new flight related files can be written....restart FSX to see if the problem is resolved.....note that any setting you have changed (such as time weather etc will be reset to the default so will need changing once the problem has been sorted..... Corrupt logbook - NOTE ONLY do this if the corrupt flight procedure doesn't fix the problem - this will lose you any hours you have logged but we maybe able to resolve that once you have tested and resolved the problem.... The logbook entries are stored in a file called logbook.bin located at . "C:\Users\<AccountName>\Documents\Flight Simulator X Files"... Rename the file to logbook.BAK and start FSX - a new .bin file be created...fly a flight for a few mins and then exit the flight and close FSX so the new file is saved - restart FSX to test if the issue has been resolved........
  5. I have this every now and then - it seems to happens most often after a Windows update... A couple of things that usually resolves the issue...the TacPack one is usually the only one required... TacPack - With FSX closed start the TacPack manager (TPM) - if you have not created a desktop icon for it or are not sure where to find the app here's some info..... An entry for the TPM can be found on the Windows Start menu under the Vertical Reality Simulations entry.... TIP to make is easy to access do one of the following - Right click on the TPM link and select the Pin To Start option (this will place a large icon onto right hand icon lists) OR select More>Pint to Taskbar (puts a small icon on your taskbar) OR my preferred option select More>Open File Location - this takes to .exe location...you can then right click on the .exe file, select Send To>Desktop (create shortcut) to place a icon onto your desktop.... I would also advise running TPM with admin rights - this can be set to happen either by Right clicking the icon and selecting the Run as Admin option or if you right click and select properties - this will open a Properties window....on this window select the Advanced button and place a tick in the Run as admin option followed by Ok and then Apply...this will run the app in admin mode every time you click on it... Once the TPM has started you may get a message about FSX running in a unsupported mode - can't remember the exact message as it quite long - and there will be a option to change the mode - do so, close TPM and then try FSX... If the TPM starts with no issues or is the FSX error remains after changing the mode you will need to provide more specific info regarding the issue....however, if you are certain that is is DirectX related I suggest downloading the DirectX Redistributable pack - this include DirectX 9 (versions A, B and C - C is used by FSX), 10 and 11 - it can be found HERE or HERE Click on the download link provided and a standard download option box will appear - DO NOT run the installer from this but select the Save As option and save the file to temp location. To install, right click on the file and select the Run as Administrator option. Allow the Installer to do its thing and once complete reboot using the RESTART option - The reboot is essential to allow the windows registry and important system files to be updated....Note that the install process will only install missing versions and/or replace missing/corrupted/incompatible files of the versions it finds installed....
  6. I don't think the default carrier has such a feature (BTW there are more than one carriers - google the phrase -FSX carrier locations' this will give you info on their locations... I also don't think the carriers that are provide via the TacPack have the function either.... There are a number of freeware carrier addons that add additional carriers (and that TacPack can use) - one of the better ones is AICarriers, a google search should find it but it available here in the library at flightsim (note you may find multiple versions of this app the best to get is the .net version (IIRC the file name for it here at flightsim is AICarrier.net)... There are also some payware stuff out there but whether they offer such functions as moving lifts I don't know....
  7. Hi, As it is a default windows folder it will be there....but it is probably 'hidden'... The easy way to determine this and then change its status is as follows.... 1. Go to C:\Users\ 2. Select the View tab from the menu options at top left of the window 3. Within the Show/Hide options click on the Hidden Items option - this should now display all of the hidden Folder/Files within the folder - they will appear as faded items.. If you wish to make any of the hidden items totally unhidden you can right click on it and select Properties from the resulting menu...at the bottom of the General page under Attributes you will see a item marked Hidden with a tick in a box next to it...click on the box to remove the tick and then click on the Apply button....
  8. Hi, You will find the .cfg file at: C:\Users\\AppData\Roaming\Mircrosoft\FSX The bit is the name of the account you use PC - at the same location you will generally find other default accounts such as one named Default and one named Public... Once you have located the file you can create a shortcut for it to find it more easily - simply RIGHT click on the .cfg file (this will open a list of options), Select Send To > Desktop (Create Shortcut) - this will them place a shortcut to the file on your desktop....
  9. Do you still have the order confirmation emails that VRS sent you when you purchased Tacpack... The email contains your Customer ID, the license ID, the Password that you set during the account set up process (note this will not be the password IF you have subsequently changed it via your account) and if appropriate the product serial number (although IIRC this is only available if you have purchased the VRS F-18E Superbug product)...
  10. longbreak754

    Fs2004

    You will need to install the relevant dedicated traffic files to get them 'flying' again...these files would have been included with the ai model... Traffic files are basically scenery files - they normally have file names that start Traffic and will have a .bgl extension..eg Traffic_.bgl... If you had AI traffic before the re-install you must have had these files installed somewhere...a default install of FS2004 will include a default AI traffic file that uses default aircraft and if you go the location indicated below you should see at least one traffic file - this will be the default FS2004 file... The most common place where most users store them (and often referred to as the default location) is FS2004|Scenery\World\Scenery...however some individuals do store them outside of this location...basically, as they are scenery files they could be stored in ANY scenery folder that is active in FS2004..you will need to figure out where you stored them in your previous install and if you have any backups of that folder OR the copies of the original AI files... If not, then you will need download all of the stuff again...
  11. Hi Max, A not so quick but basic guide regarding scenery installing...I appreciate that it is a long read but adding scenery incorrectly can cause frustrating issues... Basically, scenery is made up of two files classes: Scenery - These have a .bgl extensions and contains the 'layout' of the scenery in question. For example, if an airport scenery it will contain the runway and taxiway layouts, parking spots, buildings and other objects. Texture - These generally have .bmp and .dds extensions and contains 'dedicated' textures for the objects they are 'assigned' to. For example a scenery may have a dedicated terminal building model and its 'assigned' texture will provide the appropriate look of it. Types - there are several types that you need to be aware of... A. Airports - These provide the airport layouts and can be classed as either Basic or Detailed. Basic will only consist of scenery file(s) (mostly just a single file that contains the whole scenery but some may contain multiple files, for example one will have the airport layout and others may contain objects etc) and Detailed will contain both Scenery and Texture files. B. Library Objects - As the name suggests, these are scenery files that provide 'common' objects that can be found in the sim. For example, the default hangers, buildings etc that ship with FSX are such items. There are loads of addons libraries out there, including a few essential common ones that are used in many sceneries. If you don't have the required library installed the scenery will not display properly. A good scenery author will provide a list of any such libraries that he/she has used in the building of any scenery so check for a readme file that should detail those required. C. Landclass and Mesh - The first provide files that alter what you see on the ground when overflying an area and the second alters the lumps and bumps (i.e. the hills, valleys, mountains etc). These are normally separate downloads but SOME airport scenery may include 'corrective' files that cover such areas, most commonly being the inclusion of a landclass folder and associated files. This is important to know because the Landclass folder requires to be handled in a specific way so that the airport scenery shows correctly with the new landclass- see below. Installing Scenery Scenery can be installed inside of FSX, or even outside of FSX and on a different drive, as long as the following criteria is met... 1. Scenery files must go into a Scenery subfolder - i.e. Scenery\ will work but \ will not. 2. Texture files must go into a Texture subfolder - as per 1. above 3. FSX must be aware of the location - i.e. the scenery must be activated as per the link Charlie provided... As to the location - FSX provides simply and easy way to install scenery into a folder that is already activated - namely the default Addon Scenery folder located at ...FSX\Addon Scenery. Simply copy the appropriate files into the appropriate sub folder and that's it. When you run FSX it will recognise the new scenery files (you will see a info box about the scenery database being updated)... Whilst this provided a quick and easy way to install scenery it can quickly get messy as you install more scenery. Whilst most .bgl files will normally have individual names that readily identify the airport by its ICAO or name, some may have the same name (mostly restricted to object .bgls). Likewise, texture files may also share common names. Obviously, the danger here is that you may overwrite a file with the same name thus causing issues for a piece of scenery... A better option is to think about creating a folder system that meets your needs and then install individual sceneries into this... Here are some examples that I use - although I will use the default Addon Scenery folder as the main target to show what I mean I actually install most of my addon scenery outside of FSX... Lets take a situation that you have indicated regarding some scenery that you have already downloaded... 1. Unzip the contents into a temp folder - this will allow you to see what is included in terms of files and determine the best install solution...for example based on your comments you have a scenery that contains both a Scenery folder and a Texture folder. Check the contents of these folders and install using the best scenario that fits the scenery. Basically, the chooses are to create individual folders for each airport, areas, etc that suits your needs but for this example I will use a individual airport based folder... 2. Navigate to the ...FSX\Addon Scenery folder. 3. Create a folder named for the airport - for example EDDK Cologne - and then create two sub folders, one called Scenery and the other Texture 4. Copy the appropriate files (as indicated above) into the appropriate folders. 5. Start FSX and use the info given in the link by Charlie to activate the scenery. In the case of scenery that only contains Scenery files (i.e. no texture files) you could create a folder just to hold them on a regional or country basis - for example Germany... Also note that any scenery that contains both a Scenery and Texture folder when unzipped but has an empty Texture folder there is no need to install the empty folder - it just wastes space and can cause scenery memory leak issues... If a scenery includes dedicated Landclass folder then it is essential that when you activate the scenery that you add the Landcalss folder first followed by the Airport folder so that, when viewed in the FSX Scenery Library settings priority list the landclass folder is BELOW the airport folder...this will ensure that it is loaded into memory before the airport file. A quick note on the priority listing view. When you install new scenery it is automatically placed at the top of the list at P1. Its actually misleading in that, when FSX loads the scenery into memory, the entry at P1 will be the last to be loaded and the entry at the bottom of the list will be loaded first. Likewise if you install any library object related scenery, this must be moved down the priority listing as far as possible to a position between the Default FSX scenery entries and any addons that you have added - this will ensure that ANY addon scenery that utilises the object library will display them correctly... Storing outside of FSX follows the same rules only in a location of your choosing. And of course you can make this folder system as simply or complex to meet your needs... A final word of caution - when you want to delete any scenery that you have added into any other you MUST follow the following procedures (based on the type of deletion and its location) to avoid issues... If the scenery is in a dedicated folder that has be activated for it 1. Start FSX. 2. Go to the Scenery Library settings page. 3. Locate the desired entry and untick its box and then click OK - let the database rebuild. 4. With the desired entry highlight click on the delete area button, click OK and then let the database rebuild. 5. Exit FSX and then navigate to where the scenery is stored and delete it. If the scenery is in a shared activated folder then all that is required is to delete the required files. When FSX is next run it will detect the change and rebuild the database. If you take the time to download and install the suggested scenery config tool you can actually use that to activate scenery without starting FSX and using the FSX settings. It also provides other usefull tools, including notifying you of any issues and the ability to change the priority listing using buttons or editing an entry directly to change its list number.
  12. Hi Max, Its been along time since I last had to do a install but possible reason why no entries were made is because you missed the options to do so during the install process....IIRC there was a option screen during the install that you could select whether these two items were created... Again, WRT the sceneries - as per my earlier post the website where you have downloaded the two sceneries from is dedicated to MSFS 2020 the latest flight sim developed by MS....they are not compatible with FSX...if you view the info page for the Cologne item, about halfway down, you will see that it specifically sates that it is for MSFS 2020...
  13. Hi Max, Further to Charlie's post... Ref the poor graphics FSX Settings try the following things listed below - note that setting everything to 'max' does not automatically mean that you get better visuals...it can actually have a detrimental affect on how the sim runs and displays stuff.. 1. Start FSX 2. Select Settings from the left hand menu 3. Select 'Customise' in the left hand pane 4. On the 'Graphics' tab check and change the following as appropriate 'Device Specific Options' A. 'Device' - when first run FSX will normally pick up what GPUs are available - ensure that FSX is using the dedicated GPU (if you have one fitted) and has not defaulted to using the motherboard fitted GPU (usually an Intel) chip B. 'Target FPS rate' - this normally defaults to unlimited, change to either 20, 25 or 30 - this will ensure a stable system if you only have a on board GPU or if you have a dedicated GPU it will allow for testing to see if the current issue has been resolved and then can be increased in small steps later to find the capability of the GPU if you wish - (tip: with FSX its not about high FPS rates but what gives the most stable performance that avoids 'stutters' as new areas are loaded as the flight progresses) C. 'Full Screen Resolution' - this normally defaults to 1024x768 16 bit (on board GPU) or 1024x768 32 bit (dedicated GPU). Change this to the native 16/32 bit resolution for the monitor being used - Note: FSX can be used in Full Screen or Windowed mode (in game changed by using Alt+Enter to switch modes) some systems give better performance in one mode than the other so that may be worth checking out once you have resolve the issue) D. The other two options are GPU dependent and will need to be set as required - testing is the name of the game here because these option can affect scenery load times and causes stutters etc... 'Global Options' The key entry here is the 'Preview DirectX 10' option. Deselect this if on to see if it makes things better as this can also cause scenery issues... As stated above putting everything at max can cause issues - the other options in the Global Options area can impact performance so a bit of testing will be required to see what suits you - tip hover the mouse cursor over the written title and a description will be displayed in the box at lower left of the tab. 'Aircraft' tab - the two main settings that may cause issues are the two 'shadow' related options under 'Exterior settings'...when selected they may cause scenery issues and/or crashes...at least turn them off to test if it resolves the issue that you have. 'Scenery' tab - all these setting can cause stutters, etc but again the main one that can cause issues is the 'shadow' related option under the 'Scenery Objects' section...action as per the 'Aircraft' tab. Another change you can make that should improve things graphically will require you to edit a specific file...the following details it... FSX.cfg file changes This part involves changing a setting and adding a new one...it requires you to edit the FSX.cfg file which is located at C:\Users\\AppData\Roaming\Microsoft\FSX...Make a copy of the file so that you have a reference file just in case you accidently delete something that you shouldn't... All FSX related .cfg are best edited using Notepad (which is a basic text editor that ships with Windows), opening them in Word or other programs may corrupt the file - word for example adds hidden' function codes that FSX does not recognise. 1. Right click on the file and select 'Open' 2. Under the [Graphics] section locate the following entry: TEXTURE_MAX_LOAD=1024 3. Change the entry to read =4096 4. Directly underneath the TEXTURE_MAX_LOAD entry, add the following statement HIGHMEMFIX=1 WRT the scenery - first, the files you have downloaded from flightsim.to are incompatible with FSX - they are for use with MSFS 2020... Second, adding scenery to FSX can be done in a number of ways and is very dependent on what it is,(e.g. an simple airport, a detailed airport, library object etc), what it contains in the way of files and in some cases, may be reliant on having other scenery installed as a pre-requisite for it to display correctly...I would first suggest sorting out the activation and graphics issue before looking at scenery - feel happy to PM me when you are ready to add some scenery and I can provide with the ins and outs of where to and how best to install such stuff in both default locations and other - purely based on my experience of course which may differ from others views. Likewise with the 'special' setups that you refer to - IMO the current stuff will be fine for your kids (and you) - its gives a functionality that beats using the mouse and should meet the needs of the kids to get enjoyment out of the sim...you can consider other stuff once you know the kids are really interested in simming...
  14. Hi Further to my last...I forgot to mention how best to set the key combos.... With FSX closed start the TacPack Configuration Manager - this can done either via the desktop shortcut if you created one during the install process or via the Start Menu listing - its under the Vertical Reality Simulations entry by default... Once the manager GUI is displayed open the 'Trigger Mapping' option located on the Preference tab (it should default to the pref tab when the GUI opens - if not select it).. Here you can set either a keyboard combo or assign buttons on a joystick... Once you have made your entries click on the File > Save option (located just above Preference tab) to save the changes...You can then exit the Manager, start FSX and test...
  15. Hi, I think the problem is down to you not having mapped any key combinations and/or joystick trigger functions to actually 'fire' the weapons A list of the assigned F-35 default key strokes can be found on pages 9 and 10 of the User manual - this can be found in a folder called 'Docs' located in the F-35A model folder and it covers all operating details for all models. Notably, there is no listing for a dedicated 'fire' combo. It is important to remember that TacPack was originally designed to work with the VRS F-18E Superbug and that it has been 'updated' under license to work with other products - some to accompany dedicated models such as Dino has done with the F-35 and some are 'amateur' mods created by the community to add unofficial (and thus unsupported) functionality to products - for example you can find mods for the Aerosoft F-16 and the JustFlight Tornado GR1 products... The Superbug uses the following default key combos for firing the weapons and I have adapted my FSX keyboard settings to use them with the F-35... SHIFT+CTRL+V GUN TRIGGER - Note: In AA MM, fires currently selected weapon and in AS MM, designated ground target via HMD) SHIFT+CTRL+C BOMB PICKLE - (Note: In AS MM, releases currently selected weapon and in AA MM, it has no function).
×
×
  • Create New...