All Activity

Hello Tom ! When assigning the pair of numbers as one decal, the Args for the first two numbers are 31 and 32, for a second number it would be 442. In the ME the sequence of the board numbers starts with the lowest Arg, so Arg 31 for the last two numbers is 3. The first number at 100 would then be 1 = Arg 442; 0 = Arg 31 and 0 = Arg 32. Unfortunately, I notice that you are not using the roughmet textures I created for the fuselage on the left and right. Worse still, you are not using any roughmet at all because the name for it is wrong. You have entered a SPECULAR assignment and therefore only the gray tones from your assigned texture are read. You'll notice this immediately if you copy the two textures "gdr-jg9-no591-right_roughmet.dds" and "gdr-jg9-no591-right_roughmet.dds" from my texture folder into yours. Since these don't exist in your case, you can do it without hesitation. The reason for this is that roughmet textures are automatically loaded with the base textures, and only if they exist can a false entry be loaded for them in the description of a livery. You can see what I mean by the inclination of the fender on the main landing gear in the picture.

Wow! 14 months ago and still no fix.

Hi Toninivak ! Love the Vamp !... much appreciate all your work on it. We have one (static) at our musuem -, happy to offer any help with numbers/ details /images of the real Mcoy if you are interested. D PS...is there a new DISCORD link? Tnx

I think you're right. I found Quadviews Fixed Foveated Rendering quite helpful back when I was running the HP Reverb. However it gives a lot more control and adjustments than the new Pimax feature. For the PCL - we would need the ability to offset the horizontal and vertical area. (Moreso the vertical area) like the QFVR app. I do like that Pimax is moving forward in trying to incorporate more natively into their system, saving us having additional separate process inbetween DCS and the headset, but at the same time it needs to be of benefit. I'm guessing this is solely focused on improving the super. I'm still on a version in the .20's (Can't remember exactly which). I've been waiting to upgrade for both features, and a stable version - but so far, reading in the following, it seems people are still rolling back. I guess if there's no new features that are going to help, and mine is working as is - I won't risk breaking it. I was contemplating taking the risk in trying to update if there was going to be any significant reward, but for now it sounds like there's no reward for the PCL.

Wow, I didn't even think to check the bottom.

TACAN got fixed but it seems like a lot of other stuff got broken. Prior to this update she flew great. Rock steady even with hands off. Now the nose wobbles all over the place like there's turbulence when the mission has no turbulence. When landing it's like the ground sucks her in, with no amount of collective cushioning the touchdown.

We still had this issue the 6th of august with the latest patch.

Since the great Greg also acknowledged it I think it might be an issue. I tried speeding up on straffing runs but made it worse for some reason. Thanks for the feedback guys!

Did some carrier "quals" today and just want to say the improvements to the flight model are very much noticed and appreciated. Thank you!! With the new PTO pack just announced I think it's about to get really fun with the F4U. Anyway one thing seems buggy, maybe not many of us use Auto Level, but I do like an IL-2 noob... to look at maps and flip switches and stuff. Anyway whenever you turn on or turn off AutoLevel the plane goes through what I can only describe as a total spaz out. Sometimes crazily oscillating the pitch with no end other than to reset and try it again. Hopefully just a tiny bug. my .02.

Is the grade sheet supposed to autofill, or is it meant for manual entry? My grade sheet is blank and I’m complete up to mission 5…

Possibly related to this older post:

Bye Phant

another thing that I’ve seen a lot on this Forum, are new users that think they know best how to run a software development company… maybe you are the exception and a true genius at running business, but so far I’m not impressed.

@Bojanglez Extremely disappointing to hear this Bo! I was able to fly many shot/traps with the Hornet this morning on the George and didn't suffer the violent rig-breaking shakes. I am running 2.9.18.12722 MT and noticed there is update waiting when I start DCS. What version are you running? Also do you have the Iraq map by chance?

Yes. This problem was fixed for the Elevator Trim on the Mosquito some time ago Two lines were added to the default.lua file in >>> Mods\aircraft\MosquitoFBMkVI\Input\MosquitoFBMkVI\joystick\default.lua" I expect it would also work for the Corsair and could be modified for the rudder and ailerons too.. This below is for the Mosquito gives two extra control options , Trim Elevator Nose Up 1/4 and Trim Elevator Nose Down 1/4, to use instead of the originals -- ------------------------------------------------------------------------------ -- Tail Trim Wheel -------------------------------------------------------------- { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = -1.00, value_up = 0.0, name = _("Trim Elevator Nose Up"), category = _("Flight Control")}, { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = 1.00, value_up = 0.0, name = _("Trim Elevator Nose Down"), category = _("Flight Control")}, -- MOD ADDED HERE { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = -0.25, value_up = 0.0, name = _("Trim Elevator Nose Up 1/4"), category = _("Flight Control")}, { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = 0.25, value_up = 0.0, name = _("Trim Elevator Nose Down 1/4"), category = _("Flight Control")}, -- ---------------------------------------------------------------------------------- There will be a thread in the Mosquito forum where you can thank the original poster.

Thanks. Clicking on the historical filter button fixed my issue.

I travel from one crash site to the other. I learn the history of Starfighters form JaBoG 34. These week I visited crash site of Oblt. Kelenk on the mountain "Hochgrat". It looks very different if you see the report about the last flight, and after you see an actual crash site. Anyway.... maybe it's offtop, but may I ask for these one Skin? Looks insane.

Okay, I am mad at Mil. The ASP-17 sight of the Mi-24 is also used by MiG-23, so, they could have given it a HUD!!!! Imagine having the MiG-23 altitude and speed scales! Altitude scales that switch between radar and barometric altitude!!! The artificial horizon!!! Could it be possible to mod this on???

That's probably a DCS thing then. Always challenging to track down intermittent issues.

Good idea!

Best post ever!

Maybe you enabled the Historic Filter on the Mission Editor? ... these assets are not yet compatible with that feature.

Hi, I am a beginner trying to use these assets. I followed the directions for installation. When I first used the mission editor to play around with the assets, they were there, and I ran a scenario where I got to use a couple of them. Then, as I go and select the assets for another scenario, they disappeared. I have no idea what I did to make that happen, but restarting DCS world and reinstalling the assets hasn't brought them back. They still show up in the encyclopedia, but not the Mission Editor. Does anyone know what the issue might be here?

This was also reported in this locked thread. This problem was also in the game years ago and they fixed it, but have somehow unfixed it and left it unfixed for two months and counting now.

Hi, I use the argument 32 - bord numbers, second digit to present the MiG23 MDL. Works good so far ... interesting as long as there is no switch in DCS ... Damage models next ... Hope it will be good. Cheers TOM