Jump to content

Pak1979

Members
  • Posts

    12
  • Joined

  • Last visited

About Pak1979

  • Birthday 01/06/1979

Recent Profile Visitors

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

Pak1979's Achievements

Newbie

Newbie (1/14)

  • Dedicated
  • First Post
  • Collaborator Rare
  • Week One Done
  • One Month Later

Recent Badges

10

Reputation

  1. I can load all new Maps but i have up to 98% Ram use by 64GB of Ram... And it need long Loading Time...
  2. 43 fps i7/6700k @ 4,6Ghz with the render distance on default.... higher render distances give me lower fps... so its not good to compare the fps from benchmark... without the datails of render distance and the other graphic setings.
  3. I have updatet the new NVIDIA 381.65 drivers yesterday. Ok i found it....The Riva TunerStatisticServer from MSI Afterburner that runs in Background to display frames temps core speed and other data.....It is the problem,. After deactivate it in steelbeasts its starts and works fine. Looks like the windows update have problems with the statistic server in combination with steelbeasts. Before the update it worked allways, but the good is steelbeasts runs now after shut of the StatisticServer Tool that is great.
  4. Debug Log.... [14:56:44,587] TRACE: ------------------------------- [14:56:44,587] TRACE: Steel Beasts Log File v4.010 [14:56:44,587] TRACE: Fri Apr 7 14:56:44 201 / 15188 [14:56:44,587] TRACE: ------------------------------- [14:56:44,587] TRACE: +--+ MEMORY USAGE INFO (SteelBeasts START): [14:56:44,587] TRACE: | | Process: 291 MB (0 % of 128.0 TB total, 128.0 TB free) 291 MB min/180 MB max [14:56:44,587] TRACE: | | Physical: 2.5 GB (16 % of 15.9 GB total, 13.4 GB free) 2.4 GB min/2.5 GB max [14:56:44,587] TRACE: +--+ Pagefile: 2.5 GB (14 % of 18.3 GB total, 15.8 GB free) 2.4 GB min/2.5 GB max [14:56:44,587] INFO : Network logging alarm threshold set to '120'. [14:56:44,587] INFO : Network logging alarm message age set to '5'. [14:56:44,629] TRACE: Entered BuildDeviceList [14:56:44,655] INFO : Valid mode: 2560 x 1440, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1920 x 1440, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1920 x 1200, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1920 x 1080, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1680 x 1050, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1600 x 1200, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1600 x 1024, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1600 x 900, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1366 x 768, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1360 x 768, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1280 x 1024, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1280 x 960, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1280 x 800, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1280 x 768, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1280 x 720, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1152 x 864, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 1024 x 768, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 800 x 600, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 720 x 576, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 720 x 480, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] INFO : Valid mode: 640 x 480, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0 [14:56:44,655] TRACE: Found device... Leaving BuildDeviceList [14:56:44,658] DEBUG: WM_ACTIVATEAPP: 0x1 [14:56:44,668] DEBUG: WM_SIZE: 0x0 [14:56:44,670] DEBUG: WM_ACTIVATEAPP: 0x0 [14:56:44,671] TRACE: Called FindWindowRects [14:56:44,671] DEBUG: Display name '\\.\DISPLAY1' - 0x5. [14:56:44,671] INFO : Eyefinity configuration query failed for display name '\\.\DISPLAY1'. [14:56:44,671] DEBUG: FindMenuDisplayArea: 0/0/0/0 [14:56:44,671] TRACE: Entered Initialize3DEnvironment [14:56:44,671] DEBUG: AdjustWindowForChange: For windowed [14:56:44,672] DEBUG: *** PresentationIntervals (0x0/0x80000000) NOT SUPPORTED! (Initialize3DEnvironment) ***
  5. It do nothing. The Mouse cursor for loading rotate any seconds, but then came no reaction ... no screen or message pops up ... in the task manager i can see the exe is starting but after a few seconds he close. that is the complete text of the logfile [07:58:23,922] WARN : ------------------------------- [07:58:23,922] WARN : Steel Beasts Log File v4.010 [07:58:23,922] WARN : Fri Apr 7 07:58:23 201 / 7220 [07:58:23,922] WARN : ------------------------------- [07:58:23,922] WARN : +--+ MEMORY USAGE INFO (SteelBeasts START): [07:58:23,922] WARN : | | Process: 290 MB (0 % of 128.0 TB total, 128.0 TB free) 290 MB min/180 MB max [07:58:23,922] WARN : | | Physical: 2.9 GB (18 % of 15.9 GB total, 13.0 GB free) 2.8 GB min/2.9 GB max [07:58:23,922] WARN : +--+ Pagefile: 3.5 GB (19 % of 18.3 GB total, 14.8 GB free) 3.4 GB min/3.5 GB max
  6. I have installed the new "creators update" on my windows 10 x64 System. And after the update steel beasts 4.10 wont start anymore. a reinstallation of steel beasts and the newest codeMeter software brings no success. All other Games and Programs on my system works fine and without problems...
  7. I found this.... Yoke made in USA... http://www.scip-engineering.com/portfolio/w10-series/ http://www.scip-engineering.com/portfolio/w20-series/ ATARI StarWars Yoke works the same way... http://mirrors.arcadecontrols.com/OscarControls/ebay/yoke/ how to build your own yoke... http://arcadecontrols.com/hosted/yoke/
  8. Hi SB 3.002 works fine with my Windos 8 64bit but after updatet to Windows 8.1 SB makes trouble. The Mouse cursor flickering and the mouse movement stutters. All my other Software and Games works without this problem. A reinstall of SB 3.002 and the ATI display drivers brought no improvement, only switch SB to Window mode eliminates the problem.
  9. Version 2.0

    231 downloads

    "Einstrich-Keinstrich" Uniform of the DDR - NVA Units in the 1980´s V2.0 Completely reworked Fieldjacket, Belt and Suspenders... (removed the vest)
  10. @Emi Thanks for this Bugreport... it was a old icon file in the rar. i edited my release post A new coreccted Version 1.52 is Uploaded...(all fixes included) and a single Fix 1.50 to 1.52 for this one who downloaded the old rar File yesterday...
  11. Hi fidelthefallguy The HiRez 1.3 works fine and makes the game looks mutch better. Because unfortunately you don't work any more on the mod, i have made a updat for the 1.3 Mod with reworked and new textures. I hope it is ok for you! If not and its a problem i remove the Link immediately. It is only a Update for the fantastic HiRez 1.3 from fidelthefallguy... you must install the HiRez 1.3 first. Are included: - scenery textures - Streets / ways / stones / Trees - Explosion / fire/Effects (mix from your original HiRez 1.30 Mod and new Textures +new Alternativ version for Fire and Fireball) - M1 Turet Optics - menu logo from old SB1 Mod - Tank / tower direction better recognizably (brighter tower and darker hull) v1.52 new Upload all Fixes included... Link: http://www.megaupload.com/?d=A1HF3RJ4 Fix for the old upload v1.50 to v1.52 - coreccted Smoke-Dust and MapIcons Link: http://www.megaupload.com/?d=OIA3GTSH Mud - earths http://img805.imageshack.us/img805/3398/erdegn.jpg Street - Path http://img263.imageshack.us/img263/3816/strassem.jpg Forest ground 2x http://img32.imageshack.us/img32/3497/waldc.jpg Turf 2x http://img694.imageshack.us/img694/1456/wiese.jpg Tank direction announcement - menu Keys - gravel - shore - field http://img703.imageshack.us/img703/4859/allesj.jpg
×
×
  • Create New...