Jump to content


Founders [premium]
  • Content Count

  • Joined

  • Last visited

Posts posted by GridiroN

  1. Everyone who's been around since the beginning knows the classic trick... see a plane flying around slow, at 2K, with his nav lights on...he has a friend at 4K waiting for you to take the bait. 


    I've even seen it used offensively. Guy gets on your 6, turn your nav lights on, now the guy's thinking "crap, he must have a friend behind me, break off him!". Psychological warfare at it's best, lol...

    • Like 1
  2. Well, a major milestone for Bodenplatte was released released (and the work is fantastic). 


    With that said, a discussion on r/Il2Sturmovik reminded me of this thread. Figured I'd try bumping it and see if there's any news, or at least bring a bit more attention to this issue. 

    • Thanks 2
  3. I don't understand why anyone would be upset by this unless I'm grossly misunderstanding the post... 


    They're saying the server can either turn in a cheat to make planes artificially larger at distance or you can leave planes their realistic size of being super tiny and unspottable unless you know where they are... Because they would be. 


    The system seems to work perfectly well, especially for those with higher pixel density screens. 


    Flying with a small PPI screen is essentially the same as flying with a bad combat stick. If you're flying any of the ,3 major servers, I imagine they'll turn the spotting cheat off. Flying on Knights last night and I can see people fighting across the map at a different objective. 1440p. No spotting cheat. 


    Is this not what people wanted?

    • Like 1
  4. Before this turns into a history flame-war, I'm interested in getting some opinions on flying AGAINST these birds. Usually I'm an allied flyer, but I'm taking the opportunity to practice my D9 flying in such allied target rich environments and I find them really rather frustrating, even with entering the battle with a significant advantage, the P51 seems to have no problem at all getting behind me. One guy tonight actually saw me diving on him, flipped over on his back and just shot me in the face, which I found equally hilarious, and annoying.


    I've tried using the FW roll to my advantage but I seem to not be able to roll hard enough anymore with the G system to outroll the P51; I'm constantly falling unconscious. I've looked up some popular youtube "ace in a day" channels to see if perhaps I'm completely approaching the D9 wrong (i've been gone for months) and they're almost entirely bounces where the opposing pilot was simply unaware so not entirely helpful. 


    How do you guys find the weaknesses of these planes particularly the P51? I think the P38 is amazing also, but it's so large, I don't think it'll be quite as problematic for blue team as the P51 and Tempest.  

  5. 7 hours ago, Seb71 said:


    Yes, it is possible. You have two throttle options (with modes and without modes) in the "select grip" drop-down menu.


    I don't have a VPC throttle, so some fields are incorrect.


    Didn't see that. Thanks


    So, it seems if I set that profile, reload the bootloader with the other profile, and re-set this one, it works and the throttle is configured. Didn't work the first time for some reason, but either way, this did sort it out. Bit confusing though. 

  6. On 3/20/2019 at 10:39 PM, VIRPILControls said:

    It's very odd because I've had this reported a few times on the support portal  - I've jumped on via TeamViewer and managed to get it sorted so it seems that something is getting lost in translation! After clicking "Create Profile" are you clicking "Save VPC Device" at the top? Do you have multiple VPC devices connected?

    Thanks for the feedback guys - any help you guys can give will help us out :)


    Ok, I'm sitting here and taking a look at it again. This is what is happening: 


    1. I open file titled VPC_JOY_SETUP (vpc configurator)
    2. It instructs me to update the firmware
    3. I update the firmware successfully
    4. I go to "PROFILE" and select the M50 Base. I click "CREATE PROFILE" and the software tells me I cannot make a profile unless I also have a grip. I only have a throttle so this option is not possible.
    6. "LEGACY" folder
    7. I select the file "VPC Throttle_MT50 [PCBv07].cnfv07"
    8. I press "SAVE VPC DEVICE"
    9. I go to the "BUTTON" tab, and all my buttons are "inverted" and 4 of my buttons are registering as always activated, and button 37 is registering clicks every couple milliseconds


    If I go back and flash the prevous firmware and VPC configurator, the device works as expected, "out of the box". 

  7. 4 hours ago, VIRPILControls said:

    It's very odd because I've had this reported a few times on the support portal  - I've jumped on via TeamViewer and managed to get it sorted so it seems that something is getting lost in translation! After clicking "Create Profile" are you clicking "Save VPC Device" at the top? Do you have multiple VPC devices connected?

    Thanks for the feedback guys - any help you guys can give will help us out :)


    I can't try this tonight, but ill take a third look at this tomorrow after work!

  8. There is another gentleman who made a post about this on th eofficial Virpil forums. 


    The new firmware reverses all the buttons and basically breaks stuff. The advice has been that it's because the user did not set the profile. Many users have tried including myself to either import a profile, set it back to factory, or reset it, and nothing fixes it. 

    One guy got it working by manually going through all his buttons and setting them back up again, but this probably wouldn't work for me because my throttle on the new firmware keeps reporting a bunch of different buttons as being activated all the time. 


    I just went back to 190109. 


    It's been a long while since I've been posting videos. Figured I should post something and luckily had a clip worth sharing.


    A nice fight between me and two 190s. Luckily for me the second one is dealt with by a friendly La-5. My only regret is my gunnery is rusty as f*ck in this video,  he gave me a number of opportunities to kill him earlier but feels good to be flying in IL2 more often again!


    I've also synced it to Supermarine from the Dunkirk soundtrack, for extra coolness because that's how I roll. 


    Werd up to your mother.

    • Like 8
    • Upvote 2
  10. 11 minutes ago, Inkompetent said:


    I think that the last part is unfair. Yes, it is true that some are chronic complainers, but those can usually be counted on the fingers of a single hand. The larger group in the "regularly complaining" minority are guys who seek perfection. They do not expect perfection however. They just seek it. At least if we look at the "complainers" who have anything to come with other than a complete lack of sources outside of the Dogfights TV show. Just because something works fine we shouldn't stop asking how it could be made better. If that was the case we'd still be living in caves, without fire, and hitting each other with sticks and throwing poop at each other.


    You are right to some degree, sure. There's a larger pot of people who simply feel the sim is imperfect (and I do think it's important to think of this as a sim and not a GAME; game implies balance). The problem with that is, and I have always told people this, that if you think the sim/dev team is wrong, it's no use for people to simply complain on a forum. No developer needs or wants to hear that. I mean I have a youtube channel, and sometimes people will comment "this video was awesome". That's nice. But other times people will say "this video sucks". It's like...how does this help me please you? It doesn't help you get better content and it doesn't help me make content you'd prefer to watch. They have to provide examples and sources to the dev team. I believe the reason the FW190 got fixed was because so many community members were dedicated to finding real, credible sources that demonstrated the dev team was wrong. 


    11 minutes ago, Inkompetent said:

    Of course it must be tiring to not have the resources to work on all the things that people would like to see improved, and if anything having to be very selective with where the development work goes, but if anything it is the sim community's desire to seek absolute realism - even if presented in a simplified form, like for example the plane interaction in IL-2 - that is its driving force. A large part (most? all?) of the sim community are where they are because they want to immerse themselves in something authentic.


    I will also not disagree that a healthy degree of voting with your wallet is necessary. If 777 studios decided to become WarThunder, well people would just go play WarThunder. 


    11 minutes ago, Inkompetent said:

    I'm having issues on all servers currently, and in singleplayer. I like what the 3.008 damage model strives to achieve, but when I for example have to pelt a AI-controlled Yak-1 with 20+ rounds with my MG 151/20 for them to finally go down, then something is awry. I can't say what is wrong because I'm not sitting with the code or even decent debug feedback, but I can tell that when that isn't a unique thing but happens in almost every fight, then it doesn't match any factual analysis of WW2 air combat that I've ever come across/had presented to me.


    Jason says he and the team know what requires fixing so I'm going to assume if those kinds of things happen, they may already be working on a fix. If not, I'd suggest posting the video to forums. 

    I'm not criticising people for criticizing the team's work, I'm more suggesting that many people complain unconstructively, and considering 777 is owned by Jason, I imagine he is not beholden to shareholders and has no actual obligation to sit and listen. I have seen other games where the community complains so much all the time the development team literally just stopped caring. MechWarrior Online being a good example. 


  11. 24 minutes ago, Operation_Ivy said:


    Hey man, i really did not intend to insult you or anything. I am really trying to be civil about all of this but criticism is still allowed no?


    Concerning the different conclusions, i think you are aware of my bug report in my signature. You can also check out:


    - Rapid Fire: the Development of Automatic Cannon, Heavy Machine Guns and their Ammunition for Armies, Navies and Air Forces


    - Flying Guns: Development of Aircraft Guns, Ammunition and Installations


    Like i said already, i have no issue admitting when i am wrong if that's the case. As of right now, i have absolutely now idea on what the 20mm HE values are based upon. It is nothing game breaking and neither will it stop me from enjoying the game but i still considered it as wrongly modelled. 








    I think the issue is less that there's civil criticism and more that the criticism is never-ending. One of the hallmarks of the sim community, and what has been certainly evident to me over the 3 or 4 years I've been involved in the community is that there is a vocal group of users who wouldn't be satisfied even if you gave them a real plane, and sent them back to WW2. 


    Furthermore, the dev team either delivers what they say they will, or over-delivers by a wide margin, so why some people in this forum who've been around as long as I have always show constant doubt that they know what they're doing puzzles me. 


    As for the damage model, 80% of the issues I have with damage model are from Wings of Liberty being a potato server, and the other 20% are  because the guy was Elanski and can take the wings off a fruitfly with a ford focus. 

    • Like 1
    • Upvote 4
  12. Ok, I love the flying bathtub as much as the next person, and I'm sure the @Jason_Williams and the gang are busy trying to get the 262 to not explode the physics engine and various other incomplete things, but I humbly suggest that when the team gets some time, a damage system for the TSC be investigated. 


    I say this because A) I was just generally disappointed that there doesn't seem to be any reason to learn to use it properly when the plane was released but also B) cruising through some P47 threads it seems there are a number of people who've found ways of getting artificial performance improvements out of it by doing things the plane's official training videos specifically state not to do (like move the throttle below the TSC, and not move the propellor in step with the throttle, and/or using only the TSC to modify performance at sea level).


    That is my opinion, and that is all. 


    *Puts on fire-retardant suit*

    • Like 1
  13. On 11/30/2018 at 3:49 AM, F/JG300_Gruber said:

    There you go.


    The only things to change are :


    Joystick logical > Axis name X or Y as required 

                                    Precision : 10

    Axis Source > Type : Virtual

    Virtual axis params > Increase axis : use the physical rotary button (ex 61 for E1 when turning clockwise)

                                           Set to center : only if you want an instant reset to 50% (ex : 52 is the E1 press button)

                                          Decrease axis : the other rotary button (here 60 for E1 counter-clockwise)

                                          Step value : depends on the percentage change you want for each click


    For the step value, precision 10 (10bits) is going from 0 to 1023 at maximum value 

    If you want a 10% increase per click, set the step value to 102, for a 5% increase put 51


    Sorry if that sounds a bit dumb, but : like for any change, don't forget to actually load the modified setup into the throttle itself by clicking on the blue button "step 3 save device profile" on the top center of the window.


    After the reload you should be able to see the virtual axis movement in both windows.




    Some foot notes :


    Maximum allowable step value is 154, regardless of the resolution (precision) set to the axis 

    This corresponds to 15,04% of axis movement in 10bits (1024 values), 7.52% in 11bit (2048 values) , 3.76% in 12bit (4096) and so on.


    10 clicks at a 102 step value will get you up to 1020 and not 1023, so there will always be a slight difference (one more click will get you up 1023)

    this is not an issue if the difference is small enough (5 or less I believe ?), the throttle will read it at 100% anyways 


    If you are going for smaller increments per click (say 1 or 2%) it is better to get a higher precision on the axis (12bits) and take a step value that matches better the real value you would need for the increment.


    For example :

    in 10bit for a 2% per click you would need a real step value of 20.46 (1023 is 100%, so 10.23 is 1%) so either 20 or 21 will yeald noticeable error through the range

    in 12 bits , for a 2% per click, the real step value would be 81.9, so 82 should work fine




    I got it working man, thanks. Interesting technique...definitely increases the utility of the encoders.

    • Like 1
  14. 15 hours ago, F/JG300_Gruber said:



    I just remembered there is the possibility also to pilot two virtual axis (X and Y axis unused on the throttle) directly from the VPC software.

    The procedure is described in page 14 and 15 of the software manual and is quite straightforward.


    I'm able to get a 7th and 8th axis controled by the encoders and set up whatever % increase I want for each click of the encoder (up to 15% per click with a 10bit resolution). On testing, it is extremely reliable.

    There is even the option to set a 3rd button to reset the axis to the middle position (50%)


    That may be a very good and easy solution for people looking for two extra radiator axis on the throttle.


    (Though it wont solve the Pe2 problem, because prop pitch is NOT an axis on this plane)


    Hmmm. I tried to set it up as listed in the manual, and this didn't work for me. Can you post your settings?

  15. I was able to check out the new firmware. It's true that I was indeed on 2211 v2, where as this firmware is 2211 v3. I can report that indeed clicks in opposite directions do not drop 100% of the time anymore, but unfortunately, I also have to report that the encoder's tendency to skip clicks has increased a significant amount over v2. 


    I took E2 and turned it maybe 10 times or so, then changed direction, then a couple more times, changed direction etc... and the clicking is still very inconsistent. Something like:




    On v2, I only get 1 or 2 skips as long as I go in the same direction. 


    25 minutes ago, 216th_Retnek said:

    Same here, I would call it an inconvenience much more than a problem. Main complaint is the very retarded reaction of the Pe-2s prop pitch, water- and oil-coolers. It's possible, but one has to turn the knobs like mad to set the values. Like Gruber I tried to change some values, no success. The very same settings do fine for the He-111 or the Me-110. Turn one click left or right and the settings follow exactly 25 or 12,5%. Looks like the signals processing is different between the Pe-2 and the He-111. And the encoders way just fits to the German models.



    The PE2's propellor governor is very slow. This is the game's issue I think, not the hardware. 

  16. 2 minutes ago, VIRPILControls said:




    The software is the same for all our devices. You may have update 1 181122 - the version currently on our site is update 3 181122.  Our engineer made some changes to the upd3 firmware so that a click isn't lost when changing directions. Please try it out :)


    Very interesting. I will look into this when I return home. 


    It's funny... I have both this to look into and VKB asked me to take apart my Gunfighter and take some pics for them so they can sent me some new boards and cables so that is also on my plate... I should just open my own factory. 

    • Like 1
  17. 13 hours ago, VIRPILControls said:


    Please try out the latest firmware update on our site - some changes were made so that a click won't be lost when changing directions :)


    Where do I find that? There is no software for the throttle on your site. 


    Also is it 181122? Because that's the one the engineer gave me which was newer than the one my throttle came with and the engineer said it wasn't a firmware issue; they both do it. 

  • Create New...