NakedSquirrel
-
Posts
313 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by NakedSquirrel
-
-
(((FIXED))
I haven't noticed any FFB with Il2. Inputs work, Spring centering works, and centering strength works fine, and I have FFB selected in the options. I do not notice any feedback when firing weapons, flying in turbulence, or when flying near or into stalls. Should I be seeing input messages in the log when running the BrunnerDX program?Set the Arduino joystick to 0 in the settings in \IL-2 Sturmovik Great Battles\data\input\Devices.txt
Used the delay in the program to make sure 0 was bound for axis and not the Brunner
FFB works like a charm. Thanks for the program!
Just leaving these posts up for anyone who runs into the same issues with setup.
-
(((FIXED))
Arduino not showing COM Ports
Running the initial setup and clicking upload firmware I get the following message Init You have the latest Version Specified COM port name '' is not valid. When I select Detect Ports nothing happens, and when I try to select 'connect' I get: The PortName cannot be empty. Parameter name: PortNameI'm surprised how many of these micro USB cables I have laying around. Most are only set up for charging and not for transferring data. After the 5th cable I found one that worked lol
Just leaving the post up for anyone who experiences the same issue.
-
-
I have an error with the F14 Pilot bindings where the Y-axis is disabled and a red exclamation appears next to the Y axis. There are no modifiers attached to the axis in settings, and I do not have any curves. This error does not seem to affect other aircraft, and I have no issues in other sims. I've tried searching the forums but couldn't find any advice that helped fix this bug.
If I hover my mouse over the exclamation, no conflicts are listed.
So far I've tried deleting all keybinds, repairing, trying different usb ports, updating joystick firmware, and even deleting all of my user files and completely reinstalling the game to a different hard drive.
Deleting the keybinds and rebinding everything will work temporarily, usually until a game or PC restart, but I've also had this error reoccur mid flight, where the y axis completely stops working.
Hardware is a Virpil TM50 base and Constellation grip. Warthog Throttle. MFG Pedals.
I thought it might be the Virpil stick (since obviously that is the one I usually use as y axis) but it doesn't what I bind to the axis.
This error started after the update that added Jester LANTIRN capability. I do not know if that is related. It crops up in both DCS regular install and DCS Open Beta.
-
I have an error with the F14 Pilot bindings where the Y-axis is disabled and a red exclamation appears next to the Y axis. There are no modifiers attached to the axis in settings, and I do not have any curves. This error does not seem to affect other aircraft, and I have no issues in other sims. I've tried searching the forums but couldn't find any advice that helped fix this bug.
If I hover my mouse over the exclamation, no conflicts are listed.
So far I've tried deleting all keybinds, repairing, trying different usb ports, updating joystick firmware, and even deleting all of my user files and completely reinstalling the game to a different hard drive.
Deleting the keybinds and rebinding everything will work temporarily, usually until a game or PC restart, but I've also had this error reoccur mid flight.
Hardware is a Virpil TM50 base and Constellation grip.
Edit: I should add. This error started after the update that added Jester LANTIRN capability. I do not know if that is related.
-
Unfortunately, static templates retain their position on the map.
It is still useful for making bases/fobs, but they will always be in the same place. So if you want to move them you have to manually drag all of the objects by hand.
If you want to save a template, make sure it’s the only thing on the map when you save because the save function will save all objects on the map.
-
I am hoping to create some helicopter missions for MP that involve troop transport, but I don't want to actually add active AI entities to the map, at least not for very long periods of time.
I would simply use CTLD, but AI tend to cost quite a bit of resources when it comes to bandwidth and CPU, so I would really like to limit the amount of time they are actually on the map and active. Static objects, on the other hand, are pretty much free (except for maybe the GPU load of rendering multiple 3d objects).
I have two scenarios in mind.
One is a simple evacuation/relocation mission, where helicopters ferry troops and civilians out of one area and drop them off at another designated point.
For this, I figure I wouldn't really need AI, I could just activate/deactivate static objects using flags so the players can have a visual cue of their progress.
The trouble is I couldn't get the "Static Activate" trigger working, partly because I don't see any way to cue a static as 'late activation' and there isn't any static deactivate trigger.
I figured set internal cargo would work for this one, but I couldn't seem to get that working in MP.
The other mission is a simple "We Were Soldiers" style scenario where helicopters ferry infantry and cargo to an area, and perhaps pick up some weight after landing to represent ferrying out casualties.
For the drop off I could maybe use CTLD, but I'm not sure how to control/remove the spawned AI. I guess I could find creative ways of murdering them by having them run off to the woods to triggered explosions or some unkillable units that can gun them down, but I would really just prefer to 'delete' them when they run out of view. Trouble is to get them to run out of the LZ. AI will sort of move to engage enemy, but I need something a little more elegant that isn't going to confuse AI door gunners and players.
Does anyone have examples or suggestions that I could use to create these scenarios?
I'm still pretty novice when it comes to .lua and MIST, so any help would be appreciated.
Thanks!
-
Is there a way to map an axis as button presses without external software? I recently acquired the new VPC constellation which has an axis thumb switch. There are some planes I would like to use this for trim or sensor control, but I’m not sure if it’s possible to bind it this way.
-
Same issue with crashes for me, both in MP and SP, but the timing is fairly random. Running the game in VR, no full screen no MSAA, no mods.
-
On 4/15/2021 at 3:55 PM, Frag said:
Ironically, I asked for the same thing earlier this week in another thread. It is difficult to believe that we have all these maps now and that the static objects in the editors are the same for the last 10 years.
The objects are available! Why not making these available in the editor?
Sorry I was looking for a similar post on the 'search' function.
It looks like the WW2 assets have added a few things, but it would be nice to get some map objects as useable static objects in the ME.
Sandbags would be nice >.>
or even a hesco barrier.
-
My G1 died on me, but extended warranty allowed me to upgrade it to a G2.
I think the G1 was just fine, but I very much enjoy the improved contrast of the picture, lenses, and the new motion controllers. Games, especially flight sims, seemed somewhat washed out due to low contrast on the G1. I don't think it's a deal breaker, (not sure if it really justifies spending $600+), but I'm very happy with the G2 so far.
Long answer short, if I still had a G1 that worked just fine, I would wait.
-
Syria, Persian Gulf, and the two WW2 maps added a lot of new buildings, bunkers, and scenery. Is it possible we will see some of these as static objects in the future? It would be nice to be able to place and use some of these in the mission editor.
-
6
-
-
I can't get the FLIR to repeat on my HUD. I have the FLIR switch on. Night mode on. Snensor select R to show FLIR on the MFD. Sensor select down, and all that happens is that my hud gets slightly dimmer... no FLIR repeat on my hud.
Any idea what I'm missing?
-
13 hours ago, Triggerjo23 said:
You yourself say you lose half or more of your Phoenix's per sortie. You are also assuming how people fly.
If you can't Crank or turn during a TWS launch then how can you descend?
A crank and boards to 0.8M is a valid real word tactic and it was used in the F14 too. Cranking to 0.8M preserves range and forces even greater flight time into the oppositions missile.
Who said the bandits have been beaming? Tracks drop when you are both nose pure. What does nose pure mean you ask? It means the bandit is in my HUD and I am in the bandits HUD.
Tracks drop when we are both above the horizon line and nose pure. This is not a look down scenario.
No one has been relying on Active launches. The issue here is not a lack of understanding or over expectation of the radar but a lack of comprehension of the problems people are describing.
RIO or no RIO the issue I am describing still occurs.
What you have to understand is that I am not saying it is the Tomcat either. It may just be a DCS issue as the same thing seems to happen on both the 16 and 18. I don't know however what causes it exactly but I know it is not intended as when testing engagement tactics in 1v1 PVP the TWS reliably tracks 100% of the time even when I crank and don't dive below the bandit and I slow down to 0.8M. However on a loaded server with more 4 or 5 people the WCS reliably does not track.
I know when a missile is lost becuase the bandit is too low or is manoeuvering too heavily or in a notch. The scanarios I describe are not those instances but rather instances when the WCS should have no issues. To go from 100% reliable tracking to 0% reliable tracking using the same engagement tactics just becuase server conditions have changed is a rather blatent issue.
I have tracks of F18 vs F18 practices but will have to dig for them. Also Tacviews but will have to dig for those too. Do remember that there have been updates to the 120 since those patches and sometimes changes do not actualy make it into the patch notes.
The missile launch not giving an engagement warning during Radar slave is very easy to reproduce folowing these steps.
1. STT lock the bandit.
2. TCS slave to Radar.
3. Radar slave to TCS.
At this stage the bandit should have a lock warning.
4. Hit PD or P search.
The bandit no longer has a lock warning. Symbology on the TID expresses Radar slave to TCS.
5. Launch Phoenix.
The bandit does not get an engagement warning and still has no lock warning. The missile can not be notched and will track as long as you have a TCS track. This works 100% of the time.
Easy to test, get an F14 pilot and RIO to go through these steps vs another player in the opposing aircraft. It will only work at or under 40nm as aircraft on the TID only seem to render inside of those ranges.PD gives the missile enough information to know when to go active? I thought you needed to be in RWS or TWS in order to get range data? (Edit: NVM Didn't see Naq's reply)
I need to play around with these missiles a bit more. I'm never sure when losing and regaining a lock if/when the missile might start tracking again. I usually just chalk a lost lock to: "Bye bye $500k" and get ready to toss another. They are great for harassment, and are nice for getting you in range for a WVR fight, but I feel you have to get lucky or catch someone completely off-guard to get a BVR kill.
-
16 hours ago, dburne said:
At anytime using Vaicom Pro, you can say " show options" and it will bring up the AI comms text. You just need to put a check in " allow options" in the Vaicom preferences menu.
Then if you want to use maybe the 2nd option, you just say " take two".
Comes in handy if you are not sure of the proper command to issue.
Saying "Show Options" is useful if you forget a command. Vaicom takes a little bit of time to get used to and set up right. I highly recommend going through some of the more common commands and making sure you have all the aliases you want. For instance air supply for me is about 3 or 4 similar phrases. "Chief connect ground air supply. Ground air supply on. Connect the air supply. Chief connect the air supply."
I won't toot too much about Vaicom other than it's a great program once you get it set up, since every radio/rio command thinkable is available at the squawk of a mic.
-
I hate to be the one, but are you running VA in Admin mode? I feel I've had issues with VA not in admin mode.
-
Do the default keys 1, 2, 3, work? I usually try to go for those when Vaicom is playing poopy with my keybinds, or I have an aircraft I haven't finished the keybinds for. I sometimes get issues with double keybinds. By default, I think Vaicom is set to use your PTT keys per aircraft, but I think there is also a way to make VA ignore your DCS binds and just use a specific button press. So if 1, 2, 3 work but your joystick isn't, that might be the issue. I've also had issues with a button going bad and not staying illuminated when I hold it down, so make sure it isn't your HOTAS
Are you running SRS as well? If so there is an option in Vaicom to help with SRS compatibility. Also make sure comms menu is off in the Vaicom options. If you still need to pull up the menu to see specific categories you can say "options" "Take 1, 2, 3... ect"
-
I have a lot of trouble finishing the 2nd mission. If I don't have my f14 practically inside the damned tanker, it will not give me a 'confirm precontact' I also don't seem to get the trigger that resumes the mission after I refuel.
-
Yea, there are a number of commands Voice Attack/Vaicom doesn't seem to like. "TACAN" and "Tune" are two I can never get to come up. I did the same and changed "tune" to "Freak"
I also gave up on trying to get the game to recognize "Stennis". I just call the carrier "Dennis" now. Dennis is a nice name for a carrier anyhow.
Anyone have any tricks to getting the program to recognize problem words besides changing the command?
-
You might be losing the mouse because you are clicking on the task bar at the bottom of the screen. I fix this by dragging the Windows task bar to the right when playing DCS. (Just click and drag)
-
Edit: I bet you're in RB-05 mode, that's the air to ground missile
There are at least 3 bomb master modes. PLAN, DYK and RR Chuck's Guide has a very good play-by-play checklist with pictures.
Once you have the basics down, I like to supplement with Crash Laobi's "1 minute DCS" tutorial videos. They're quick, dirty, and pretty funny. So you can listen to him rattle off all the steps in 1 minute and quickly figure out what step you missed.
-
NVM It looks like button 4 on my warthog isn't making good contact. I'll have to open it up and see if I can't fix it.
-
Do you still have the HOTAS controls bound in DCS?
What HOTAS are you using?
Are there any beeps or entries in the VA logfile when you have issues in DCS? Which module(s) are you flying?
The most recent aircraft I have tried is the Mig 21. I sort of had this with other aircraft in the past, but chalked it up to the game having 'quirks.'
I love the Mig, but I have recently needed to replace all the keybinds (new hardware)
I only get the "beeps" and recognition when I use the keyboard "1" key. If I try the "TX-1" which is bound on my warthog throttle... I only occasionally get a 'beep'
I feel I've had this issue before with the F14 (mic switch flicking on and off), but it is far more extreme considering I can't get any response.
Other aircraft "Sort of" had this issue for me. I've tried separating SRS from Vaicom in the hopes I could make a PTT for Vaicom alone... but I'm still getting some odd issues
-
I'm having trouble with Voice Attack It recognizes keyboard commands, but rarely recognizes HOTAS input in game. I have all of my mic transmit buttons bound, but the program only occasionally recognizes them when I am in game. It seems very inconsistent. When I am out of game it has no issues recognizing my HOTAS inputs. Anyone had this issue or a similar one?
Can we get rid of the radar?
in DCS: Mirage F1
Posted
I think for that, you would have to get a time machine and convince Northrop that the F-5 ought to be developed with a better radar system in mind.
The primary purpose of the F5 radar is for guns and sidewinders. It isn't BVR capable and can't even guide Aim-7 Sparrows.
The F1 has a reasonably good radar. The range on the Cyrano IV is more than double that of the Sapfir in the Mig21, but the Mig21 is a small target, even the modern jets like the f16 have difficulty picking them out at distance.
The Cyrano has look down capability, but that doesn't mean it's good at it. PD Radars have an easier time finding targets against an empty sky than they do in ground clutter. The mig21 is a smart design in that it doesn't let you point the radar dish down, probably with the idea that it wouldn't be able to distinguish contacts below you even if it could point down, so you're forced to search for targets above you.
Also remember that TL mode is limited to ~7km, so you'll have to be pretty close to get a lock.