espiral Posted November 12, 2010 Report Share Posted November 12, 2010 Curioseando por ahí para tratar de encontrar algún "driver" para el "TrackIr" que funcione en Linux, me he encontrado (en la página de "wine": wine con una extensa explicación del "conf.ini" del IL-2, además de cómo añadir nuestra propia música y alguna otra curiosidad: HOWTO : Tweaking Il2 : extra details If your computer is powerful enough to run il2 on max. details, you can try to enable some extra effects: 1. Set graphics quality to maximum settings ingame 2. In your games directory (e.g.: "~/.wine/drive_c/Program Files/Ubisoft/IL-2 Sturmovik 1946") you can find a file named "conf.ini". Here you can change some details. This also is described in the manual: 3. Go to "[Render_OpenGL]" and change "Forest = 2" to "Forest = 3" to enable 3D-trees and higher tree resolution 4. Go to "[Render_OpenGL]" and change "Water = x" to one of these values: 0 (normal water), 1 (some reflections, shadows), 2 (reflections, shadows, water-dependent wave types), 3 (ultra-quality using shader 3.0) If your airports flicker, change the following values too: 1. "PolygonOffsetFactor=-0.15" 2. "PolygonOffsetUnits=-3.0" HOWTO : Add own music To add own music to il2, you'll have to convert and copy them: The manual says: "You can add music files at your own discretion via Samples/Music/Directory. The music should be in Windows WAVE-file, MPEG 1.3 format. The files for playback are chosen at random." Use any audio-converter to do so, e.g. "ffmpeg": "ffmpeg -acodec mp3 -i somefile.mp3 outfile.wav" Now copy the wav-file into your gamedir: (e.g.: "~/.wine/drive_c/Program Files/Ubisoft/IL-2 Sturmovik 1946/samples/Music/") 1. Folder "Crash": (any filename) played on crash 2. Folder "InFlight": (any filename) played inflight 3. Folder "Takeoff": (any filename) played on takeoff / after landing 4. Folder "Intro": ("intro.wav") played as intro 5. Folder "Menu": (".wav") played in menus (depends on nation selected) If you only hear first some "clickers" or only the first seconds, you didn't convert to "mpeg x layer 3" HOWTO : No sound? If you don't get audio output in il2, first check others apps, esp. wine-apps. Also check ingame settings. If this was not the problem, maybe you need to edit your "conf.ini" file (can be found in your gamedir): Find section "[sound]": Set "SoundUse=1 ", Set "Speakers=2" (or more) Try not to use other audio applications when running il2! Complete IL2 config.ini Explained copy, paste to text file and save for easy reference [il2] this describes game title=Il2-Sturmovik Forgotten Battles hotkeys=HotKey game this determines whether the game uses hotkeys that are assigned in control section of hardware section of game setup [window] this describes how windows displays the game on screen width=1024 resolution width in pixels set in display properties settings tab in windows height=768 resolution height in pixels set in display properties settings tab in windows LCD native resolution not included as an option in FB/AEP/PF Enter your screen values here and Save and start your game.... (if you later open the IL-2 Setup and close it by clicking OK it will change the resolution to 640x480 16bit, unless you change it to something else via this IL-2 Setup.) You will need the following values as well change SaveAspect=0 ChangeScreenRes=1 EnableResize=0 ColourBits=32 resolution colour set in display properties settings tab in windows. Can be 16 or 32 DepthBits=24 Z buffer usage can be 16 or 24 StencilBits=0 Set in driver section of Il2FB hardware setup. Can be 0 or 8 All the above deal with image quality. The higher the numbers for width and height then the more pixels will be used in the same area therefore the image will be more detailed. The larger the number of bits then the more detail there is per pixel so better image quality ChangeScreenRes=1 allows the screen resolution to be changed in game. Can be 0 or 1 FullScreen=1 forces display to be full screen and not in a window. Can be 0 or 1 DrawIfNotFocused=0 setting to 1 allows watching the IL2 window in the background, while Alt-Tabbing out of the game. Quite useful for playing co-ops - if you crash and wait for the next mission to start, you can put IL-2 in the background and keep an eye on the mission progress, but at the same time start ranting about "my fav plane is porked" on the forums. EnableResize=0 Enables user to change window size. can be 0 or 1 must be 0 to allow lcds to fill screen EnableClose=1 SaveAspect=1 Forces 4:3 picture aspect. Can be 0 or 1 Change SaveAspect=1 to SaveAspect=0 will remove some small black bars at the top and bottom of the screen you get without it on lcds Use3Renders=0 Allows use of up to 3 screens. Can be 0 or 1 [GLPROVIDER] This section comments on what 3D drivers you are using GL=Opengl32.dll It will either be openGL or Direct X depending on what you picked during setup. [GLPROVIDERS] Changed by running setup from start-programs-ubi-il2sturmovich-setup Open GL=Opengl32.dll DirectX=dx8wrap.dll [NET] This section deals with your settings for connecting to the internet speed=25000 for multiplayer games. routeChannels=0 serverChannels=31 serverchannels indicates max allowable number of players localPort=21000 port 21000 this will have to be enabled in your firewall to allow you to connect to web remotePort=21000 SkinDownload=1 SkinDownload= 1 allows skins to be used. 0 does not serverName= Name of own server serverDescription= Own description of server remoteHost= IP Internet address of the remote computer that one connects to localHost= IP internet address of the local computer that one connects to socksHost= checkServerTimeSpeed=1 Compares master clock of server and client checkClientTimeSpeed=0 checkTimeSpeedDifferense=0.05 Maximum difference of the master clock permitted (Maximum is 5%) Note spelling of differense is correct checkTimeSpeedInterval=5 Maximum difference of the master clock permitted (Maximum is seconds) checkruntime= In order to set the client-side verification parameters you will need to manually edit here checkRuntime=0-no check is made (default); checkRuntime=1-quick check; checkRuntime=2-comprehensive check. [MaxLag] farMaxLagTime=10.0 nearMaxLagTime=2.0 cheaterWarningDelay=5.0 Time until you are cheating warning cheaterWarningNum=-1 Number of warnings until player is kicked. If at -1 autokick is deactivated. [chat] region=(dx=0.6925,dy=0.071666665,x=0.0,y=0.0) Position and size of chat window msg0 = Contents of the message "0" adr0=ALL Receiver of the message "0" (all) msg1 = Contents of the message "1" adr1=MY ARMY Receiver of the message "1" (own side) autoLogDetail = On-Line Stat Messages The server hosting an on-line game may set the ‘level of detail’ of the server auto-generated stat messages. The level is set in the conf.ini file in the Il-2 folder, in section [chat], in the autoLogDetail key. Ex.: [chat] autoLogDetail = 3 You can set the key to the following options: 0 - disables all stat messages. 1 - only player-vs-player kill messages are displayed. 2 - displays player-vs-player, and AI-vs-player kill messages. 3 - a lot of chit-chatting. [game] In game settings Arcade=0 when at 1 changes display to show balloon speech from aircraft and arrow bullet strikes etc. Can be 1 or 0 HighGore=0 when at 1 changes display to show gore effects on a limited number of planes Can be 1 or 0 This feature has been dsabled in recent versions of the game mapPadX=0.6689453 mapPadX and mapPadY are position coordinates for the inflight map, they're nothing to do with padlock. They are a measure in fractions of full screen width from left of screen (mapPadX) and height from the top of the screen (mapPadY) for the top left corner of the map. mapPadY=-0.046875 viewSet=32 Snap view -Even number. Pan view Odd number. Intro=0 when at 1 runs intro movie at game launch NoSubTitles=0 (Subtitles for pilots' voices; 1 = none, 0 = all) At top of screen SubTitlesLines=3 Number of lines for sub-titles NoChatter=0 (Radio chatter; 1 = none, 0 = all) To hear pilots voices NoHudLog=0 HUD text messages and warnings; 1 = none, 0 = all At side of screen NoLensFlare=0 (Lens flare effects; 1 = none, 0 = all) iconTypes=3 allows user to change what is displayed in icons when enabled these are available from key bind in control section. Icon Settings: You can change your icon types and distances by typing these variables in console in game the command syntax is: mp_dotrange [FRIENDLY|FOE] [DEFAULT] [DOT ] [RANGE ] [TYPE ] [iD ] [NAME ] FRIENDLY or FOE keywords define which party the following parameters apply to the aircraft of the viewer's army, or the aircraft of the hostile armies. The following keys define the distance at which the appropriate icon is enabled: COLOR: The distance at which icons take the color of the inbound plane’s army. Icons farther away will be drawn in grey. DOT: The distance at which the “dot†plane marker becomes visible. RANGE: The distance at which the distance measurement appears in the icon. TYPE: The distance at which the airplane model or model family becomes visible. ID: The distance at which the tactical number is visible. NAME: The distance at which the aircraft’s pilot name is visible (if it is driven by a human pilot). mp_dotrange DEFAULT restores the Pacific Fighters predefined icon setup. mp_dotrange run without parameters prints the current icon setup ranges (which may be issued by both client and server). e.g mp_dotrange FRIENDLY COLOR 0.1 DOT 15 RANGE 5 TYPE 0.1 ID 0.1 NAME 2.5 This will give you friendly info at Aircraft dot at 15km range at 5km Pilot name 2.5km all other at 100metres eventlog=eventlog.lst describes where eventlog is written=n to is enabled eventlogkeep=0 0 when 0, every mission overwrites the event log file, so it contains the last mission only. when 1, it writes an eventlog continuously, keeping log for all missions you fly 3dgunners=1 For 3d gunners in PF will effect frame rate =0 turns them off Typeclouds= TypeClouds=0 - standard clouds TypeClouds=1 - improved quality clouds [HotKey game] describes keys assigned during play PrintScreen= ScreenShot P=pause Pause=pause [HotKey gui] Escape=activate This line needs to be in config to end missions, For some reason, this line very often disappears when patching is done. [HookViewFly Config] this section is how your view moves in external view timeFirstStep=2.0 Time until aircraft passes camera deltaZ=10.0 Angle of camera to aircraft [HookView] The camera origins are fixed but the distances you may be able to change for the [Hook View] and [Hook View Fly] sections MouseLeft=Len [HookView Config] AzimutSpeed=0.1 TangageSpeed=0.1 LenSpeed=1.0 MinLen=1.0 (closest distance from a given object while in camera view) DefaultLen=20.0 (Default distance from object when using external views) MaxLen=3000.0 (Max distance from camera you can zoom out, I have mine set to 50000 which is 50km. Nice for finding stuff if you die!) Speed=6 (speed of mouse zoom and pan, higher is faster) [HotKey builder] these are key assignments when using the mission builder [MouseXYZ] This section concerns the variables for mouse control The mouse is generally used as a viewing device either in game or when viewing tracks [HotKey Console] This section deals with console . There is a console help section in forums at www.airwarfare.com for full list of commands. In the console you can change most of the config parameters while in game. Shift Tab=Activate The console is where you can type commands to the game. In this default setting you press shift +tab to show console [Console] The console is where you can type commands to the game. In the default key setting you press shift +tab to show console The most common use is fps START SHOW to display FPS In the console you can change most of the config parameters while in the game. HISTORY=1024 Number of lines permitted in console HISTORYCMD=1024 LOAD=console.cmd SAVE=console.cmd LOG=0 Here logs are disabled but you can save them by setting to 1 if you wish the console will then be saved to a text file for you to view later. LOGTIME=0 LOGFILE=log.lst LOGKEEP=0 [sound] This section deals with sound settings in game most are determined in the in game hardware setup sound section SoundUse=1 SoundEngine=1 Speakers=1 0=Default 1=Headphones 2=Desktop speakers 3=Quadraphonic 4=Surround Placement=0 0=Default 1=Small 2=Narrow 3=Wide SoundFlags.reversestereo=0 RadioFlags.Enabled=1 RadioEngine=2 Radio volume MusicVolume=8 Music volume ObjectVolume=14 Object volume MusState.takeoff=1 Takeoff music can be 1 or 0 MusState.inflight=1 Inflight music can be 1 or 0 MusState.crash=1 Crash music can be 1 or 0 MasterVolume=12 Main volume NumChannels=2 0=Default 1=8 2=16 Best for quality vs. performance 3=32 Beware of performance hit! [rts] This section is for input controls for mouse and joystick ;ProcessAffinityMask=1 IL-2 supports two processors using the ProcessAffinityMask in the conf.ini. There's little documentation from Maddox Games about how you're supposed to use it, though. ProcessAffinityMask=1 Core1 (default) or ProcessAffinityMask=2 Core2 or ProcessAffinityMask=3 Core1+2 You must remove the semicolon in order to run this command Basically tells IL-2 which core(s)to run on. There appears to be no consensus that running IL-2 on two cores shows any tangible difference. One more thing to add. With the Semicolon in place you essentially have the same as: ProcessAffinityMask=0 which also uses both cores so it's the same as =3. mouseUse=2 joyUse=1 can be 1 or 0 trackIRUse=1 TrackIR is a piece of hardware that moves view when you move your head. This line also has to be in file if you use niewview a program that helps you get better control of your hat switch DisableIME=0 locale= Set menu and HUD message language to other than English, e.g., German (de) or Russian (ru) or Hungarian (hu) [rts_mouse] SensitivityX=1.0 the higher the value the more sensitive movement in x axis SensitivityY=1.0 the higher the value the more sensitive movement in y axis Invert=0 Inverts mouse movement SensitivityZ=1.0 the higher the value the more sensitive movement in z axis [rts_joystick] Joystick settings are found in hardware setup in game See Tully's Joystick section for full instructions on setting up your joystick. X=0 1 4 9 16 25 36 49 64 81 100 0 Each axis has 12 entries. The first is the dead zone ( 0 to 50) the last is filtering ( 0 to 100) Y=0 1 4 9 16 25 36 49 64 81 100 0 If all values set to 100, IL-2 software does not do any "curving" [Render_DirectX] This section is for your video card and how its features are used in the game. Most use OPENGL as the game was optimized for this so all comments are in this section. See Video card section in IL2 optimization guide for explanation of terms [Render_OpenGL] This section is for your video card and how its features are used in the game. See Video card section in IL2 optimization guide for explanation of terms As Far as I Know the Text variables are all set in hardware setup program and depend on your card. TexQual=3 3= normal 2= reduced by factor of 2 1= reduced by factor of 4 0 = reduced by factor of 8. Only need to reduce for older graphics cards of 16mb or less. TexMipFilter=1 0=Bilinear (fastest) 1=Trilinear (Improves quality with little sacrifice in speed) 2=anisotrophic (Best quality but slower) TexCompress=2 0=No compression best quality 1=16bit conversion 2=S3TC compression, best Performance. with easily worst texture quality TexFlags.UseDither=1 TexFlags.UseAlpha=0 TexFlags.UseIndex=0 TexFlags.PolygonStipple=1 TexFlags.UseClampedSprites=0 TexFlags.DrawLandByTriangles=1 TexFlags.UseVertexArrays=1 TexFlags.DisableAPIExtensions=0 TexFlags.ARBMultitextureExt=1 TexFlags.TexEnvCombineExt=1 TexFlags.SecondaryColorExt=1 TexFlags.VertexArrayExt=1 TexFlags.ClipHintExt=0 TexFlags.UsePaletteExt=0 TexFlags.TexAnisotropicExt=0 TexFlags.TexCompressARBExt=1 must be activated if S3TC compression is used TexFlags.TexEnvCombine4NV=1 TexFlags.TexEnvCombineDot3=1 TexFlags.DepthClampNV=1 TexFlags.SeparateSpecular=1 TexFlags.TextureShaderNV=1 HardwareShaders=0 Must be 1 to activate Perfect mode. Shadows=1 The lower the value in this section the less detailed these appear but game runs faster e.g If you suspect trees or forests may cause the frame rate to drop, try lowering the Forestparameter in the conf.ini to 1, or even 0 (that would make forest appear in less detail, but render faster). The only ones I have adjusted are water, Forest and Effects. Specular=2 SpecularLight=2 DiffuseLight=2 DynamicalLights=1 MeshDetail=2 VisibilityDistance=2 Sky=2 Forest=1 LandShading=2 LandDetails=2 LandGeom=2 TexLarge=0 High-resolution airplane textures (0/1) 0= low resolution, fewer memory needs, faster 1= quality, improves textures more memory need, slower TexLandQual=3 TexLandLarge=0 High-resolution land textures (0/1) 0= low resolution, fewer memory needs, faster 1= quality, improves textures more memory need, slower VideoSetupId=15 0 - Safe Settings 1 - Default Settings 2 - Maximum Settings 3 - NVidia GeForce 6800/6600/FX/4/3 4 - NVidia GeForce 5200..5900 - 1.x Shaders 5 - NVidia GeForce 4MX 6 - NVidia GeForce 2 GTS/MX/256 7 - NVidia Riva TNT2 8 - ATI Radeon X800/9800/9700/9600/9500 9 - ATI Radeon 8500/9000 10 - ATI Radeon 11 - Intel 915/925 (GMA900) 12 - Kyro II 13 - Matrox G400 14 - 3dfx Voodoo 3 15 - 3dfx Voodoo 5 16 - S3 Savage 4 17 – Custom Water=1 To select water rendering mode please modify the Water section in the file conf.ini in the [Render_OpenGL] section (Water = 1 by default). Water = 0 - Water with flat geometry (fastest). Water = 1 - Water with flat geometry (fast). Water = 2 - This mode is visually similar to water = 3 but it runs on ATI cards 9800, X800, X1800 and later models. Water = 3 - Fast render mode with Vertex Shaders 3.0 (NVIDIA 6600 and later models) Water = 4 - Better quality mode with Vertex Shaders 3.0 (NVIDIA 6800 and later models) Reminder: ATI 9500 and higher supports modes: 0, 1, 2. NVIDIA 6600 and later models support: 0, 1, 2, 3, 4. NVIDIA cards before the 6xxx series support: 0, 1, 2 (2 is not recommended). Effects=1 To minimize effects settings, use Effects = 0 (effects without shadows). Effects=2, ([Render_OpenGL] section of conf.ini) test mode for improved effects lighting. This mode required 3.0+ MHz CPU. ForceShaders1x=0 If on older cards try to use ForceShaders1x = 1 it's helpful for GeForce FX 5200, 5600, 5700 cards. Not needed for newer cards Clouds rendering In order to see higher quality clouds you will need to manually edit the conf.ini file located in your main game folder before launching the game. Open the file with a text editor, find the [game] section and in the TypeClouds= line write in either 0 or 1, then save the file. TypeClouds=0 standard clouds TypeClouds=1 improved quality clouds Note: When playing online the player will see the cloud type set by the server, and not as individually set in their conf.ini. This is done to ensure all players see the same tactical situation in the air regardless of their settings. PolygonOffsetFactor=-0.15 If you experience flickering airfields when viewed from high altitude, add these two lines into the OpenGL section to fix the issue PolygonOffsetUnits=-3.0 [DGen] Not added by default used to alter settings for offline play NoBadWeather=1 Can be set to zero or one, one meaning you never get bad weather MissionDistance=50 Can be set to from 10 to 200 Kilometers, depends on the map and targets available. It is not guaranteed that there will be suitable targets in this distance NoAirfieldHighlight=1 Set to one to zero. Zero meaning you'll have AAA/flak unit at some unused airbases RandomFlights=0 Can be set to 0 to 5 Random flights are flights not related to your mission, both friendly and enemy are just incidental you may or may not see these flights, they might not get close enough. Default or not having the line in conf.ini is average (3). Can affect frame rates. MaxFLAK=5 Can be set to 0 to 100, default or not having the line in conf.ini is 10. Can affect frame rates. Affects the amount of flak generated from your airfield to target, so can affect frame rates very much. AirIntensity=Low Settings are low, medium and high. Default or not having the line in conf.ini is medium. Sets the number of flights, enemy and friendly, that are related to your mission. On low setting, there will be no random flights and it will override the "RandomFlights=" setting in that case, ( see above ). Can dramatically affect frame rates. GroundIntensity=Low Settings are low, medium or high. On low, you'll only have ground objects around target or active airfields. Default is medium (or not having the line in conf.ini ) and there will also be extra objects around your flight route, besides target area and active airfields. High gives you extra targets of opportunity to and from your home field. Can dramatically affect frame rates. Maxbomberskill=1 Settings are 0, 1, 2 and 3, ( for rookie, average, veteran and ace ) and default or not having this line in conf.ini, the AI bomber gunners will be kind of random or depend on other settings like CampaignAI=. This limits the entire bomber skill ( not just the gunners ) to a lower level if preferred, so you can attack bombers more easily if you limit it to a low setting. It affects only enemy AI for bombers, not friendly. Unfortunately, this does nothing for transport aircraft, such as LI-2, C-47 or JU-52, so be careful around those and don't assume they will be limited like the bombers if you set this to a low setting!!! Sometimes FW-200 Condor can also sometimes be assigned as a transport plane in some maps, so watch it!!!! CampaignMissions=Hard Settings are easy, normal or hard. Default or not having the line in conf.ini is normal. This changes the scripts ( ops files, I.E. - ops41-E.dat, where "E", means easy ) files in the Dgen folder used to generate missions. Affects the number of enemy planes encoutered as opposed to the number of friendly planes in your group/s. For example, set on easy, you might have a mission generated which gives you four fighters on your side with four bombers, and two enemy fighters will later show up to intercept your bombers. The very same mission on hard might give you only two fighters on your side, maybe the same number of bombers to escort, but you'll run into four enemy fighters to deal with!! This balances out so it does not affect frame rate much, if at all. CampaignAI=Hard Settings are easy, normal or hard. Default or not having the line in conf.ini is normal. Increases enemy and friendly AI by a factor of one. Low increases friendly AI level higher while lowering enemy AI level. High does the opposite. Normal gives you a more even match of AI strength." CampaignLength=Short VeryShort, Short, Medium, Long, VeryLong (VeryLong is default) CampaignDifficulty CampaignDifficulty=Easy CampaignDifficulty=Hard Easy settings will add one level to all friendly groups and decrease enemy experience OperationVictory=100 In Pacific Fighters dynamic campaigns the player's actions influence the outcome of individual operations as well as the whole war. The system works by assigning a static number of points to each target destroyed, and calculating a total number of points for each side. If your side destroys enemy targets, points are added to your side's tally. If your side's targets are destroyed by the enemy, the points are subtracted from your side's tally..Each side is assigned a predetermined number of points which in each operation means a historical outcome (victory or defeat). If the operation's tally does not match the historical outcome, an alternative briefing is triggered which may mean a defeat for the side that historically won, or vice versa.For example, if you want mission outcome to always be historical, you can set the parameters to unachievable high values, such as: OperationDefeat=-100 OperationVictory=3000 WarVictory=1000 OperationDefeat=-3000 WarDefeat=-1000 WarVictory=30000 WarDefeat=-30000 Default value for an operation outcome is 100 points (added if it's a victory, subtracted if it's a defeat). War outcome's value is 1,000 points By reducing the numbers you can make your contributions matter much more in the overall war effort. The following point values are used Carrier = 100 points Other ship = 20 points Plane = 5 points Tank = 3 points All other targets = 1 point The tallies are recalculated after each mission, and they're checked at the end of each operation. UseParachutes Japanese have chutes from start of war Saludos. Quote Link to comment Share on other sites More sharing options...
Unghaar Posted November 12, 2010 Report Share Posted November 12, 2010 Juer cuanta cosa Gracias Quote Link to comment Share on other sites More sharing options...
Rayonant Posted November 12, 2010 Report Share Posted November 12, 2010 Muchas gracias espiral, muy bueno para complementar el de Cube :icon11: Quote Link to comment Share on other sites More sharing options...
Soec Posted November 13, 2010 Report Share Posted November 13, 2010 Muy buena espiral! espero que después de esto nadie más vuelva a preguntar dónde modificar cosas del conf.ini Quote Link to comment Share on other sites More sharing options...
Cube Posted November 18, 2010 Report Share Posted November 18, 2010 Muy buen trabajo espiral, entre el tuyo y el mio deberia ser suficiente para tenerlo todo puesto correctamente. Si quieres modificar el mio para rectificar y añadir cosas, no tengo inconveniente. Quote Link to comment Share on other sites More sharing options...
Vulcanel Posted November 18, 2010 Report Share Posted November 18, 2010 (edited) Buenísimo... muchas gracias. Si me permitís un apunte: Landgeom=2 => 36 kmts. de distancia de visión del terreno. Landgeom=3 => 72 kmts. de distancia de visión del terreno, en modo perfect y con clima despejado Ni que decir tiene que la segunda opción, requiere una máquina a la altura de las circunstancias... Saludos. Edited November 18, 2010 by Vulcanel Quote Link to comment Share on other sites More sharing options...
Jack_Aubrey Posted November 18, 2010 Report Share Posted November 18, 2010 Pos yo uso el landgeom a 3 y gasto una geforce 8600m gt con un core duo t 7500 y veo los objetivos en tierra a gran distancia... si no preguntaselo a Unghar o Baronkaos que fueron conmigo en el entreno de este martes Quote Link to comment Share on other sites More sharing options...
Unghaar Posted November 18, 2010 Report Share Posted November 18, 2010 Pos yo uso el landgeom a 3 y gasto una geforce 8600m gt con un core duo t 7500 y veo los objetivos en tierra a gran distancia... si no preguntaselo a Unghar o Baronkaos que fueron conmigo en el entreno de este martes Doy fe de ello Quote Link to comment Share on other sites More sharing options...
Shura Posted November 18, 2010 Report Share Posted November 18, 2010 Pos yo uso el landgeom a 3 y gasto una geforce 8600m gt con un core duo t 7500 y veo los objetivos en tierra a gran distancia... si no preguntaselo a Unghar o Baronkaos que fueron conmigo en el entreno de este martes Eu tamen estaba. Una cosa Jack, ¿tienes activado el modo perfect? Es que yo tengo un ordenador muy similar y si pongo el perfect se me pone el suelo todo negro. Saludos y buena caza Quote Link to comment Share on other sites More sharing options...
Arcus Posted November 18, 2010 Report Share Posted November 18, 2010 Pos yo uso el landgeom a 3 y gasto una geforce 8600m gt con un core duo t 7500 y veo los objetivos en tierra a gran distancia... si no preguntaselo a Unghar o Baronkaos que fueron conmigo en el entreno de este martes Eu tamen estaba. Una cosa Jack, ¿tienes activado el modo perfect? Es que yo tengo un ordenador muy similar y si pongo el perfect se me pone el suelo todo negro. Saludos y buena caza Yo tengo un portátil con la 8600 y también me pasaba, me copie la configuración de Jack y mano de santo. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.