Jump to content

janwas

WFG Retired
  • Content Count

    2.733
  • Joined

  • Last visited

Community Reputation

0 Neutral

About janwas

  • Rank
    Primus Pilus

Contact Methods

  • MSN
    janwassenberg@gmx.net
  • ICQ
    135709088

Profile Information

  • Gender
    Male
  • Location
    DE

Recent Profile Visitors

902 profile views
  1. Interesting, thanks for the data. Looks like 9 people with the TSC (though the 1.5 GHz one is quite a low frequency). The vast majority is apparently running Linux, which reports 1 GHz. Also interesting - they probably scale the TSC. 4 are using the HPET - unsure whether on Linux or via Aken (and one of them has the frequency hopping thing enabled, which is why it doesnt exactly hit the frequency of the classic PC master clock). 2 using PMT, which is rather buggy and bad. It'd really be good to combine this data with OS. Then we've got (most likely) 4 Windows users where QPC is returning TSC/1
  2. True. It's on the back burner for now as I've already left for Singapore; we'll see what the new employer's policy is. And yes, naming is especially hard for this kind of miscellany. jwlib isnt so bad, cbloom appararently reached the same conclusion with cblib Cool, thanks! I am looking forward to seeing this data.
  3. Yes, just to expand on this a bit - there would probably be some additional pain due to byte alignment and endianess (PPC is stricter/different on both counts). That's why we have always assumed only x86/x64 would be supported.
  4. janwas

    Game Error

    To expand a bit more on Philip's entirely correct reply: The message just means the platform/BIOS does not provide a HPET, so activating it understandably fails r10858 will indeed stop this from appearing, because we would no longer even check for the HPET (unless the user takes additional action by invoking aken_install.bat). I am not sure why the error code isn't resolved into an error string - that's worrisome and will be investigated tomorrow.
  5. Cool, glad you fixed it I am a big believer in symbol information in general. It is apparently possible to force a PDB to match: http://stackoverflow.com/questions/744870/how-can-you-change-an-age-mismatched-pdb-to-match-properly That looks too crazy even for my taste, though, so it'd be nicer to always commit PDBs of any code of ours that might possibly crash I don't think the AtlasUI symbols depend on wxW - did you have any particular problem in mind?
  6. Thanks for mentioning so. That is indeed the expected behavior on Win7 x64. The error message is misleading or false in that the driver is not unsigned - it is just not signed with a special Microsoft certificate. You can work around it by enabling test mode (see aken_install.bat) or launching the game with the -wNoMahaf command line switch or updating the game to the most recent SVN revision, which no longer attempts to start the driver. (It will still be accessible if you have used aken_install, though.)
  7. OK. If it's difficult to repro, perhaps we can see the problem from this crashdump once the symbols are available. It's great that you posted it
  8. Bummer, sorry to hear that. Presumably you were running with the latest binaries from SVN? Unfortunately we don't have symbols for AtlasUI.dll in SVN. @Philip - would you please add them?
  9. I think it would be enough to just report timer_Resolution. (Incidentally, a colleague asked to namespacify timer.h, turning it into timer::Resolution etc - any objections?) The current code only allows choosing one timer (the best available) and it'd be a spot of a bother to get them all. However, we can still deduce a lot from that - presence of an HPET can be gleaned from the chipset (i.e. CPU), and I would recognize the other timers based on their frequency (because the CPU frequency is also known). Let me expand on the 1 ms. That's only if somewhat calls timeSetPeriod and speeds up the ti
  10. Thanks for joining the forum to post your concern! I imagine the similar winring0 library also removed most of its functions after version 1.3 for these same reasons. Let's begin with the signature. You will find it to be basically OK and trusted by a root certificate, so the driver's integrity and source can at least be established. However, Vista and Win7 have apparently started requiring an additional bit in the certificate, and I'm not clear on which. "Basic Constraints" and "Key Usage" are marked with an exclamation point, so those are probably the culprits. "Digital Signature (80)" looks
  11. Hi! Unfortunately you'll need more than an integrated graphics card to run the game. It's most likely a video-related crash, possibly because the driver is erroneously reporting support for an extension we require. Please give it a try on a system with a dedicated graphics card and ensure your driver is up to date. If it still crashes, please also upload the .dmp file (very important for analyzing other types of crashes) and we'll have a look.
  12. These questions are all directed at Philip, but maybe I'll save him some time IIRC, the shaders were intended to simplify the code and reduce the number of combinations that had to be implemented. Shaders sometimes decreased the performance, but can also lead to improvements vs. equivalent fixed-function stuff. I do not know the rationale for the OpenGL3+ extensions. They're not currently in use - perhaps only for completeness or for other applications. We could print the extensions, but I am wondering as to the intended application. It would be possible already to grep for ogl_HaveExtension
  13. Let me add to that a little bit. The one-time conversion to DDS/S3TC is actually rather compute intensive if you care about quality, because it involves finding the optimal 2 colors for every 4x4 block, which is quite a bunch of combinations. If you suspect or would like to probe for other slowdowns, you use the TIMER_ACCRUE functionality documented at http://trac.wildfiregames.com/wiki/EngineProfiling . Anything that gets into the gigaclock range after a minute or two is something we should look at
  14. A minor note on telling whether apps are 32-bit: you can see the Task Manager process listing. If "Image Name" ends in "*32", it's running in 32-bit mode. That applies to about half of the processes I currently have running, so we're in good company
  15. That's a very good point. I don't see a way to get commented-out names into Doxygen. There are not THAT many unused parameters, but I agree they should be mentioned in Doxygen. The commenting-out idea is dead in the water as far as I'm concerned. Any ideas for better (but still short) names for the macros?
×
×
  • Create New...