Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

rhk1138

Frozen-Inactivity
  • Joined

  • Last visited

  1. Appreciate your help, got it figured out. As it turns out I just wasn't saving it right when I converted it back to the extended bitmap using DXTBmp. I thought I had been doing it the same way all along, but I suppose I was mistaken. Thanks Again.
  2. No luck, followed the exact same procedure I did with the day textures. I still can't figure out why my modded overhead panel texture only shows when the landing lights are switched on, my mods become very apparent at this point. Even the part of the texture that I didn't mod still doesn't show until the landing lights are on. If I load the replacement VC texture without any mod then it shows up just fine, with all the other modded lights. Very weird, very puzzling.
  3. Hello Everyone, I will try and explain this as precisely and quickly as possible. I am flying the Overland 737-700 for FS9. I am using a Southwest Airlines add-on livery. I downloaded a set of reworked virtual cockpit textures. Using the DXTBmp program, I loaded the files into Photoshop to do some further editing. I was able to edit the replacement textures with no problem, I could save them as a .bmp directly from Photoshop and they would load no problem. Once those were to my liking I downloaded a set of replacement night textures for the VC. There was only one that I wanted to edit, to coincide with changes I'd made to the VC texture. I used the same process, loaded it into Photoshop and then saved it to the texture folder replacing the original 737ngvc4_l file (as a 24 bit bitmap this time). I start FS and reset the time so that I can test the replacement night textures. Every other replacement VC night texture shows up except for the one I made changes to. I don't really find this to be odd as I probably overlooked a certain step during save night textures except that when I flipped on the landing lights, my edited texture shows. I'm really at a loss as to how this could be happening. I tried different methods of saving or converting the file but nothing seems to make a difference, other than the texture not showing at all in some cases. If anybody has any insight I'd greatly appreciate it. Thanks, Rob
  4. Really appreciate the help, it seems as though I was on something of snipe hunt. Just a matter now of finding out which previous set up I was obviously more satisfied with. Made the suggested cfg tweaks and lowered my visibility settings to something a bit more realistic, looking better. Not sure why I have always been inclined to leave the vis slider set to the max. One question: Until now I have been using an unregistered copy of FSUIPC, but am interested in changing the settings that you recommended Word Not Allowed. Will the effects be worthwhile enough to register, or would I be better off leaving that alone?Thanks again, Rob
  5. Hi Guys, @Garygb, thanks for all the links, I haven't had time to read through them yet but figured I would post a couple of screenshots before returning to work. The effect with the ocean is the same on flat land if I have the GEPro textures installed (which I don't currently after the last reinstall), they just come to an end. The water textures are some that I pulled from the library and are my personal preference. Like I said, I don't recall having these issues in the past. I will read through the links you posted tonight for some insight, but at least you have an idea of what I'm experiencing.@tgibson, I am running in 32.Thanks guys for the help, Rob
  6. Hi Everyone, I've looked around on the web, and the forums to see if there is a solution to my particular issue, but haven't had too much luck. I recently made the move to Windows 7 x64 Home Edition (from Vista 64) and did a clean install, i.e. not the upgrade. I installed FS9, ran the 9.1 update, ran fs9 and then made some changes to the fs9.cfg file to fix the blurred textures. These changes in particular are the ones I have made and am now having issues with:[TERRAIN]TERRAIN_ERROR_FACTOR=100.000000TERRAIN_MIN_DEM_AREA=10.000000TERRAIN_MAX_DEM_AREA=100.000000TERRAIN_MAX_VERTEX_LEVEL=19TERRAIN_TEXTURE_SIZE_EXP=8TERRAIN_AUTOGEN_DENSITY=4TERRAIN_USE_GRADIENT_MAP=1TERRAIN_EXTENDED_TEXTURES=1TERRAIN_DEFAULT_RADIUS=9.500000TERRAIN_EXTENDED_RADIUS=4.500000TERRAIN_EXTENDED_LEVELS=4[sCENERY]I have made these changes in the past and have had good results, though I still play with them from time to time as there seems to be differing opinions on the values to enter. This time however, these changes do not seem to have any effect. Textures are still blurred and since I have installed new water textures, there is a distinct line where the new textures end, noticeable from a height of about 8000ft and up. The odd thing is, I change the pan rate as well, and this works. The pan rate through the VC reflects the changes made to the cfg file but there is no difference in the textures. I have read in different places that certain values will not be recognized, but like I said I have used these before with results. I've tried reinstalling fs9, to a couple of different drives, with and without the no cd patch to see if there is a chance that there is some quirk in these various setups that is causing an issue. The only other thing I could think of would be that in the past I have used nhancer and I currently use nvidiaInpector to handle the AA, etc. I can't imagine though that this would be the source of any issues. Any help is greatly appreciated as I am starting to get quite frustrated with the whole thing. Thanks very much, Rob

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.