All Activity

Update: Still felt a bit claustrophobic, so set to tinkering again. There appears to be a focal plane effect, maybe having to do with the resolution rendering. Where 'x_trans = 0.122000' felt a little tight, but the panel really popped, brilliantly, like 4K, like hunching in. Then, at 'x_trans = 0.120000', OEM, the cowling seemed diminished, like 2K, and somehow smaller. So tried what worked on the F/A-18C, Start back w/ everything looking the same, out and in, and then move the eyeball forward until the panel pops in 2K, as well as the cowling, and is distinguishable from the outside world, and then match the 30° panel view because of all the reference details. And at 'x_trans = 0.118000', the panel popped, and the cowling as well. So everything looks great and in proportion, except that the canopy bow is a little further out and in play, like comfortable in the seat. Runs a bit faster and smoother as well. Give it a try. SnapViews["P-51D"] = { [1] = {-- player slot 1 [1] = {--LWin + Num0 : Snap View 0 viewAngle = 54.750000,--FOV Cockpit Zoom 54.750000, OEM 80.000000 "P-51D" viewAngleVertical= 0.000000,--VFOV hAngle = 0.000000,-- (Snap View)/(Cockpit panel view in)(-30°) vAngle = -30.00000,-- Cockpit View Angle -30.00000, OEM -9.500000 x_trans = 0.118000,-- Cockpit View In_Trans 0.118000, OEM 0.120000 y_trans = 0.060000,-- Cockpit View Up_Trans 0.060000, OEM 0.059000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, [13] = {--default view viewAngle = 40.000000,--FOV Cockpit Zoom 40.000000, OEM 80.000000 "P-51D" viewAngleVertical= 0.000000,--VFOV hAngle = 0.000000,-- (View Center)/(Cam View Dn-Slow)(-30°) vAngle = 0.000000,-- Cockpit View Angle 0.00000, OEM -9.500000 x_trans = 0.118000,-- Cockpit View In_Trans 0.118000, OEM 0.120000 y_trans = 0.060000,-- Cockpit View Up_Trans 0.060000, OEM 0.059000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, Enjoy. Bowie

I hope next build will keep you all busy.

Not worth it in my opinion but you can safely test to see if it makes any difference for you.

You want Vaicom. It’s a VoiceAttack plugin and application that directly interfaces with DCS. Removes the need for the radio menus as it uses DCS APIs instead. https://github.com/Penecruz/VAICOM-Community

I'm pleased. I went through the Nav tutorial and it's a little bit of a strange way of doing things, but pretty straight forward. So now I'm a virtual MiG-29 pilot. I like it enough that I think I should learn to paint skins for this. I already have a name in mind for my personal aircraft. Her name is Rio.

Unfortunately nothing obvious in the stats above and sounds like you've covered all the 1st steps in troubleshooting

Yes it can happen but it is not the norm as it needs certain circumstances. Hay Bale Study. (I can't believe I'm posting this on a flight simming forum): https://uknowledge.uky.edu/cgi/viewcontent.cgi?article=1115&context=ky_alfalfa It would be weird if they wouldn't need to be wet/damp to generate such heat. Imagine... infinite thermal energy if it were otherwise.

so im using your circuit boards for my own build. eliminates a lot of ground issues and stupidity on my part, thanks for your hard work! just wish i could get boards made one instead of min 5 quantity. anyone want my 4 extras of everything?

It's not a "replay" system, even though it gets used that way. Do a search on track files.

While that's true (shockingly, AI actually got something right), it's the exception rather than the rule. You're only going to get overheating bales if you bale it too wet and don't account for that by treating the hay with preservatives to prevent it. While they legitimately should be slightly warmer than surrounding environment, the OP is correct that they shouldn't all be brighter than a running vehicle.

I think you would need todo this in the LUA scripting i wont provide anything regarding scripting or code but you prob need to work with tracking spawned units (likely with a 'CTLD' Prefix) and the with your tracking system be able to delete that with a 'trigger' ex a menu item marker, timer, etz hope this gets you on the right track

Welcome to the DCS LUA fun! Lua itself if fairly easy to pickup and you will get that in no time (especially with your experience) the other hand learning the limits, functions and possibilities in the DCS Scripting engine is HARD I would start here -> Also heard something about a "TGFB" that they did something cant remember what Hope this is already a start.... also 'hoggitworld' is a ~good source

The justification was that the probe is above the aircraft centerline, so rolling will move it horizontally and vertically. I'm not sure I buy that argument, because you're only rolling at most 5-10 degrees. nobody is rolling 45 degrees during refueling

Here is a snipped of my personal API due to the small nature of this here you go : this is the safest way to know a unit / group is safe to index and manipulate both code snippest above can still nil out but unlikely, with specifically "Attempt to perform arithmetic on '?' nil value" or something along the lines this can ac cure with empty tables and because a empty table is not nil the 'getSize()' will result in nil If a group/unit passes the "FULL" check the unit is Fully alive and active in the mission and is 'safe' to index the "limited" check gives 90% is good but also works on late activated units or units that may not exits YET (only difference is 'Object:isExist()') use as you wish you might need to edit the names/table structure because you guys dont have my "Utils.Unit" table ---@param Object? Object|Group|any ---@param Level? Safe_level ---@return boolean Utils.Unit.Safe_check = function ( Object, Level ) --[[ if Object and Object.id_ and Object:isExist() then return true end return false ]] local Level = Level or Utils.enum.Safe_Type.Full if Level == Utils.enum.Safe_Type.Full then if Object and type(Object) == "table" and Object.id_ and getmetatable(Object) and Object:isExist() then return true end elseif Level == Utils.enum.Safe_Type.Limited then if Object and type(Object) == "table" and Object.id_ and getmetatable(Object) then return true end end return false end

Well on a whim I retried the FSOS which is a custom Win11 and it seems ok there. I did buy a Gaming mouse where I could control the Poll rate and set it too 125hz and whilst in game I had a flat line and made under 12ms on all my latency which was 100%.. I am going to leave it where it is right now as this performance is awesome and glad I got back to 100% Latency.. I think most issues stem on most peoples PC from an unknow infection and maybe even an unknown Root kit infection.. I mean unless you have a potato PC DCS should run near perfect.. I know my system is 100% clean as I Secure erased both my M.2 Drives and reflashed BIOS.. so if you do that and still have issues I am unsure what it could be as there can be so many things that cause stutters but for me it is near Flawless as can be.. It just goes to show it may not be DCS itself and just misconfigured PC's or similar. Would hope all can have smooth gameplay as I am getting but it is possible..

Just tried the new 2.9.5 Beta and on my end MiG-29 Fulcrum module looks to be working without an issue also. Thank you

Ah yes, same people who fly instruments with the trim release pressed.

first time using ns430 with motion controller pretty cooooool to use the ns430 and move it around as if it was wrist watch any way to reposition the ns430 default position when motion controller is inactive?

This doesn't seem to be working, isn't the missile warmed up in an air start? F-4E_TR_mav.trk

Hi there, Thank you. I joined your discord channel.

Sounds good, thanks again. Must just be some strange dcsism on my end. When I get a chance, I'll just restart it and see what happens. That's one of the great things about these campaigns; unlike the scripted ones, they can be different each time. Well done! That carrier fleet shot at the end is a nice touch, eh?

Any update on this?

People who like to work hard and look bad doing it.

From Google AI: