Izgud
Members-
Posts
67 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Izgud
-
Hi, I hope this helps explain what I am talking about: In the real thing, the pitch lines become flat when the aircraft is level. In DCS, they are always angled. Regards
-
Hi, The lines on the pitch ladder should not be angled when the aircraft is level. Please see the folowing gifs: Regards
-
-
MS FFB2 It would be great if this could be correctly configured by default:
-
Hi, Chizh Are there any plans to tweak the drag? Currently the 9M has a slightly longer range. Thanks!
-
F/A-18 Livery from Battlefield 2 For those of you who are feeling nostalgic... (for reference) Please be gentle - it's my first skin :) https://www.digitalcombatsimulator.com/en/files/3300831/
-
For those of you who are feeling nostalgic... (for reference) Please be gentle - it's my first skin :) https://www.digitalcombatsimulator.com/en/files/3300831/
-
I haven't taken a close look at the velocity vector yet, so we may not be entirely in disagreement.
-
Hi, I posted a thread about this here, but unfortunately interest in it seems to have died out. Regards
-
Hi, While interesting, there is quite a difference between 4 Hz and 4 MHz. It sounds to me as though this excerpt is referring to something akin to a clock. I thought it looked a little slow, so I measured it. One relatively easy way is to use a tempo tool like the one offered here. Simply tap a key for each change in HUD data - altitude during a rapid climb/descent, for instance. Using this method, and with the videos set to 0.25 speed, I am consistently getting 75 BPM (5 updates per real second) on the RL videos, and ~60 BPM (~4 updates per real second) on the DCS videos. Of course, video editing software can also be used. Please note that certain HUD elements such as the pitch ladder and velocity vector are updated more frequently and aren't part of my concern. I would be interested to hear if anyone else can confirm or refute these measurements. Do you think I am mistaken? Could you please explain why you think so? Thanks!
-
Hi, Sorry if this is a bit much, but I'm interested in helping us all get the best Hornet we can! Is it just me, or is the HUD a little slow? It's my impression that the refresh rate for most of the basic flight data (airspeed, altitude, vertical velocity, alpha, Mach, G) should be at 5 Hz as shown in all of the videos linked below, while it currently seems to be at about 4 Hz in DCS. Regards
-
Fix attached, OvGME/JSGME compatible. M-2000C heading tape fix (temp).zip
-
Great! :thumbup: With a DCS folder of 30.2 GB, 35,960 files, 4,036 folders: OvGME 1.2 ------ Snapshot 1: 3m50s Snapshot 2: 3m59s OvGME 1.21 ------ Snapshot 1: 3m27s Snapshot 2: 3m23s
-
no longer works The Ultimate DCS World JSGME Guide - If you use mods, you need this.
Izgud replied to Ebs's topic in DCS Modding
Delete JSGME.ini (the one in the DCS World folder, not the one in the MODS folder) or manually edit it, changing "Name=MODS" to "Name=_MODS". -
Very nice! Eases the complications with multiple DCS/JSGME installs and reduces my mod folder size considerably with the zip support. I'll be recommending this to my friends. Here's some feedback from what I've experienced so far: - When 'run as administrator' is required but not granted, no files will be copied but OvGME will show the mod as successfully installed anyway. I think JSGME might also have this problem; not sure if there's anything you can do. - Comparing snapshots could be improved with a resizable window or with word wrap off - see pic below. These are very minor points, though, and overall I'm very satisfied with your work :thumbup: Thanks!
-
Nice work! Do you know if it's possible to have altitude display in tens? (980, 990, 1000, 1010...)
-
Mi-8 main rotorhead and tail rotor animation
Izgud replied to Hueyman's topic in DCS: Mi-8MTV2 Magnificent Eight
I'm seeing the new main rotor animations (:thumbup::thumbup::thumbup:) but nothing for the tail rotor. Anyone else? -
Great job on the Mirage so far! It's coming along quite nicely, and I'm happy to see such a level of participation in discussions from RAZBAM during the beta process. Since you guys have been so receptive, I figured putting effort into a few minor suggestions would be worth my time. These little things have been bugging me for a while now: 1. Altitude readouts on the HUD should be reporting in tens (980, 990, 1000, 1010, etc). 2. HUD refresh rate, especially for speed and altitude readouts After further research, it appears as if this may be accurate for the variant modeled in DCS. I've seen some Mirage HUDs with speed/altitude refresh rates of about 6.3Hz, which makes for a very obvious slideshow effect typical of many HUDs, but others that are more instantaneous like the one in our DCS model. Input from other forum users still welcome! Instead, my #2 will be this: VSI and altitude seem to respond instantly to changes in actual altitude/vertical speed. Shouldn't there be a slight delay? 3. KCAS is incorrect - the calculation does not take temperature into account. This is something to look at in the FM as well if incorrect cockpit readouts were used for performance tuning. The altimeter correctly reacts to temperature. Attached is a mission with an A-10C and M-2000C side-by-side at 300 KTAS and 20,000 feet true altitude. Weather conditions are default aside from a temperature 50°C. Indicated altitude is lowered by a similar amount on both aircraft when compared to true altitude reported by the Ctrl+Y info bar. However, only the A-10C correctly shows a reduced airspeed readout of about 213 KCAS while the M-2000C seems to be using the simplified info bar "IAS" calculation of about 219 KCAS. The aircraft's systems and the Ctrl+Y info bar should only match when atmospheric conditions are standard (15°C). KCAS_vs_temp.miz
-
-
I noticed that the rotor turns considerably slower than it should (tops out at ~180 RPM) - is this by design or might this be fixed at some point? Might just be me, but it stands out next to other helicopters, especially at higher frame rates.
-
I can't get the pilots to appear in the cockpit with 2.0.2. I realize the update has been pulled, but wanted to be sure any potential issue is caught as early as possible for a future patch. On a side note: with the pilots gone, it's easier to notice that the seat cushions are still missing - have I missed a reason for this?
-
The problem with the pitot tube at high speeds (http://forums.eagle.ru/showthread.php?t=163611) has been fixed, but now the wing itself has a problem! Right wing only, as far as I can tell. Steps to reproduce are quite similar ------ 1. Reach high subsonic or transonic speeds 2. Pitch up and down while observing right wing
-
Thanks! :)
-
2.0.1.50747.33 I just added a 30 second track in the OP if you want to have a quick look.