Jump to content

wju

Members
  • Content Count

    70
  • Joined

  • Last visited

Community Reputation

20 Excellent

About wju

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    EU
  • Interests
    BoX, DCS

Recent Profile Visitors

804 profile views
  1. my GPU test was done not on native 4K but 2560x1440 native with DSR; windows screen resolution set to 3540*2160 and dtto in IL-2 setting, to be consistent, you should better delete my GPU record form the overwiev
  2. CPU TEST: 2020-11-23 18:25:08 - Il-2 Frames: 5040 - Time: 60000ms - Avg: 84.000 - Min: 72 - Max: 113 2020-11-23 18:27:14 - Il-2 Frames: 5013 - Time: 60000ms - Avg: 83.550 - Min: 71 - Max: 112 GPU TEST: 2020-11-23 18:32:27 - Il-2 Frames: 5508 - Time: 60000ms - Avg: 91.800 - Min: 73 - Max: 108 2020-11-23 18:34:10 - Il-2 Frames: 5574 - Time: 60000ms - Avg: 92.900 - Min: 78 - Max: 110 VR TEST: REverb G1 SS100%, i.e. 2200x2160x2 = 9.504Mpix 2020-11-23 18:41:02 - Il-2 Frames: 3203 - Time: 60000ms - Avg: 53.383 - Min: 43 - Max: 69 2020-11-23 18:4
  3. regarding topic "allocated vs really used VRAM" , there is a tool give a try! 😉 https://www.resetera.com/threads/msi-afterburner-can-now-display-per-process-vram.291986/
  4. you have two options: a) simple: just make visible main fpsVR graph window elsewhere on monitor and make printscreen; the system one, not IL-2 b) better one: in fpsVR settings go to advanced and enable frametime logging, the best by hotkey; then go to IL-2 and make record by hotkey; start/stop is indicated by bell fpsVR creates csv file with all relevant data for every frame; this can be plotted with your favorite tool; even stupid excel can be used, fpsVR built in histograms are nice tool, but have one significant disadvantage - they take into account whole session
  5. as a current Reverb user, I am also curious how they will manage steamVR/WMR layers
  6. fpsVR has now a hotkey to start/stop recording every single frametime, both CPU&GPU
  7. frametimes + utilization for GPU and CPU all cores
  8. Jason mentioned something like benchmark: cite: "I need to design a standard test for everyone and check results...." Maybe we should encourage him. Is it on the wishlist already?
  9. Hi all, the last fpsVR has a new hot key function to start/stop logging CPU/GPU frametimes and loads. One can find it under Settings/Advanced/Frames data logging. So far the beta only, but works. https://store.steampowered.com/app/908520/fpsVR/ EDIT: 2020_06_03: the logging function now available also in the last stable version
  10. this sometimes happens when You do not have centered position what usually helps is 1) "recenter seated position" in SteamVR 2) "fix floor" in Open VR Advanced setting 3) center position in game a good test is thant this initial "bad center position" causes snap turn is not working in expert mode, (i.e. your moves are limited to cockpit)
  11. this is true, your SW implementation is very good; but still, external ADC will be improvement; I hope, we will have it.. 😉 I can also add my own measurement: simple switch on from zero to cca half of the max overview: zoom at the beginning, one can see that blue pill refreshes value every 2ms: ( with 1ms USB exchange period ) zoom at the end nice thing is, that all eight channels are within three LSB (12bit resolution, i.e. within 32 on 16bit scale); unfiltered channel alters 3 bits, filter no1 2-3bits
  12. working on external ADC support? good news! 🙂 yep, the MLX90393 is the real beast! May I kindly ask You about multiple ADCs support? Is it in your pipeline? Is it even possible to have separate ADCs? The reason, why I am asking is in my previous post, hope it is obvious. My Russian knowledge is very limited so cannot read whole ru thread version, my bad.. well, I am playing with your last fw just now - so far i am impressed! 🙂 I have noticed your project this morning, and as I have some spare bluepills in my drawer, I flashed firmware and this is my f
  13. Hi WG_Magners! many thanks for sharing your effort! If it counts, I also vote for external ADC support, and if possible multiple ADCs, meaning not only MCP3204 but also 4xMCP3201 for example. The reason is to keep wires with analog signal as short as possible, important especially in case, when analog sources are not close each other. I have build my button box with 6 analog axes based on bluepill in the past, namely this project: https://opensimhardware.wordpress.com/pedal-button-controller/ It is working, but I was really suprised how noisy is the intern
×
×
  • Create New...