Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

50 Excellent

About =IL2AU=ToknMurican

  • Rank

Profile Information

  • Gender
  • Location
    Southeast Murica, Hell Yeah.
  • Interests
    Flight sim - race sim (future), music.. stuff.

Recent Profile Visitors

706 profile views
  1. Title pretty much says it. This has actually been a long standing issue since kuban or perhaps earlier. Trim using a FFB joystick at one point a year or two ago worked completely fine in these aircraft, but all versions of the IL-2 and Pe-2 don't seem to work correclty anymore, requiring pretty much 100% nose up trim to fly level, and that's only after you hit speed. Otherwise it wants to nose down.
  2. Loving the update, for a lot of reasons, but most of all the view distance and visibility updates make me =D
  3. Restarted engines in the thing after throttling down too quickly, got just below about 500kph before I turned them back on and was back up to 630+ in no time. Feels like your only real chance at nailing another fighter is if they're flying rather straight and level or maybe climbing/diving but without turning. When you set the stab to tail heavy, you do get a little more control in a turn fight but I feel like it's just putting yourself at risk. After a sortie or two in it, I feel like if you get caught anywhere but landing/taking off you're flying it wrong. Even if you aren't able to line up a shot on a fighter who knows you're there when you're flying it to its strengths. I feel sorry for any bombers who find themselves in front of the guns.
  4. Ah sorry, I wouldn't know what to do there. glad that was all figured out by another odyssey user before me, personally. y6 should adjust the horizontal convergence, as described above the entry in the .vive file. I'd imagine lower is closer together and higher is further apart or vice versa. Might be easier to measure with the mask center (the black circles) set to 0.0. (x7) (1.0 is no black circles) In my odyssey the two black circles kind of overlap slightly on the inner curves but when I turn them off and zoom at objects it's pretty spot on, no double vision. maybe adjust in + -.05 increments until you're happy or fine tune from there. From the 10x settings in the .vive file ; horizontal zoomed view shift for convergence y6 = 0.5 ; vertical zoomed view shift y7 = 0.1  ;Xvalue for zoom mask center. Set 1.0 to remove it. x7 = 0.0 y7 adjust the zoomed image vertically.
  5. In your games folder, there is a new folder called users_settings, that folder looks like this kind of You want to rename user_keymapping_zoom.ini to user_keymapping_zoom.ini.bkp and then rename user_keymapping_zoom.ini.Vive to user_keymapping_zoom.ini By default, you're using settings for the rift. Be sure the its the _zoom.ini file that you backup.
  6. Me thinks maybe you forgot to uninstall or disable the mod before downloading the patch. 11.3 is still working with the latest version for me. I highly recommend finding jsgme or ovgme, as it makes managing mods easier, enable disable at will.. like before and after a patch.
  7. So, I hate to be this guy, but I'm pointing at the big yellow "Donate" button at the top center of your snip .
  8. It's kind of funny, seeing the same names argue against any point against particular features repeatedly, for which many of us have been flying on taw for years, and didn't really have much complaint and therefore no reason to come to the forums until cold starts came along, then new features that make it harder to spawn in and do anything, when the balancing of teams changes throughout the day. The people I fly with switch sides almost every campaign. I'm starting to wonder if the current campaign design is the result of a few people, repetitively arguing against any differing opinion rather than a collective of individual opinions. Frankly.. i don't come to forums complaining due to how I died in a video game most of the time. What I am noticing, is that these "balancing" features haven't done much in the way to change the fact that LW is the preferred platform of gameplay for the majority of this playerbase.. and to many I fly with, seem to hinder the over all fun of the experience rather than solve problems. For me it's not about winning or losing.. it's about having a good time with my friends, epic air battles and epic ground assaults. It's NICE to win, to have effect on the map, and when we have the numbers we aim for it, when we're light we might stay on the defensive. I'll even go as far as to say that the GAME being designed around early eastern front has more to do with imbalance than anybody's preconceived notions about other people flying against them. As a community it would be nice if people just owned up and alternated sides per campaign, but I don't think trying to shove that down anybody's throats is going to fix the issue. P.S. this video is from what is likely the last campaign that RED has won.. before any spawn restrictions were ever in place. I could be inaccurate about how many campaigns red has won since then, but my point's still the same. IMO - Don't fly alone, bolster your numbers. Outside of language barriers, reach out to people you see online on your team and find out what VOIP client they're using. Chances are you're more than welcome to join in on the fun if you aren't a poor sport. "The more the merrier." Personally, I like discord. Feel free to PM me to work out server arrangements and lets make stuff like the video above happen, even against overwhelming odds. P.S. I mean no offense to server admins, =LG= or any other member of this community. I do appreciate the effort involved in giving us the TAW experience as long I've been around. But looking at the total number of registrations for TAW, expecting 24/7 balanced gameplay is a long shot. You spread that out over worldwide timezones and the average person's amount of free time it's not a huge number. A balanced game is giving everybody the same option of plane to fly, painted different colors. And that just wouldn't be TAW >.< Flying red takes having the stones, and maybe some additional control bindings, keystrokes and knowhow beyond toebrakes and throttle, that once it clicks, is like riding a bike. I'm sorry if I've repeated myself, or if this seems out of the blue and I don't intend to hover over the forums after this. But be nice to each other folks, getting killed on TAW while upsetting, isn't the end of the world, and you have to ask yourself how you let yourself present the opportunity in the first place. Try not to let it happen again. Rinse. Repeat. *Last edit* It's extremely hard to keep my thoughts short and sweet here, as thoughts pop up later on the subject and wishing I had a solution myself, but maybe influencing larger squads to fly for the underdogs needs to happen at the point of server registration based on squad size and current registration count, maybe even based on timezone on a first come first serve basis. "Register as squad", "register to squad" or "register solo" so to speak. As it stands I can't blame people for hanging out waiting to fly with their wingmates, and a registration capping system might actually put the more experienced, more coordinated larger squads on whichever side happens to be the underdog and needs them the most. That appeals more to me than longer death timers, airfields that open and close as players join/leave server, and the possibility of server slots going unused when there are willing players. This could be further maintained with a minimum amount of flight time required per week or every other week to maintain an active account throughout the campaign, to make room for active players, even just a few sorties. - I've more than spoken my peace here and I'll leave the thoughts be for now. My apologies for it turning into an essay. See you guys in the skies.
  9. Airfields on red side on the back are closed due to attacks from tanks/aircraft. OUr only spawn point is closed because of the "balancing" feature of closing forward airfields when blue side is outnumbered. Oversight on this feature here, that I still find unnecessary. Red outnumbers blue during this timezone through the week, while blue spends most of the day crushing us. I personally, don't mind a loss but the airfield restrictions bug me.
  10. You are mistaken.. I will shred many LW aircraft with the 23 mm next map.
  11. Turns out to be a false alarm, sorry lufeneste!. Something else was causing my performance issues other than the mod. I think it has something to do with the way I launched the game or from alt tabbing or something but I can't be sure.. not the first time mixed reality portal/steamVR have caused a little funkiness. Just so happened to happen after installing 11.3 for the first time. The benchmarks in my last post seem normal but the hit to average framerate isn't really a big deal to me as I tune to run at a minimum of 45fps + motion reprojection anyway. Please forgive the misunderstanding and thank you for your ongoing work with this mod.
  12. And i've said I will already. So I'm not sure your point? Still..benchmark or no this performance issue is new to the latest version of the game and mod for me, where previously performance was fine regardless of which MP server I was playing. Like I said. When it's convenient for me to spend the time necessary to do this stuff. I'll provide such. There's also a post further up this page, where JG77_motoadve reverted to 10.6c due to framerate issues. Might not be related but it sounds similar to my experience, previous versions were 10.6.2 and 10.7. 11.0 was still bugged when I tried it and this versions corrects the anomalies and taw wasn't up yet so I wasn't really in the game much. I have some experiments of my own to do to verify something else is not going on as well. So it's not like this is going to be some 10-20 minute ordeal. Bare with me it sez. Bare with me. just using msi afterburner to benchmark the track file supplied with the thread lufeneste linked with my current settings WIthout Mod: 19-02-2019, 03:07:35 Il-2.exe benchmark completed, 9245 frames rendered in 123.047 s Average framerate : 75.1 FPS Minimum framerate : 43.8 FPS Maximum framerate : 90.8 FPS 1% low framerate : 41.2 FPS 0.1% low framerate : 30.3 FPS With Mod: 19-02-2019, 03:11:45 Il-2.exe benchmark completed, 7700 frames rendered in 121.125 s Average framerate : 63.5 FPS Minimum framerate : 43.9 FPS Maximum framerate : 90.8 FPS 1% low framerate : 39.5 FPS 0.1% low framerate : 30.5 FPS at most the difference in almost 2 seconds would be 180 frames rendered for results with mod. Min/Max 1% low .1% low all very close to eachother but a 12fps loss to average framerate. Something else might be going on however, as running the same track file, before disabling automatic motion reprojection my minmum framerate was down in the 30's and now that I'm actively checking all things performance, things feel better. This was before I started benchmarking with software I already have on my machine, so there might be another factor there. In monitoring my CPU and gpu usage however, after disabling motion reprojection in WMR, there are questions that come to mind I might have to inquire about in another thread. No CPU bottlenecking occuring that I can see, not a single cpu core breaking 40-50%, and I understand the 90hz refresh rate causing the gpu to cap at 80%ish usage, but I would expect gpu usage to go UP if the game causes my framerate to drop and instead my gpu usage is @ 70%ish when in the 70-80 fps range, and gpu usage lowers to about 45-50% when Im in a range of 45-50+ fps. This might be a limation of WMR's default asynchronous rotation reprojection, which I'll bug microsoft about as it's silly to not be able to completely disable such a thing for measuring performance. It could also just be a matter of optimization regarding drivers or Il-2, or a faulty installation of either. Before continuing on to the very specific benchmark using software that I need to d/l install and familiarize myself with as I use different software for those purposes, I'm going to run DDU, reinstall nvidia driver as well as back up my input device files and reinstall il-2 despite having disabled auto-updates in steam and having tried to be vigilant about disabling the mod before I let steam download anything for the sim. I also plan to make some track files made from the current version of the game, as it's kind of obvious the track provided in the performance thread is from previous versions. Along with this I'll record video of at least the IL-2 Mirror with on-screen display showing hardware usage, track files, and run benchmarks provided ddu and il-2 reinstall doesn't solve the issue all together. Will update - Don't go on a bug hunt just yet lufeneste. I might stumble on something else being the cause.
  13. Yeesh lol. That's a very specific performance test. I use your mod enough to want to help out if i can however. I will say, that I've been using the mod mostly without issue in MP since I got my Odyssey I think in summer or fall of last year even before upgrading my gpu, and usually on the TAW server as it's really the only place I fly in IL-2. There have been quite a few hotfixes since 3.010 so I'll even go so far as to back up my controls and reinstall the sim. That much should only take me about 10 minutes. I will state that I factory reset Win10 as recently as January, all drivers on my system are up to date, latest two being nvidia drivers 2/13 and z370 chipset drivers 2/12. Prior to the reset I would download new versions as patches were released to fix anomalies, but had no issues with performance using the mod prior to 11.0 and 11.3. Just the smoke being offset, and weirdness on the ground like everybody else. Bare with me on my results. I'll follow protocal of the linked thread as well as benchmark using my usual settings and software.
  14. No offense taken. It's a noticeable effect of enabling the mod while playing on the TAW server. Without the mod I maintain no less than 45 fps on the ground due to motion reprjection. , and am playing at 90 fps once I get about 2km in the air. With the mod I'm fluctuating betweeen 35-43 fps throughout the entire flight, which at least using my odyssey is a jittery experience being not enough frames for motion reprojection. Disabling GUI with mod enabled seemed to help out a bit but still not quite equal to performance without the mod. And when speaking of flying barebones il-2 no mod, framerates described above are with GUI enabled. Aside from the in-game FPS counter, the WMR motion reprjection indicator (Green, blue, light blue, or red square in top left corner of left eye) will flicker as the frames fluctuate below the 45 fps required for motion reprjection, as well as some jitter/lack of fluidity/smoothness when looking around. reprojection indicator never turns red as the frames are fluctuating rather quickly in the 30's-40's. The blue box just flickers. So no this isn't just a feeling. As far as track files provided with the mod, I wasn't aware there was one. But I'll take a look. I did a fresh install of the mod tonight before logging in to fly with my wingmates, noticed the same behavior, and things got smooth again when i exited the game and disabled the mod via ovgme and restarted. When i both have the time and feel motivated enough I'll record a video showing framerate comparisons and upload screenshots of my in-game settings along with track files. Until then just consider this me mentioning it with intent to provide further evidence when I can. I'm not expecting lufeneste to bust his butt trying to fix something just based off this or my previous post. I'll sit down and put some time into providing some tracks/videos and screenshots in the next day or so as well as see if disabling features with keyboard shortcuts has any effect.
  15. I wasn't asking you to make and maintain and make another mod, so much as being curious of how comparible the amount of work required would be. Zoom is all I really use it for so I was just asking. When I get some time I'll try to draw some performance comparisons between mod and no mod, after trying a fresh install of the mod through ovgme to ensure I didn't rename the wrong .ini file for my odyssey or something before enabling. At the moment the most i can say is last night I first ran without the mod, by accident, downloaded 11.3 and enabled and my performance just tanked. There's room for user error and I'll double check and correct myself if I'm wrong, while hopefully providing more for you to work with with track files, settings, and maybe some video showing framerates.
  • Create New...