Jump to content

Panzertard

Members
  • Posts

    5164
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by Panzertard

  1. AA/AF variant of your problem:

    I just have to ask if you tried the following method (whic seems to me like that it may cure the proplem too):

    1. Set DCS to native resolution from start on

    2. Start DCS normally like you do. But stay in the "menu".

    3. Switch to desktop

    4. Switch back

     

    Or maybe you have to be "ingame" rather than in the "menu" for it to work?

    It may trigger the ATI to reconsider the parameters the game is running under.

     

    But as of your original cause to this dilemma - maybe you can post a DXDiag report to anyone who might have an insight into what the cause may be?

    And maybe throw in a few details about your system, os and version, etc? :)

    You never know who spots this post and is able to weed out the original problem :)

     

    Stuttering:

    Hm, there's another post reagarding that around here in this subforum somewhere - I need time to search it up - or maybe you finds it before me.

  2. Hm well - this post http://forums.eagle.ru/showpost.php?p=603352&postcount=50

    states that a "Graphics card: 256 MB DirectX 9 compatible" should be okai - says nothing about ATI or Nvidia only. (Recomended says that).

    And Intel about the Express Chipset: How much graphics memory does my computer have?

     

    You know what would be nice - just to have a report form your DXDiag.

    Start "Dxdiag" from you Run command - there's a "save report" function there.

    Attach it here - that way if someone with better knowledge of the minimum requirements may be able to tell us if you are stuck with this problem.

     

    Other than that - tweaking your graphic setting may be the only option to get rid of it. Again, tweaking the "C:\Program Files\Eagle Dynamics\Ka-50\Config\graphics.cfg" may cause even more problems - so make sure you make a backup of the file before we start.

     

    I dont know the options and settings there too well - but why not just try to disable all shadows as you said.

    I've spotted two settings indicating it can change shadows and it's behaviour:

     

    ShadowLevel = 1;

    Set it to 0

     

    This one is a bit more questionable, but try it anyway:

    ShadowDensity = 0.6;

    Set it to 0 as well, like

    ShadowDensity = 0;

     

    Regarding the water and that it shows up above the landmass - I dont have any suggestions. But maybe, just maybe, disabling the "faulty" shadows may help and it fixes that problem too.

  3. Koenigstiger - I could asist you a bit more "up close" and have a look at your system to try to help you. But that involves you joining our Teamspeak over at our place (see the Lebowske link in my signature).

    And that you are able to set up a remote dekstop tools so you could share out some of your system event viewer (or other system tools).

     

    I'm not giving you any more specific directions right now - because you need to make up your mind if you are willing to trust me with this, and that you are able to spend a little bit of time doing this :)

    But if you are - drop me a PM and I'll burn off a few hours togetehr with you to have a look. PS - just bought a motorcycle, so I might not respond to the PM right away - out driving quite a lot :)

  4. This sounds a bit like a "known problem" - when it crashes at the *end*.

    However - the crash before a full load - is somewhat strange.

     

    Can you give us some data about your system maybe?

    OS versions, and 32 or 64 bit / CPU / RAM / graphics / soundsystem / game controllers, keyboard, mouse.

     

    Tell us about the details from any software that enhance any of the things above?

    Joystick software? Mouse software? Graphics software?

     

    Other customization you have done to your pc? Overclocking?

     

    And see if you find a "\Ka-50\Temp\something.CRASH" file - attach it or post the content here.

    And any Errors in the "Event Log / Viewer - for Applications" please. There should be some details about the crash there too.

  5. Yeah, I just tried ARMA 2. It sucked. Graphics are "ok", but their is no realism in the vehicles. The Ka-52 just has a big bullseye decaled over the hud. Flight model is arcade. Even the firearms kind of suck. Guess I'll keep on waiting...

    Thats the kind of compromises you may get when you reach out and try to cover all the aspects in a war and making all the roles playable. Otherwise they would end up developing it forever - or using too many man-hours, so it would be too expensive for customers to buy.

    Of course there might be someone who are able to put together a "war simulator". However I doubt there will be anyone daring to do so or even be successful at it. :)

  6. Im planning on getting a bike so I can come over to you and inspect that garage of yours - clearly it's big enough to hide a real Ka-50.

    Keep up the good work bud :)

     

    (Altogh shame on you who doesnt know how to handle the camera - it's clearly a requirement in any relationshsip where you want to have photos from memorable moments in the garage, kitchen, the kitchen-floor or the hood of your car).

  7. Just a heads up if you didnt know it.

    It's the "up" speed of 2mbps that is important for others connecting to you. You will be sending data "up" to them from your server.

     

    In that aspect - dont get your hopes too high regarding how many people who can play at your server.

    I would assume you should be able to host for 2 guests - no sweat.

    4 People - yes, you shouldnt have any problems, unless they have problems in their end.

    8 people - well, this is beyond some of the recomendations I've seen for DCS MP hosting. (Which is based on "get 1mbps for each guest you are planning to host for). I havent seen any good definitions of the host / guest data requirements yet though. :)

     

    Personally I would definitively experiment with it and see how well she (Mrs. Server host ... Nina wasnt it?) holds together.

    Altough I would be supprised if someone have problems staying connected / lags / desyncs if you go beyond what you can expect to host :)

     

    Good luck, Ramstein :)

  8. Ah that summarize pretty well how these issues, diagnostic data and results are tied together.

    Thank you once again :)

     

    No worries - well be greeting the experimental support with open arms whenever it appears for download and testing.

    On a related note - is there a way for me to sign up for testing this / beta? Sign an NDA? Or perhaps it's for developer and partners only?

    • Like 1
  9. LALT-C once, twice, three times until you have the desired "mouselook behaviour" (I use TrackIR - no mouselook).

    The Mouse Wheel - to release it the SAI lock.

    Sometimes I have to hold the Right Mouse button - to neutralize the SAI.

    And then use Mouse Wheel again to align/calibrate it to my current attitude.

     

    Hm, I cant remember if you used the left mouse button for anything.

    Altough I seem to remember I used both mouse buttons at some stage - maybe that was for re-locking it again? Not sure.

  10. - Rotary knobs: Left click or right click - knob goes left or right (or up / down).

    Ex: Radio knob - or the targeting computer knob.

    - Rotary wheel knobs: Hold left mouse botton on them - move left/right.

    Ex: HUD brightnes or Shkval contrast/brightnes.

     

    Some knobs/switches may have no function. I think I've seen the same thing with the HSI as you mentioned.

     

    Trimming - the AP channels behaves more like a damper.

    You Press and hold the Trim until you have reached the attitude you want - then release it. The AP damper will the try to maintain that attitude.

    (Hint: It can be smart to assign the Trim to a accesible trigger on your joystick - you have to use it often/almost always).

     

    As for more technical discussions about the AP/trimming - there's a few articles here on the forum if you search a little bit :)

  11. Wags has said that the next big change to the engine should be an addition of a 64 bit version, so DCS can take advantage of more RAM. So if you have a fairly modern system, 64 bit is the way to go. I'm currently using win 7 rc 64 bit, never had any issue.

    I would guess they to take advantage of more of the 64bit systems - altough rebuild the whole engine into 64bit is quite a big undertaking. This is due to the nature of x64 platform require you to run all the software - and all the components it relies on (all DLL's in the system / Lua / everyting, maybe including TrackIr).

    I doubt we will see a full 64bit enginge within the next 2 years (my personal opiniion of course). I think it may be more realistic to see this closer to the end of teh DCS-series.

     

    But at some stage we will see the first experimental support for it (sometimes next yer maybe?) - and better optimization - altough as Microsoft states, you shouldn't have any major performance hit from runnign 32bit software on a 64bit platform. :)

     

    EDIT: Ohgawd - look at my spelling - no wonder I suck at coding :(

  12. Normally I would suspect a graphics driver - or a mod to cause this. Or manually editing some of the setting files to try increase the fps?

    So maybe you can have a look at some of those things?

    Latest drivers? Unedit / remove any mods?

     

    And regarding the Mobile chipset - is it within the minimum requirements for BS?

  13. 1. Never seen it illuminate - altough now that you've menationed it, I'll keep an eye out for it.

    2. No. Ground crew only - I've never experienced any AI using radio communication other than the "hardcoded" groundcrew. (Aka Boris according to a member in the 159'th). :)

    I've seen no evidence of mechanisms supporting "intelligent" ground unit communication.

     

    EDIT: "Manuals"? I have to look that up somewhere ... :D

  14. Simple question:

     

    I want to upgrade to Windows 7 Beta to try it - only because I hear BlackShark runs way faster with multicore in DX 10 due to some DX 10 optimizations. That is all, I don't want to use the OS for anything else. I'm using XP right now and feel like I'm missing out.

     

    Which do I go to for best performance with DCS - 32 bit or 64 bit?

     

    Thanks.

     

    This is a late reply - but since I've dug up some new information, quoted from MSDN:

    Performance Implications of Running a 64-bit Operating System

    Because processors with AMD64 and Intel 64 architecture can execute 32-bit instructions natively, they can run 32-bit applications at full speed, even on a 64-bit OS. There is a modest cost for converting parameters between 32-bit and 64-bit when calling operating system functions, but this cost is generally negligible. This means that you should see no slowdown when running 32-bit applications on a 64-bit OS.

    Altough you must see this information in relevance to your drivers and hardware - because you need hardware and drivers which is mature enough for 64bit (of course).

     

    The reality of 64bit is that you may experience some slowdowns depending on your configuration - but from this point in time and onwards I think we will see much more 64bit development and (latest) hardware/driver configurations that runs as smooth as 32bit - or starting to outperforming it as well.

     

    But for "old" configurations - sticking with 32bit may seem to be the smart thing until you have a new rig. :)

  15. Thanks for the heads up c0ff - still, even though you are looking elsewhere to nail the issue - I still wanted to understand a bit more about the 32 bit vs 64 bit workings.

    (all quotes in this post is taken from http://msdn.microsoft.com/en-us/library/bb147385(VS.85).aspx)

    EDIT: Oh, I hope you're all rested and getting back up to speed after your vacation! :)

     

    And I stumbled upon the definition/requirements of the adressable memory spaces:

     

    Differences in Addressable Memory

     

     

     

    The first thing most developers notice is that 64-bit processors provide a huge leap in the amount of physical and virtual memory that can be addressed.

    • 32-bit applications on 32-bit platforms can address up to 2 GB
    • 32-bit applications built with the /LARGEADDRESSAWARE:YES linker flag on 32-bit Windows XP or Windows Server 2003 with the special /3gb boot option can address up to 3 GB. This constrains the kernel to only 1 GB which may cause some drivers and/or services to fail.
    • 32-bit applications built with the /LARGEADDRESSAWARE:YES linker flag on 32-bit versions of Windows Vista, and on 32-bit versions of Windows Server Code Name "Longhorn" operating systems, can address memory up to the number specified by the boot configuration data (BCD) element IncreaseUserVa. IncreaseUserVa can have a value ranging from 2048, the default, to 3072 (which matches the amount of memory configured by the /3gb boot option on Windows XP). The remainder of 4 GB is allocated to the kernel and can result in failing driver and service configurations.
      For more information about BCD, see Boot Configuration Data on MSDN.
    • 32-bit applications on 64-bit platforms can address up to 2 GB, or up to 4 GB with the /LARGEADDRESSAWARE:YES linker flag.
    • 64-bit applications use 43 bits for addressing, which provides 8 TB of virtual address for applications and 8 TB reserved for the kernel.

    As you can see - with 32bit on the 64bit version we should technically be able to utilize 4Gb of adresses.

    And that I could have gotten into trouble for messing about with the "IncreaseUserVa", or more frequent crashing if the system would run out of resources. Altough it can be reset quite easilly again.

     

    But also - reflecting on the difficulties of coding for (compiling a true) 64 bit - my god, that seems quite strict, altought I understand the necessity of it:

     

    Potential Compatibility Pitfalls

     

     

     

    Most applications developed for a 32-bit platform will run without problems on a 64-bit platform. A few applications could have issues, which might include the following:

    • All drivers for by 64-bit editions of Windows operating systems must be 64-bit versions. Requiring new 64-bit drivers has implications for copy-protection schemes that rely on old drivers. Note that kernel-mode drivers must be Authenticode-signed to be loaded by 64-bit editions of Windows.
    • 64-bit processes cannot load 32-bit DLLs, and 32-bit processes cannot load 64-bit DLLs. Developers must ensure that 64-bit versions of third-party DLLs are available before proceeding with development. If you must use a 32-bit DLL in a 64-bit process, then Windows inter-process communication (IPC) can be used. COM components can also make use of out-of-process servers and marshalling to communicate between boundaries, but doing so may introduce a performance penalty.
    • Many x64 processors .....

    Well - just my reflections now that there's nothing more for us to do than waiting for the patch - and/or getting experimental 64bit support.
  16. S@oDepp:

    From my basic understanding of the DirectX framework, I dont remember the whole strategy but:

    Affinity depends on which cpu geths which job. They wont all (4) work on rendering - only one of the cores can have that task (or rather, thats the recomended strategy). Other threads may work with AI behaviour, other kinds of logics.

    EDIT: Ah, found the reference: http://msdn.microsoft.com/en-us/library/bb204834(VS.85).aspx

    This is what ED have coded. The guys who makes the "affinity trick" have no control over which thread/workload goes to which cpu/core.

     

    So you will never see equal workload for all the cores. Or rather, if you see it - then it's just a coincidence. :)

  17. HI Madmax. Sorry to hear you only found 20 servers online.

    I can assure you if you find me online, I count as 40 servers extra due to the confusion and the immersion you get from me as I spew out cusses when you kill me in PvP.

    Truly.

     

    Sincerly, your Tard - hope to see you later :)

  18. I wont pay €1 for a hotas that fits in my garage and smells badly - someone actually have to pay me for taking it.

    I'll pay €300 easilly for one that suits my needs, and doesnt wear out. Ever.

    for an x52 fully dressed up, €200 is quite fair .. with pedals. (I dont remember what I paid for it).

  19. Sorry to not be of assitance - since I think you should avoid Game mode if you can.

    You can learn so much more from the sim mode - and have so much more fun over time compared to game-mode if you are stuck with the "easy" stuff there.

    But it might take a bit of training to get there - but still worth it. :)

    EDIT: Okai, so I was a bit drunk last night .. oops

×
×
  • Create New...