Jump to content

guitarxe

Members
  • Posts

    209
  • Joined

  • Last visited

Everything posted by guitarxe

  1. Sorry if it's a stupid question, I am just trying to understand why I see the discount in the store, since I don't see any news about any sales, so I assume that my account got some kind of discount, but I don't know why or how long it will last. Today I bought The Channel map, Normandy 2.0, and the WWII Assets pack. Before I did that, I did not see this 50% discount on my account, but now the WWII (except the Mossie) are 50% off for me. I assume one of those that I bought gave me some kind of discount? Does anyone have any information about that? Is it for one-purchase only? Does it expire?
  2. I don't know what I'm doing wrong. I have checked in the map editor that the mhz frequency for Batumi is 131.00mhz. I set the radio preset for the aircraft channel "B" to exactly 131. When in the plane, however, with the battery running, I cannot talk to Batumi. When I press "\" and select "ATC", Batumi is greyed out.
  3. When I make changes to the P-51D controls, they don't seem to be saved when I next re-open the game. I figured out how to save "profiles", but it looks like these profiles are saved per controller. i.e, one for the pedals, one for joystick, one for the throttle, etc. So now whenever I launch the game I have to go into controls, click each different column for each controller, and load a saved profile for each. Not a big deal, but still kind of annoying having to do that every time. Is there no way to just save it as defaults somehow? Am I doing something wrong?
  4. Thanks! I was able to get it perfect. The sweet spot was 78% total fuel. Now I need to figure out why the radio frequencies for the airports don't seem to be working... I pre-set Channel A to 131mhz which is supposed to be Batumi, but it doesn't seem to let me communicate with the tower.
  5. I am using the mission editor, and I want to set fuel for the bird. I read that for correct aerodynamics, you are supposed to have 25 gallons of fuel in the fuselage tank. However, I can't seem to figure out how to achieve that when setting fuel for the plane object in the mission editor, because it just has a single slider for fuel, and not something that can adjust specific fuel tanks. I tried to eyeball it by hopping from the mission editor and into the game, and it seems that it will first fill up the wing tanks, and then start filling up the fuselage tank. So I tried putting it to full and then just removing 55 gallons (to have 25 remaining), but for some reason it doesn't put it to 25 exactly, more like 30 gallons. Anyone know how to do this properly?
  6. Thanks for the help all. It was the rudder trim and slippage that was throwing everything off. I was flying with very high slippage without realizing it and that's why none of the other trims seemed to make a difference. As soon as I corrected that, everything seems to be fine now. Is this still a thing? I do have a FFB wheel plugged in (I need it plugged in to use the the pedals as rudder pedals).
  7. Hi all! New to DCS, and to WW2 era planes. I've played some other sims before, but those don't compare to the level of detail and simulation as this. I'm starting to realize how much more involved flying a prop plane is compared to a jet like an A-10C or a Su-25. I am still trying to find some videos regarding general prop flying to learn better, but what I'm trying to figure out right now is how much should I expect trim to be helping. On other (jet) planes, I can do a few points of trim and it can raise or lower my nose, but with the P-51 I feel like even if I roll the trim wheel all the way to one side it doesn't seem to be enough to affect the flight dynamic very much. I still need more practice to figure it out but already I feel like trim is going to act very differently than what I'm used to in jet sims. Am I correct in that assumption or might I be doing something wrong already?
  8. But is the TM Warthog still top-dog for HOTAS? I mean, at least in that price range?
  9. I wonder if this would make MFDs (or at least just the buttons on the frames!) something that can be retained when using VR. Since of course you don't see your own fingers in the virtual world, you're groping blindly for controls, but if you have the mouse cursor there to guide you, and if you can make the alignment between VR and your real setup match 1:1, then it would probably make it work? Has anyone tried something like that?
  10. I need to upgrade my old PC, and so I'm looking into speccing out a new build. However I've been out of the game for nearly 10 years so I'm not very well up to speed about what's been going on recently. For example, I can tell for sure that buying a new GPU now is not a good idea because nVidia is expected to release a new series this year, so that can wait. But what about the CPU market? I'm looking to make a high-end purchase that will last a long time. I am thinking of the i9-9900K. Is it a good time for the CPU market right now or is there any shakeup expected to happen soon?
  11. Well this is still the right one, yeah? https://www.amazon.com/ThrustMaster-2960720-Thrustmaster-Hotas-Warthog/dp/B00371R8P4/ref=sr_1_1?dchild=1&keywords=x56+hotas&qid=1597721665&sr=8-1 Looks like you can sort of "pre-order" it before they restock. Hm, not sure if it's worth it, who knows when they will ship...
  12. Long time ago, I wanted to get the TM Warthog, but couldn't afford it. But back then it was going for about $USD 600 on Amazon.com. Now I look at it, and it looks like the "official" item is out of stock, and there are some other resellers and they are all for craaaaazy prices like close to and some even over $1,000 ! Does anyone know what happened? Does TM still produce the Warthog or is there now another product that supersedes it? (I've been out of the market for many years, I don't know what's changed).
  13. Is that really a defect? From the photos it just looks like where two halves of the mold come together.
  14. I find myself in a bit of a predicament, I want the TM Warthog but cannot currently afford one, and doesn't seem like I would until I've got more disposable income to throw around (few more years, plus my wife should be finishing college soon so that will help), but in any case I'm worried that it goes out of production and there will be no other product of the same quality to replace it, and it will go into legend and nothing as good will be available like it, kind of like the Logitech G27 Wheel and what was that Force Feedback Joystick from Microsoft, I forget the name now... Am I being silly and paranoid, or should I cough up the dough now while it's readily available and supported?
  15. Wouldn't it be up to whoever plans the mission and others higher on the chain of command that make the decision of what's cost-effective and what isn't? Then the only decision the pilot has to make in combat is how to complete the mission in the safest way. So even if it's just one truck, if the safest way to take out the truck is a maverick, then by golly it will be the maverick!
  16. Ah ok, yeah, but you want to keep all the other parts of the HUD the same size as it is? You don't want them any smaller? Because if you set the "new_k" value that I showed in the previous post to 73.5 or bigger, like 80, then the pitch ladder I think will be a good size, can you give that a try? I also can't actually see the pitch ladder on that screenshot, I think it's off to the site, a bit, you're flying in a strong cross-wind?
  17. When you spend the last 3 days modding the HUD rather than actually flying. ... or is that counter to the topic? Oops But I still love the A-10!
  18. Was watching a track of myself flying and let me tell you how surprising it was to see myself get blown up by an interceptor not 5 mins off the runway! That's obviously not at all what really happened! (and that sounds pretty hilarious when you think about it), but why does the track show something different from what actually happened?
  19. From what I was seeing it doesn't look like you can scale individual HUD elements independently, but maybe there is another way, I will see what's possible. Are you trying to make it bigger or smaller?
  20. Right, so this is all assuming DCS 1.5, if you are using DCS 2.0 let me know I will have to download it and check if it's all the same, but it probably is. It looks like HUD scale can be controlled by a single value in this file: \DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\HUD\Indicator\HUD_definitions.lua Someone had actually made a sort of "mod" for it - http://forums.eagle.ru/showthread.php?t=95797 , but that's not really required, you can make the changes on your own. Just be sure to backup any of the files you'll be modifying. For the HUD scale, open the HUD_definitions.lua file at the above path (use a text editing software like Notepad++ or similar for much easier use). Find this line old_K = 73.5 new_K = 73.5 It will be at the top of the file. The value you want to change is "new_K". Bigger values produce a smaller HUD font size. Smaller values produce a bigger HUD font size. For example: old_K = 73.5 new_K = 90 Will make the HUD font even smaller than default. And this: old_K = 73.5 new_K = 49 Will make it much larger, which is what I personally use. You can try a value in-between or whatever you want really, just play around with it until you feel it comfortable. Now to change the positioning of the elements on the HUD you need to modify different file. That whole info block at the bottom right of the HUD is actually two parts - waypoint information as well as the Radar Altimeter, and they are separate things in different files. The Radar Altimeter info doesn't really get cut-off so you can ignore it if you want to, but if you want the whole block to all line-up then you'll have to move it as well. Open this file: \DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\HUD\Indicator\HUD_NOCLIP_SYM_page.lua Find this block of code, it starts on line 70 and ends on line 104: AddHUDTextElement_Pos("Steer_Point_Number_ID", {{"steer_point_number_id_txt", 0.1667}}, {[b][color="Red"]70[/color][/b], -76.5, 0.0}, nil, HUD_DEFAULT_LEVEL, "LeftCenter") AddHUDTextElement_Pos_Formats("SPDis_to_go_Num_Targ_Elev", {{"SPDis_to_go_Num_Targ_Elev_txt", 0.1667}}, {[b][color="red"]70[/color][/b], -89, 0.0}, nil, HUD_DEFAULT_LEVEL, "LeftCenter", {"%s", "/", "%d", "DTS", "XXXX"}) AddHUDTextElement_Pos("Time_on_Target", {{"Time_on_Target_txt"}}, {[b][color="red"]70[/color][/b], -101.5, 0.0}, nil, HUD_DEFAULT_LEVEL, "LeftCenter") AddHUDTextElement_Pos("Current_Time", {{"hack_mode", 1}, {"Current_Time_txt"}}, {[b][color="red"]70[/color][/b], -114, 0.0}, nil, HUD_DEFAULT_LEVEL, "LeftCenter") HackTime = AddHUDTextElement_Pos("HackTime", {{"hack_mode", 2}, {"Time_to_Target_txt"}}, {[b][color="Red"]70[/color][/b], -114, 0}, nil, HUD_DEFAULT_LEVEL, "LeftCenter") What you are interested in here is the number I've bolded and colored red, which is "70" for all. This is the x-coordinate for the position of the element on the HUD. 0 in the middle of the HUD. So smaller numbers will move it to the left, and bigger numbers will move it to the right. If you fancy moving it to the left side of the HUD, then continue below zero into negative numbers. The value that I used to show on the screenshot was "55" for each. So in my file it looks like this: {55, -114, 0} Also if you fancy moving it up or down, then modify the second value. Again, the center of the HUD is 0 and by default it sits below the center so it's negative. To move up use bigger numbers, to move down use smaller numbers. Now after you move that, your Radar Altimeter reading will still stay where it was and this might bother you because then it won't align nicely with the waypoint info below it, so you may want to move it to the same horizontal position. To do this, open this file: \DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\HUD\Indicator\HUD_COMMON_page.lua Then find this code, it's on lines 1022 to 1027: AddHUDTextElement_Pos("Radar_Altitude_Numerics", {{"radar_altitude_numerics_txt"}}, {[b][color="red"]70[/color][/b], -64, 0.0}, nil, HUD_DEFAULT_LEVEL, "LeftCenter") And again change the value of the bolded, red-coloured part, which is 70 by default (same as the waypoint elements were). Change that to be the same value that you used for the waypoint values to make it align exactly on the HUD. I had mine at 55 for the screenshot, but you can use whatever values you want. Smaller numbers will move it to the left, and bigger numbers will move it to the right. Save all files and start the game and you should see your changes once the HUD is active and showing info (just use create fast mission and start at runway for a quick check).
  21. Is that an official extension for the TM Warthog? Outside of people sticking a PVC tube in there to make it longer that's the first time I'm hearing it can be extended. Just curious to know because I am eyeing it on Amazon, just waiting until some kind of sale comes up to snag it.
  22. Various elements of the HUD can be re-positioned and the HUD itself can be scaled. Let me clarify I am understanding the problem correctly, is this below what you are referring to? https://i.imgur.com/1ek4Nre.jpg And if we move it to the left a bit, will that be better for you? https://i.imgur.com/8pT8oyi.jpg
  23. Ahhh, that's how! Perfect! Thanks for explaining all that!
×
×
  • Create New...