S77th-ReOrdain

I didn't, I cheated. I made two versions in ModMan with the single Road_textures_black_v2.cdds file. The only difference between the two are the readme(s) crediting you, and instructions to modify either the graphics.cfg in FC2, or the graphics_bs.cfg in Blackshark. Because added lines in those two files don't affect gameplay, frames, etc., and servers don't integrity check them, I simply copy the reference file locations and leave them there. No conflicts with other mods this way, but also, FC2 and BS don't bother with meinit or the graphics files in the way the previous incarnations did, therefore, it's all good :thumbup:. I suppose, if one wanted to, one could also include the necessary graphic.cfg file with either version. Shoot me a PM if you want them emailed.

Great job, as usual, Mustang. The atmosphere improvements of roads, buildings, fences, etc., make the low flying experience even better. Personal comment about adding road markings to all roads: If all markings are identical, all roads will look like two lane, one way streets. My personal preference is to have a distinction between roads and highways. I made a ModMan compatible addon of the current version for FC2 and Blackshark as v2.0 does the trick for me. Anyway, I'll continue to use some version of this mod, as it is a welcomed improvement. Thanks for your hard work.

Don't forget that L-Shift and R-Shift function independently. Commands programmed with R-Shift will not work if just using Shift (typically Left) + the keystroke.

Not familiar with the software you're using, but the programming looks correct. I would suggest you try alternate keystroke programming using the in game options for commands that don't seem to work. In my case, many of the commands using the "right" modifiers (R-ctrl, R-shift, etc.) didn't work either. Since DCS allows multiple commands for the same action, I backed all the "right" modifiers up by using the same keystroke with the "left" modifier, if it wasn't being used by something else. Give it a try.

Confirmed.

Changing the UseDefaultSnapViews = value (line 51 in view.lua) should solve the client view issue. I believe, but not sure, the mission designer designer needs to have the "global" settings box unchecked to prevent that option from being overridden. I too use snapviews frequently, I noticed right away that the server was forcing my views, and an attempt to set your own in game, doesn't work. Obviously, I prefer my own views to see the instruments that my failing eyesight can't see when zoomed out. Zoom function works, but it takes longer to zoom than it does to snap. Tenths of seconds often matter. All that said, adapting and overcoming has its merits. Either way, 104th is doing good things for the community and their server(s) offer great online flying. Keep up the good work.

I'll see you in the skies then, homie.

Get it here.

Absolutely correct Distiler. I was using the pre-Skypat self modified version. Making the switch now.

My bad. I meant to ask about the S-8OFPs. Thanks for the reference. That's the answer. I've got the SimMod A-10 installed. It's the S-8OFPs that don't show up with the SimMod A-10 installed. You are correct that the S-8KOMs are visible.

S-8KOM2's Invisible? Is it me, or do the S-8KOM2 rockets not show up on the pylons in game?

According to the manual (pg. 221), Attack my Target directs your flight/wingman to attack any aircraft attempting to attack you Seems a bit like the "Cover Me" command. Sounds like the difference is "cover me" directs flight/wingmen to attack a bandit that already has you targeted (locked?). Perhaps "Attack my enemy" directs flight/wingmen to engage any "potential" airborne threat. Need to test to compare AI reaction.

Nice work Ryke, Thanks for honoring my well placed faith in you.:thumbup:

Running the lastest driver from ATI (Catalyst 10.3). You can turn your shadows down from in game options/system/graphics/shadows menu (Full, All Planar, Active Planar), but you can't turn them off from there. Looks like you can remove shadows from within your graphics.cfg file (~line 145), or tweek the density (~line 400). I haven't had the need to adjust those myself though, so I can't comment on what your results may be.

Case, Check out the view.lua file in \config\view\ . . Change lines 50 and 51 to false. This will disable snapviewsdefault.lua and allow saving of custom views in the cockpit without manually adjusting the numbers in the file itself. Saves a lot of time, you get the exact view you want (as best you can), and you only have to worry about snapviews.lua if you do want to make further manual adjustments.

Same card, Vista 64. Try turning off Catalyst AI and Triple buffering if you have it on. I also have the Multi-Sample AA turned all the way down. Getting similar framerates or slightly higher than your observations. No graphic anomalies or artifacts to report. Looking sweet.

Flaming Cliffs 2.0: Smoldering Boulders

Flaming Cliffs 2.0: The Unclickable

Hey jessi1, if you're on the ramp, it's actually easier to do it as described in section 7-50 "Editing a waypoints location". That way you can move waypoints around without unloading the current plan. Keep in mind that when you change waypoints in ABRIS, it does not effect the route that's stored in the PVI-800. You'd have to edit those coordinates manually to sync.

What do you want each pedal to do? I've got one I could send you that uses right foot for wheel brakes and left foot for TrackIR precision. PM me.

Have you tried checking for the x52 in Black Shark options if the SST software is not installed? Not sure which OS you're running, but typically if the x52 is functioning properly, you can see the little Saitek profiling icon in your taskbar on the bottom right with the rest of your running apps (Win98, XP, Vista - not sure about W7). If you see that app, right click it and select control panel. This will show you your HOTAS button assignment. Optionally, (on Vista and XP) you can go to control panel - game controllers and your Saitek x52 should be listed. If so, select it and click properties to show the joystick control panel. If it isn't in either of those places, there was probably an install issue. In my case, swapping or changing USB ports after programming causes hardware recognition issues. If not properly recognized, the HOTAS icon doesn't show in taskmanager and is not available for programming or in game (as you described). Saitek's SST programming, although seemingly complex, allows a great deal of flexibility. Check out the SST programming manual included with the software. The only problems I've experienced with this software has occured when I've used an outdated version. Hopefully, you already knew this, but just in case, there are (2) software programs to install. One is the drivers for the HOTAS, the other is for SST Programing (32 or 64bit). Good luck.

If that doesn't work, try one of these solutions. http://forums.eagle.ru/showpost.php?p=782125&postcount=3 http://forums.eagle.ru/showthread.php?t=49168&page=2

Thanks for sharing :thumbup:.

Thanks Frazer, these sounds are very good.

You can lower it prior to starting the game by starting VLC and adjusting the volume, or the way I do it by alt-tab method. Basically, you have to open the VLC app first and then you can manipulate the volume. Another trick is to setup shortcuts on your HOTAS or whatever controller you use. Right Control - up arrow (vol. up), Right Control - down arrow (vol. down). So it is possible to manipulate volume in the background by alt-tabbing and then using these shortcuts. Keep in mind, you will temporarily lose control of your aircraft when alt-tabbing.