Jump to content

yeikov

Founders [premium]
  • Content Count

    163
  • Joined

  • Last visited

Community Reputation

66 Excellent

About yeikov

  • Rank
    Founder

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

876 profile views
  1. yeikov

    Work in Progress

    I have always had the feeling that image looks smoother in game when HDR is enabled. So after your post I have checked an scenario with and without HDR (using Ultra preset), and indeed banding is much worse when HDR is off (mostly visible when looking at the sky, sea/rivers, or god-rays). To me it's almost not noticeable with it on. @HappyHaddock, I guess you have it off in your screenshots?
  2. yeikov

    Work in Progress

    The picture with the bridge looks really good. I don't see obvious banding, only some slight patches of colour in the mid-right section of the sky (in the mid-dark colours), but I don't know if those are only jpg compression artifacts. In the unmodded game there's a lot of banding at night anyway, most visible while moving; the picture certainly does not seem to make things worse in that regard.
  3. yeikov

    Work in Progress

    I see 1, 2, 3. Each number has a different background: - 1: Very dark (black) background - 2: dark grey (bluish tint maybe) - 3: less dark, with green-blue tint. Shows most visible compression artifacts around the number I hope it helps! ๐Ÿ™‚
  4. Have you tried those settings in the Kuban map? I think the sea is 3D (and chaging its looks with weather) only in that one, and that Rheinland's uses the same textures/properties as lakes and rivers.
  5. I would try the suggestion from FlyingH (deleting your devices.txt file), if you did not do it already. Do not replace it with any other file, let the game re-generate it.
  6. No idea. Can you zip and post your input folder? It's under [game folder]/data/input As I have the same controllers, I can compare the files with mine to see if there's something strange. And if you did not do it already since the update, disable all mods, restart your PC and try again. Some times I've had issues with joysticks not being detected, but it was in all programs and in Windows, not only in IL2. In those cases changing to a different USB port (if possible, direct to the motherboard, not through extension cards/USB concentrators) and restarting the PC always worked. If it worked before, a game re-install may solve it too. And contacting support may help too ๐Ÿ™‚
  7. I have a Warthog joystick (not the throttle) and MFG pedals, and both work in the current version (and in past ones). I don't use TARGET, just the driver and all the axes and buttons are recognised. Does anything happen when you try to map controls in IL2 to those devices, or you just get no response? Can it be that you have "mouse control" selected as control method? (in the input devices configuration)
  8. I don't know if you read the previous page of this thread or the Dev Diaries, but there is a workaround implemented by the devs some months ago, adding a line to your startup.cfg file: 3. Force Feedback joystick owners who experience stutters can alter the new value in startup.cfg that governs the maximum frequency of FFB effects polling to try to eliminate them (update_freq parameter in [KEY = force_feedback] section can be set to a value from 0.5 Hz to 10 Hz, example: update_freq = 10.0); Try with different update_freq values, combined with your camera view smoothness, to see what works better for you. It does improve a lot the stutters, at the cost of some responsiveness/lag in the shaking FFB effects.
  9. Hi, I don't know if the following issues are caused by the AI code or by the mission logic, but just in case I report them here, please let me know if it's better to do it in the AI section: Brief description: AI behaviour in Career missions: A. inefficient take-off maneuvers; B. Wingmen (usually last flight members) navigate after take-off at very low speed, falling behind of the rest of the flight. Detailed description, conditions: Both issues observed in Career mode: A. Some AI pilots make very violent and inefficient maneuvers during take-off, causing them to stay too low and fall behind of their flight. See attached track_1, recorded in autopilot. B. Almost in every mission in Career mode, some wingmen (usually the last ones in the flight) keep their flaps extended after take-off and navigate through the first waypoints at very low speed, causing them to fall more than 5 km behind of the rest of the flight. At some undefined point, they decide to throttle up and catch up. See attached track_2, where you can see the AI plane with flaps extended at 2000 m of altitude (which is already the nominal waypoint altitude, i.e. the plane is not trying to climb). Additional assets (videos, screenshots, logs): Attached Tracks.zip file with tracks and mission files: A_Track_1; B_Track_2 Your PC config data (OS, drivers, specific software): Game version v4.005 Tracks.zip
  10. No Career mode, but PWCG is a good campaign generator. There's also a static campaign and several loose missions, you can find the available material here: https://forum.il2sturmovik.com/forum/132-missions-and-campaigns/
  11. Brief description: Career "River crossing cover" missions: bombers consistently arrive after the patrol is completed. Detailed description, conditions: In Career mode, most or all of the "River crossing cover" missions I have been assigned lately are eventless, but when checking the flight log it always shows that the position we were protecting was bombed some minutes after the patrol was completed (on our way back to the airfield). Last occurrence today, in Kuban career, Russian side (see attached mission): patrol was completed at around 6:30-6:33 am, He-111 bombed the position at 6:40 am. This is now happening consistently for most/all missions of this type, but did not happen some months ago. Additional assets (videos, screenshots, logs): Example mission: river_crossing_cover.zip Your PC config data (OS, drivers, specific software): Game version v4.004 river_crossing_cover.zip
  12. As said above, looks like Vsync is not kicking in, do you have it enabled in game? Otherwise it won't work, as you have it set per application in your Nvidia CP. Also, although it's not related to tearing, you may want to try setting your Power Management Mode for IL2 to "Prefer Maximum Performance". In general for demanding games Optimal power reduces significantly the performance of your card (for my 1080 it creates lots of stutters).
  13. I'd suggest to check and try these two settings in the Nvidia Control Panel: 1. Max Frame Rate (not in game, but in the CP) - Disabled (or try 144 Hz to see if it overrides whatever seems to be limiting your frames). 2. Preferred Refresh Rate - Try both "highest" and "application controlled" to see if it makes a difference. For some reason, I need to set it to application controlled to have VSync working (I use also a Gsync monitor, but with VSync on). A reinstall of the graphics driver is also an option worth checking. If you used Nvidia Inspector in the past, you may have some residual profiles working in the background and those get reset after a reinstall. Also, just to make sure: do other games work at >60 fps?
  14. Please, I'd like to register here my request. For lights and tracers. And if feasible, to be able to configure the amount of scaling as an option ๐Ÿ™‚
  15. Thank you so much for this campaign, I'm still flying it and I think it's really good. Also had the same problem reported by others in mission 6 (circling A-20's before they reach the target ships). I landed and went on, but I'm reporting it in case it helps.
×
×
  • Create New...