TurboHog

Looks like we were informed by the same website ;)

Hi, I was searching the internet for information about submunitions for the RBK series of clusterbombs. So basicly PTAB is HEAT and AO is anti-personnel. The number (2.5 / 1 / 10) indicates the weight of the individual submunition. So I compared this to DCS and this is what I saw: - The RBK500U that is supposed to include no less than 352 PTAB-1M only shows a few impacts - The RBK500 with 10kg submunitions is visually the same - The RBK250 with PTAB 2.5kg submunitions leaves more craters than the RBK-500U Maybe it is an effort to reduce FPS loss and the mechanics are ok? Or is there something wrong here?

It shouldn't make a difference in effectiveness, but this might narrow down the cause of the bug! EDIT: No, has nothing to do with it! tested the Su-25 gorund attack quickstart with adjusted payload and in all possible modes the hits are effective. This only makes troubleshooting more difficult because it's hard to see why it sometimes doesnt work. Hope this bug does not go down the line as one of those known but never fixed bugs. (Ka-50 HUD/Doppler repair, HEI rounds impact sound, Crazy Shkval etc etc.)

This bug sometimes occurs. I use the track below as an example: - At exactly 7:17:19, I hit an M113 APC with the 23mm rounds from the SPPU-22 gunpod. They are recorded and deal some damage. Nothing wrong here. - In the minutes following that attack I target a german TPZ vehicle that is standing on the road. You can visually see by the impact effects (watch him closely in freeview) that I hit him multiple times and from different angles. However, his health remains the same and the event log does not register the hits. Clearly a bug that I hope will be fixed soon! The file is called Su-25 tutorial because I made it for a friend who is learning the Su-25 Su-25 Tutorial.trk

Hi, I appreciate your efforts but could you please communicate this with me before you put up an entire different version of my mod. I want you to do this because in fact I've experimented with these things already by adding the required waypoint actions. Note that the non-NATO factions still don't work properly even though I've added callsign tables for Russian units. I will add this extra functionality in the next official version of my mod, although it does not add much.

+ if deviation caused by the aircraft's own magnetic field would result in 180 degrees differences, all compasses would point to your aircraft :lol: When you look at the inside of the canopy to your right, slightly behind you, there is a magnetical deviation chart (I think.) Interesting.

But you can't make them invisible to the player... The idea is that the player finds nothing at the supposed position.

Isegrim, it's not about info points or lines on the ABRIS map. It is about the known threats and their effective engagement range that are visible on the ABRIS. Fish, can you try to destroy or remove the threat by using a trigger after the ABRIS has booted. Because threats will remain visible if they get destroyed during your mission so it must be possible to achieve the same result by destroying/removing a vehicle by a trigger, unless an actual weapon hit prior to destruction is required. If the latter is how it works I don't see another solution. Try a trigger zone around the threat (Larger than their engagement range off course!). If Ka-50 enters, remove/destroy threat.

You will slide of the deck with your parking brakes on. If you are able to start the Ka-50 fast enough you might be able to get off the deck before you end up in the sea. But I guess the sea is where sharks belong...

Good, I will watch my clock then. Nothing about it in the latest version of the manual though. Or am I missing something? That should really be added because navigation can be really annoying if you don't know about this hidden feature.

It is a not-so-well documented feature that will hopefully bring us closer to a DCS level aircraft :thumbup:

Could an ED tester take a look? This is a very annoying bug because the HSI is your main navigation instrument in the Su25. I'm bringing up my post because I hope the fix can be included in the final update for V1.2.5 as V1.2.6 is going to take a while. EDIT: See this thread Just allowed some more time for the instrument to align and all seems fine now even after taxi! I thought the avionics were also very simple? Is this a hint towards DCS Su-25A then? But please, if you add features please document them. Nothing in the manual sais something about aligning your HSI/gyro.

But first of all DCS Su-25A :thumbup: In my dreams

I zoom in to scan an area.

In theory this should work: Make a group, active and unhidden. Deactivate group by a trigger (for example when the Ka-50 enters the area or leaves the FARP, or just a time trigger) I'm not sure if you can already deactivate the group on mission start as I don't know exactly when the information for the ABRIS is retrieved (mission start or during ABRIS boot). As the info on the ABRIS is not updated through the use of an active datalink, the threat, once deactivated, should still appear on your abris. Just like destroyed threats still show up. In case the game mechanics work differently and deactivating a group DOES remove the threat on the ABRIS, just make the units explode. The latter will definitly work but is not a really 'clean' solution. @ Lizzard. The threat is pre-entered and not updated as explained above.

It seems to happen only on the first few turns on the ground. Same thing happened in the Su-25T. Make a fast turn and stop turning abruptly. However it seemed to stabilize at the correct heading after a while. In the Su-25A you will be fed up with an error throughout your flight as there is no way to reset the instrument. Need some more people testing...

Mi-8Mtv2 in 1.2.6 YESSSS!!!!!!! :thumbup:

Ok. There is a bug here. See attached track file. Starting at Batumi, I check my true heading (305) with my indicated heading (305). Correct. Right after taxi (easy and coordinated turns as you can see) I line up with the runway and my true heading is 305 degrees again. Indication is way off. I then try to navigate to Kobuleti (HDG 026 from Batumi) and you can see I will never get there if I have to believe my HSI. Note that significant errors under normal conditions like these have nothing to with magnetical deviation. Looking forward to confirmation and eventually (V1.2.6?) a fix. Heading bug Su-25.trk

I've noticed this too, discussed it, and concluded that it is not a feature, but a bug that will hopefully be fixed for final release. I think there is some kind of conflict in the calculations sometimes. Sometimes it doesn't happen and sometimes you get a kick up, down, to the left or to the right. (The inconsistency itself reveals that there is some kind of conflict/error) There are no sudden torque/RPM/EGT changes as this happens. BTW in the video it is not that bad and I understand that it can be explained as an AFM feature. But I've seen much worse in all different directions.

Some bugs are known, but are apparently completely ignored by ED. - Crazy Shkval - HUD / Pulse-Doppler sensor not repairable Known for so long and I don't think they will ever be fixed. I will donate $10 to ED if they do. So basicly that means I will never have to donate anything.

Try this: On the ground turn 360 degrees during taxi. This resulted for me in an error of 100 degrees. Not good. It seems likely that your aircraft's movement (on the ground) has something to do with it. Further testing tomorrow (how it behaves in the air while turning)

Very strange. I start on batumi runway and it is fine. Then again I've had several occasions where it was absolutely incorrect. 10 degrees is way too much for magnetical deviation by the airplane's own magnetic field. I will further investigate and post screenshots to show you what the problem is.

The heading as indicated by the HSI is 10 degrees off. To reproduce this bug: - Start a mission. - Press Ctrl + y in outside view to show your 'real' heading. - Compare to heading on HSI. Error is about 10 degrees. Or use the Bearing/range finder on the F10 map to find bearing to a point and use your HSI. You will end up somewhere else.

Does your FC3 key work with the Su-25 standalone module btw?

I'm glad to see that so many people would like a DCS Su-25 or 25T. Maybe this gets ED thinking...