Jump to content

=FEW=N3cRoo

Members
  • Content Count

    124
  • Joined

  • Last visited

Community Reputation

104 Excellent

About =FEW=N3cRoo

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

724 profile views
  1. Yep defenitely an issue and not reliable, i had tracer impacts inside the cockpit and didnt hear them
  2. 109 K-4s with DC and DB engines are rated for 1.45 ATA but they display cobat mode up to 80% throttle in regular flight envelopes. However the manifold is exceeding the 1.45ATA value with that setting especially in cold climates as you can see here with 1.5 ATA. My suspicion is that the engine mode display may only be tied to RPM not manifold
  3. Turning circle like a spitfire Highspeed response make structural breakup of the wings very prominent despite lack of evidence for such a problem Available ammocounts are missing aswell and not the standard ammocount for fightersweeps 1. On the first topic: http://www.wwiiaircraftperformance.org/tempest/tempestafdu.html http://www.wwiiaircraftperformance.org/tempest/tempafdu.gif Turning Circles FW.190 BMW.801D 41. There is very little difference in turning circles between the two aircraft. If anything a very slight advantage lies with the Tempest. Turning Circle 47. The Tempest is slightly better, the Me.109G being embarrassed by its slots opening near the stall. Turning Circle 28. The Tempest is not quite as good as the Mustang III. Turning Circle 35. The Spitfire XVI easily out-turns the Tempest. I'd expect it being close to equal with a D-9, yet a temepest in the vertical just runs loops inside the D-9 all day and sustains tighter turns better ingame, yet it should be easily outaccelerated by those big pedals of a Dora or FW. https://books.google.de/books?id=ZM6hDwAAQBAJ&pg=PA76&lpg=PA76&dq=tempest+D-9+dogfight&source=bl&ots=LP6KwfJQYf&sig=ACfU3U3qlg4PNKh4S6fzNBPEkHXvOlfsbA&hl=de&sa=X&ved=2ahUKEwiTo6Gw-7DlAhXQ-qQKHbGtDhoQ6AEwDXoECAYQAQ#v=onepage&q=tempest%20D-9%20dogfight&f=false swapping planes, I'm flying spitfire @4:25 slotting in, spitfire on tempest @ 7:00 slotting in, tempest on spitfire @ 11:10 As a minor point which may indicate a too high CL (missing PEC?) is that VNEs are unreachable next to a 10km 90° vertical dive and only then at below 2km. They may have been predicted speeds, I havent spend the time fiinding testflights on it 2. Ask anybody about the first few fight in the tempest, you can even rip the wings from flying level applying a bit quicker of a stiiickmove, I havent seen refences to wingfailures. It should also handle high speed stalls see point 45(II) https://ww2aircraft.net/forum/attachments/tempestv-pilotnotes-pdf.34006/ 3. We certainly have room for 870 plus the one unkown box not specified in this source other sources indicate that this is bigger than the 145 box https://books.google.co.uk/books?id=SMuTDgAAQBAJ&pg=PA134&lpg=PA134&dq=%22hawker+Tempest%22+%22ammunition+box%22&source=bl&ots=WBSruGU8ui&sig=ACfU3U0borp8nv_e42HBxhRUUUS1yt2IFQ&hl=en&sa=X&ved=2ahUKEwiY2tWyzZvlAhXMSBUIHRBeA0oQ6AEwC3oECAcQAQ#v=onepage&q&f=false https://cdn.discordapp.com/attachments/230625718092955649/633255999847006237/Screenshot_20180822-180021.thumb.png.b805f7b8c6f451f1d962d48c5af93163.png https://cdn.discordapp.com/attachments/230625718092955649/633255999847006238/Screenshot_20190814-224949.png
  4. Today on Kota, same view for the wingmen above https://youtu.be/vJAiOu_kqXE Today on Wings:
  5. I ran in to the twice in a row flying the K-4 in multiplayer, basically the engine sounded like to the side or behind me. Sadly i havent been able to replicate that problem as something has been triggereing this issue even tho it happened twice in a row on the same server. Detail where DC engine with default Payload Server: Knight of the air, Mission: PrebodenFantasyWinterD The second clip is particularily noticeable that the engine is to the side
  6. To an extend its on the server settings what amount of lag they tolerate in their config, but also ... I wonder if the server check the UDP packet order https://youtu.be/Xb94y8K3AsU
  7. still a thing, here's how this looks https://youtu.be/_4tYwsYC-sI just in case it helps here is the Pe-2s flight log the events are somewhat compressed, i dont know the logger beavhiour on this the video tells the story anyway http://il2stat.aviaskins.com:8008/de/sortie/log/4516566/?tour=50
  8. The A-20 technochat pops the oil overheat warning at 80°C which is the lower limit of the rated area. Its rated for 80-95°C maximum is 105°C even tho you can push to 120°C till your oil pressure can drop till failure. Note: the point where the warning pops up is right in between the two engines, since one is always a bit hotter bec of the generator load
  9. You can see it off to my right wing over the volga, its also visible in the tacview that i tossed in there tooghost tracers over the volga.rar
  10. Same thing still persists any lateral movement to the left half to any side is slowed down to ~ 50% Issue does not seem to be the case with VR, but it is the case for TIR I heard from opentrack users that this is not a problem If you need more info and cannot replicate tell us and acknowledge this issue
  11. The game since i remember had issues in MP with effects like contrail or tracers being stuck on a position in the map firing. This can be in case of contrails a static snowball hanging in the air- In case of Tracers, they will fire when iirc when the player that originally fired them is firing, atleast they arent continious in the appearance but may trigger repeatedly over the same spot The latter is still the case of 3.101b, I havent kept a close eye on the first if that is still the case i will update once i stumble into it.
  12. Hello folks, I wrote a python script that renames recording files with information provided by the statstracking websites. To make it useable for people without python 3.6 I packed it with pyinstaller into an executeable that will run in a console what does it do rename_and_link will check specified folders for ingame, tacview and video recordings for a match inside the statstracking websites of IL-2. When a match occurs it will rename the file to a format that will ease chronlogical analysis aswell as provide a txt file. The txt will contain events inside the recording relative to the recording start aswell as the link to the log and brief description of the entire sortie. How-To-Basic configure the json: Json entries that you have to set are the playernames and Path to your recordings, this can be the IL-2 track folder or any sort videocapture. Replace the windows path specific \ with a \\ or / like any other system uses. For videocapture you may want to check your video capture format is in "supported_formats". Since i only check the metadata from the OS it makes no difference what format you are using. Do NOT add .acmi to this since its already tied to .trk files This should already be the basics you need to do and now you could run the exe and get your files renames aswell as get a .txt file with all the events in that recording and a link to the given sortie. Further customisation options In "statspages" you can modify the websites the script checks aswell as customize the prefix the script uses for the given server. If you play on a server that is not listed and has a statstracking website, you can add this aswell as long as it uses the same architecture. (note that this is not the case for TAW neither does it specify the robots.txt) "overwrite_old_renames" determines if the script ignores files with the current "name_prefix" which is the last option in the json to customize, use this if you want to change already renamed files. any of the string can also be left empty if so desired, the file names generate are setup with name_prefix + server_prefix + date + mapname + (if recordingNo > 1): recordingNo/recordingsNo of that sortie + (if kills > 1): kills in that recording/kills of that sortie "mission_name_character_limit" cuts the mission name to the given size if its longer, this can also be set to 0 Notes This script has limited support with copies of files since it utilizes creation time and modify time provided by OS metadata. In case the metadata does not allow assessment of the duration of the file the starting point inside sortie will be noted in the txt instead of events. If you want to take a look at what you are running here it was packed with Pyinstaller you can unpack with https://sourceforge.net/projects/pyinstallerextractor/ (even tho i havent tried myself) Feedback and repository https://gitlab.com/N3croo/aviatools you need to register to gitlab but the repo is public alternatively poke me on discord N3croo#9083 where do you find it? https://www.mediafire.com/file/f64ycuq6lcc7tve/rename_and_link_IL2.rar/file
×
×
  • Create New...