nima2014
-
Posts
133 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by nima2014
-
-
Can someone confirm that we still have the issue of rudder trim being added up? I mean, if I put the rudder in a certain position, let’s say half deflection and trim it, it stays there (in game). My physical pedals are centered thereafter, now if I put the pedals a quarter in the same direction again, my understanding is that the new position of the in game pedals should only be that quarter deflection but as of right now, at least for me, it adds up the deflection so my in game pedals are now 3/4 deflected. I hope I made myself clear here and everybody understands what I’m talking about.
This was a present issue some time ago if I remember correctly, is it still present or just me stupid guy?!
-
Can someone else confirm that the RWR test is not working anymore?
-
1 hour ago, Kinkkujuustovoileipä said:
And the Force Trim still doesn't work?
Do you have Force Feedback enabled in the module settings?
Found the issue! It was a binding concerning the magnetic brake….so no brake, no trim…..easy as that .
Thanks for your help- 1
-
34 minutes ago, sleepycanuck said:
Just thought of something: go into the “Special” menu for the gazelle. There are separate trimming options for the stick and pedals. Maybe the option for the pedals is set to “No Trimming” for non-centering pedals.
Sent from my iPhone using TapatalkFound the issue. It was a binding concerning the magnetic brake…..so no brake, no trim. As easy as that .
Thanks for your help!
- 1
-
11 hours ago, sleepycanuck said:
Hmmm … not being able to trim. There is a “Trim Reset” function in the sim … check to see if you have this mapped to something that is always “ turned on”, like a switch on your HOTAS.
Also, when in the Gazelle, there are 4 switches in the lower right of the Front Panel that need to be on as well as the the Trim Actuator Switch, again on the main panel just below the oil temp gauge. All have to be on for the force trim and trimming functions to work.
Sent from my iPhone using TapatalkAll Autopilot switches are on (up position) as well as the trim actuator switch. I do even see the button press on the “in sim stick” when pressing the trim button on my physical stick, I also tried to click it with the mouse but no luck that the trim stays in place.
I‘ll check the bindings once more.
Maybe, it is an issue that I’ve bound the same trim reset to the pilot as well as to the copilot (even if it’s not pressed)?!
- 1
-
On 2/25/2024 at 3:55 PM, sleepycanuck said:
Hello to the Polychop developer(s) and thanks for making a very cool and fun module; really enjoying the updates of recent months!
(Please note: when ED released the latest update, with the unified version implemented I did a clean install of DCS World.)
I do have an issue that has cropped up since the last update: the binding of the X and Y axes to the Roll and Pitch control for the Gazelle.
The issue is that any of my other controllers that have an X and Y axis are also bound to the Roll and Pitch control as well and interfere with the desired controller. To be clear I have gone through each of my controllers and used the "Clear Category" function to remove any default settings, then set the desired controllers to the desired functions. Even though the other controllers no longer indicated activity in the "Adjust Commands Menu" lists they are still actively bound to Roll and Pitch. From my testing of other modules I don't see this phenomenon repeated, just in the Gazelle.
Also, a small glitch of note: the bug "Floating Clip from Pilot 3D model present on Mike variant" is back.
Kind regards,
Tom
My controllers:
flight/cyclic grip: TM Warthog, connected to Virpil MT-50CM2 base
throttle/collective grip: Virplil Throttle MT-50CM3
Rudder pedals: MFG Crosswind v2
Aux panel1: Virpil Sharka-50 panel
Aux panel2: Total Controls MFBB
See above ... your issue may be linked to other controller axes interfering with each other.
Cheers,
Tom
Thanks for your reply, I deleted all bindings and set it up as a new one…so there should be no conflict between the new choosable positions. When pushing/pulling the stick & pressing the trim button, the white diamond in the control indicator does not move nor does the stick, all remains centered.
-
3 hours ago, Kinkkujuustovoileipä said:
Which trim option are you using in the Gazelle module settings?
I tried all three of them and now it is set to my personal default setting “center position”
-
Am I the only one whose Force Trim is not working at all? I’ve cleared the old binding (even though it was the right one & survived the update) and made it new. But neither the stick, nor the pedals stay in place where I want them to be. Checked the controls indicator and voilà, the white diamond stays centered. If I move the trim hat, the stick and the indicator are moving accordingly but with the force trim button it is not.
I’ve bound the Trim button only to the pilot section as the Copilot doesn’t have that binding.
any ideas what’s wrong?!
-
16 hours ago, BIGNEWY said:
Hi,
As we've said before, we're working on a new external light system that will apply to all aircraft
thank you
Good to hear @BIGNEWY, thanks!
-
2 hours ago, razo+r said:
Maybe the old fix still works, I doubt it though. Besides, it took ED years to reduce the visibility range from unlimited to what it is now. I just hope it doesn't take just as long to fix the final bit...
https://www.digitalcombatsimulator.com/en/files/3320413/
Thanks, I’ll give it a try! Maybe ED will improve/fix this in an future update
- 1
-
Hey everyone,
I don’t know if it is only a VR issue or even a known thing but the external lights are glowing like hell. If you put the position lights to full bright and doing a “F3 view” flyby, you’re seeing more or less just glowing lights all over the place, kind of only a light ball. Is there any way to fix this?
cheers
-
1 hour ago, RealDCSpilot said:
Fixed with the latest update!
Is it? I can’t press a button for the master arm toggle to stay on, it just needs to be pressed to stay in the on position, otherwise it’ll revert straight back into the off position.
-
First of all, thanks for the update :-). After yesterday’s update I’m having an issue where I can’t trim the pedals….anyone else having this also? I tried all three options for trimming and everytime they are returning to their center position
- 1
-
1 hour ago, BIGNEWY said:
module releases can only come with patches. It just depends if a new module is ready and has been tested by the QA team.
thank you
Alright. Thanks for clarification. Have a great day!
- 1
-
@BIGNEWY Just one question regarding the unified version and the respective patch cycle around every 6 weeks. Does this include module releases or may modules be released in between without a patch?
cheers
-
https://www.instagram.com/reel/C2SUhfZMjmW/?igsh=MWN2YmF3bzFkbWsxcg==
check this reel from ED if you can, there you’ll see the future kneebaord on the pilots left leg
-
According to this video, there will be no new FM, they’ll use the existing FC3 FM
-
28 minutes ago, Vibora said:
You will get these bindings:
Throttle Cut/Idle switch - toggle Cut/Idle
Throttle Cut/Idle switch - Cut
Throttle Cut/Idle switch - Idle
Throttle Cut/Idle switch - Cut while held pressed
You will need to use the latter one for the Warthog.
I do use a Winwing Orion 2. I have two buttons so I can use the “cut” and “idle” binding.
Thanks for your quick reply and effort to solve this issue .
Cheers.
- 1
-
7 hours ago, Vibora said:
We fixed it and will probably be included in next OB update.
Does this mean we will get two bindings? One for „off“ and one for „on“? Or just fixed the current binding?
cheers
-
No news regarding this issue?
-
48 minutes ago, BIGNEWY said:
Hell yeah, all off them and not only once .
45 minutes ago, hotrod525 said:If you guys "Cold Start" do you turn on the FCR ? Then do you "unpin"-it ? (UTIL -> MAST -> PINNED / NORMAL).
If FCR is "ON" and "UNPIN" then :
Go to FCR page, make the FCR your SIGHT, go to Single or Continuous Scan, i'll suggest "Continuous" as the radar dont "magicly pick up everything at one" it need time to scan and classify, well from what i've experienced. I recal Wags saying the FCR computer need 30 seconds to provide targetting info (or something alike).
To consider : LOS seems to affect the Longbow radar, no seeing trought building or deep forest.
Yes, everything done accordingly
-
I’ve tried it with a hot start and it worked better. So something related to the cold start maybe?
-
Same here, getting inconsistent contacts if any. Tried the instant cold and dark mission (I modified the mission to have the FCR dome) at Nellis and targets are roughly 6km away, no contact on radar screen. Tried to fire up the radar with the bit test and without. Sometimes the targets appear around 4km, sometimes at 6.5km and sometimes nothing even thought I’m hovering in the wide wide open, no obstruction or anything nearby. Tried the manual tilt and auto tilt function.
-
I’m looking for help. I’m using a G2 at 100% resolution and at bright underground’s, let’s say Nellis at Noon, the edges of the cockpit frames are flickering (F16 and F15E), but only on ground during taxi. As soon as I’m airborne all is good, but on ground you see the canopy rails flickering when passing by bright ground. I don’t know how to further describe this issue. Is there any change in my Nvidia control panel I can do to get rid of this?
Specs: RTX4090, i913900k,64GB ddr5, win11.
DCS Multithreaded settings: anisotropic filtering at 16x, MSAA 2x, the rest is at medium to high.
openXR is used with best frame setting option selected.
cheers
RWR Test not working?!
in DCS: F-16C Viper
Posted
Will try that, thank you!