Omsi 2 direct9 error
Just downloaded and installed Omsi bus sim 2 from here steam.
When I start the game I get an error and am forced to close.
ERROR= Fatal error- omsi will be closed-Error -While creating Direct 3d device direct 9 error-d3d err not available (-2005530518)
I am running on windows 8.1 64bit with direct x 11 installed from standard(dir x 11.2)
My drivers including direct x are up to date.
Any help or advice would be great.
Your system specifications would help a great deal here. 🙂
What as happened is this.I bought omsi bus 2 and got the directx 9 error.Now I have noticed my wtcc race and pro cycling manager games which also work with steam once worked about a couple of days to a week ago but now won’t work due to the directx 9 errors.Also I reinstalled Omsi bus 1 and tried to run through Aerosoft and that also as directx 9 error.
I have updated my graphics drivers/adapters and run the direct x web installer updates but no joy.Obviously something as gone wrong with my pc which may be from a windows update? or something I have done but I can’t recall any messing about with the system from me.
I really am at a loss.
My specs are Pc Laptop with windows 8.1-64 bit
Processor-AMD a4 5000 Radeon HD Graphics 8330 1.5 ghz
Directx 11(11.2)
Memory 8192 mb
Display 1366×768
In dxdiag- Direct draw,3d and texture acceleration all enabled.
Hope that is enough and if you require any more info I would be happy to do so.
Laptops and video drivers are hit or miss.. perhaps installing the original video driver may help.
WIndows update could have replaced it.. however most video drivers for laptops are custom made, are you sure you obtained your driver from the OEM manufactures website?
Does this laptop have any discreet video as well as the HD Graphics?
Hi RL and thanks for your help.
To update my driver I went the control panel way and to the Radeon adapter-Properties and auto update driver.
I have also used the dx diag tool to check if I have directx 9 installed and I have.Also in dxdiag it states I have directx 11.
Not sure about the discreet video and wouldn’t know where to look to find out.
I am now thinkling of rolling back the graphics driver to see if that helps?
PS: I am sure it is to do with some incompatability with a windows update?
I do not know who makes your computer, even though I would suggest you go right to the manufactures website and make sure there are no full video driver packages available there.
Uninstall the old drivers if they are in the Control Panel/Programs and Features, if they are there.
Install the official ones from the manufactures website.. or at the very least the original.
Hello people and thanks for the replies!
Sorry been awhile back on comment but been away for a holiday.
Since I have come back I have solved my problem.Seems it all came from a windows update which was an optional update which I should have never done.It was for my graphics and that is why all messed up after update.Maybe the update wasn’t patched properley for compatability with older games running directx 9.
Anyway I did a system restore and all is well again.
Thanks all for their help.
I never update my video drivers/audio drivers or any full package drivers from windows update.
Just a heads up on video drivers.. what is good for one game could be bad for another..
If you feel inclined to do a video driver update.. make sure you create a restore point.. and make sure you get the driver from the OEM site as most are custom for laptops.
Also if the video driver is working great for the games you play.. I wouldnt upgrade it. I’m using video drivers from many moons ago, in updates they rarely care about older or less mainstream games, often breaking them. I cannot count how many drivers has done terrible for Flight SImulator X, one of the main reasons I’m still with a very old driver.
I’m glad MS does not force these updates.. I cannot count how many has broken this or that, and there were even a few that they were forced to pull. I cannot stand windows update for another reason, the fact that they always display the same description for each patch. I have to go digging on each KB number to be sure of what it is/does.
In the end.. I’m glad you got it working again. 🙂
Источник
Direct X — d3d9.dll — consistently crashing since OMSI 2.3 update
1st Which version of OMSI 1 or OMSI 2 is being used?
2nd How often does the problem occur? How does the problem appear? (Error message, but OMSI stays playable / crash / freeze / . )
Since 2.3 update — Direct X d3d9.dll error, Direct 3D always crashing.
3rd What did you do before the problem occurs? (Place a new bus / activate scheduled driving /. )
Waiting at Uniklinik Aachen Addon map — Route 73 waiting for return journey
4th Which content do you use? (Maps, busses, . )
5th Which mods or plugins do you use? (SweetFX, . )
6th Logfile inside a spoiler.
767 15:10:42 — — Warning: Direct3D-Device lost!
768 15:10:42 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
769 15:10:43 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
770 15:10:47 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
771 15:10:47 — — Warning: Direct3D-Device lost!
772 15:10:47 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
773 15:10:47 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
774 15:10:51 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
775 15:10:51 — — Warning: Direct3D-Device lost!
776 15:10:51 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
777 15:10:52 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
778 15:10:55 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
779 15:10:55 — — Warning: Direct3D-Device lost!
780 15:10:55 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
781 15:10:56 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
782 15:11:00 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
783 15:11:00 — — Warning: Direct3D-Device lost!
784 15:11:00 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
785 15:11:01 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
786 15:11:04 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
787 15:11:04 — — Warning: Direct3D-Device lost!
788 15:11:04 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
789 15:11:05 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
790 15:11:09 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
791 15:11:09 — — Warning: Direct3D-Device lost!
792 15:11:09 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
793 15:11:09 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
794 15:11:13 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
795 15:11:13 — — Warning: Direct3D-Device lost!
796 15:11:13 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
797 15:11:14 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
798 15:11:18 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
799 15:11:18 — — Warning: Direct3D-Device lost!
800 15:11:18 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
801 15:11:18 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
802 15:11:22 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
803 15:11:22 — — Warning: Direct3D-Device lost!
804 15:11:22 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
805 15:11:23 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
806 15:11:27 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
807 15:11:27 — — Warning: Direct3D-Device lost!
808 15:11:27 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
809 15:11:28 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
810 15:11:31 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
811 15:11:31 — — Warning: Direct3D-Device lost!
812 15:11:32 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
813 15:11:36 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
814 15:11:36 — — Warning: Direct3D-Device lost!
815 15:11:36 — — Error: Privilegierte Anweisung: Reset DirectX — Unload RedLine
816 15:11:36 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
817 15:11:40 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
818 15:11:40 — — Information: Menu pos set
819 15:11:48 — — Warning: Direct3D-Device lost!
820 15:11:48 — — Error: Zugriffsverletzung bei Adresse 00406B14 in Modul ‘Omsi.exe’. Lesen von Adresse FFFFFFFD: Reset DirectX — Unload RedLine
821 15:11:49 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
822 15:11:53 — — Error: Zugriffsverletzung bei Adresse 00000000. Lesen von Adresse 00000000: P.Render
823 15:11:53 — — Warning: Direct3D-Device lost!
824 15:11:53 — — Error: Zugriffsverletzung bei Adresse 00406B14 in Modul ‘Omsi.exe’. Lesen von Adresse FFFFFFFD: Reset DirectX — Unload RedLine
825 15:11:53 — — Error: Zugriffsverletzung bei Adresse 100078FC in Modul ‘d3d9.dll’. Lesen von Adresse 00000000: Reset DirectX
7th System information (Operating system, RAM, CPU, graphics adapter, . )
Windows 7 fully updated
32Gb DDR3 RAM
i7 Haswell L3
GTX980 — 4GB GeForce NVidia
please reinstall your DirectX9 (from the main OMSI-folderCommonRedist) and the 4GB-Patch. This very important.
Then check, if your graphiccard-driver is up to date.
After all, restart your computer and try again.
I’m way ahead of you my man, I’ve done that already! Even re-verified the cache and re-applied the 4GB patch, Graphics Card is up to date, two days ago updated it, and installed from the CommonRedist folder. Still no go. It crashes out momentarily.
There are the same problems with Grundorf & Spandau with the standard-busses?
Please take a trip on Spandau with the MAN NG and look, if you have the same problems there.
After that please post your complete logfile (in a spoiler).
It doesn’t matter what map you use, when it comes to running it since 2.3 this issue keeps on halting gameplay.
It’s not good at all, i’ve been playing OMSI for 5 years and never had such issues.
Edited 2 times, last by LT586 ( Oct 26th 2016 ).
This is still happening, Regardless with or without the 4GB patch — When I say everything on my system is up to date it is.
72 19:19:32 — — Warning: Direct3D-Device lost!
273 19:19:32 — — Information: Direct3D-Device resetted!
274 19:19:32 — — Information: Reset State Matrices.
275 19:19:32 — — Information: Start Tex Thread.
276 19:19:32 — — Information: Init Red Line.
277 19:19:32 — — Information: Set Initial Render States.
278 19:19:39 — — Warning: Direct3D-Device lost!
279 19:19:39 — — Fatal Error: Direct3D-Device-Reset schlug fehl, Fehler: D3DERR_DEVICELOST
280 19:19:40 — — Error: O3D Mesh: Create — Direct9 Error: D3DERR_INVALIDCALL (-2005530516)
281 19:19:40 — — Error: In «vehiclesMB_O530_Faceliftmodelmodel_O530G_FL_3doors_Trail.cfg» there was an error in line 479!
282 19:19:46 — — Warning: Direct3D-Device lost!
283 19:19:46 — — Error: Zugriffsverletzung bei Adresse 00406B14 in Modul ‘Omsi.exe’. Lesen von Adresse FFFFFFFD: Reset DirectX — Unload RedLine
284 19:19:46 — — Information: Direct3D-Device resetted!
285 19:19:46 — — Information: Reset State Matrices.
286 19:19:46 — — Information: Start Tex Thread.
287 19:19:46 — — Information: Init Red Line.
288 19:19:46 — — Information: Set Initial Render States.
289 19:19:46 — — Information: Deativating TIR.
290 19:19:46 — — Information: TIR was not available
49601 22:51:20 — — Warning: Direct3D-Device lost!
49602 22:51:20 — — Information: Direct3D-Device resetted!
49603 22:51:20 — — Information: Reset State Matrices.
49604 22:51:20 — — Information: Start Tex Thread.
49605 22:51:20 — — Information: Init Red Line.
49606 22:51:20 — — Information: Set Initial Render States.
49607 22:51:31 — — Information: Menu pos set
49608 22:51:31 — — Warning: Direct3D-Device lost!
49609 22:51:31 — — Information: Direct3D-Device resetted!
49610 22:51:31 — — Information: Reset State Matrices.
49611 22:51:31 — — Information: Start Tex Thread.
49612 22:51:31 — — Information: Init Red Line.
49613 22:51:31 — — Information: Set Initial Render States.
49614 22:51:42 — — Warning: Direct3D-Device lost!
49615 22:51:42 — — Information: Refresh Tile: 44, mapsAachen Linie 33tile_1107_10764.map .
49616 22:51:42 — — Information: Direct3D-Device resetted!
49617 22:51:42 — — Information: Reset State Matrices.
49618 22:51:42 — — Information: Start Tex Thread.
49619 22:51:42 — — Information: Init Red Line.
49620 22:51:42 — — Information: Set Initial Render States.
49621 22:51:45 — — Information: Menu pos set
49622 22:51:45 — — Information: Refresh Tile: 95, mapsAachen Linie 33tile_1107_10765.map .
49623 22:51:45 — — Information: Refresh Tile: 96, mapsAachen Linie 33tile_1107_10766.map .
49624 22:51:55 — — Warning: Direct3D-Device lost!
49625 22:51:55 — — Information: Direct3D-Device resetted!
49626 22:51:55 — — Information: Reset State Matrices.
49627 22:51:55 — — Information: Start Tex Thread.
49628 22:51:55 — — Information: Init Red Line.
49629 22:51:55 — — Information: Set Initial Render States.
49630 22:54:23 — — Information: Try placing random bus:
49631 22:54:23 — — Information: Try placing random bus:
49632 22:54:23 — — Information: Try placing random bus:
49633 22:55:07 — — Information: Mesh SceneryobjectsAachen_XmodelX_Theaterstr_Form.o3d did not generate any materials!
49634 22:55:08 — — Information: Mesh SceneryobjectsAachen_XmodelX_Theaterpl_Form.o3d did not generate any materials!
49635 22:55:08 — — Information: Refresh Tile: 47, mapsAachen Linie 33tile_1108_10762.map .
49636 22:55:09 — — Information: Mesh SceneryobjectsAachen_XmodelX_Elisenbrunnen_Form.o3d did not generate any materials!
49637 22:55:09 — — Information: Mesh SceneryobjectsAachen_XmodelX_Bushof_Form.o3d did not generate any materials!
49638 22:55:10 — — Information: Mesh SceneryobjectsAachen_XmodelX_Bushof2_Form.o3d did not generate any materials!
49639 22:55:10 — — Information: Mesh SceneryobjectsAachen_XmodelPeterstr_Bushof_Form.o3d did not generate any materials!
49640 22:55:13 — — Information: Refresh Tile: 46, mapsAachen Linie 33tile_1108_10763.map .
49641 22:55:13 — — Information: Refresh Tile: 45, mapsAachen Linie 33tile_1108_10764.map .
49642 22:55:15 — — Warning: Busstop Kastanienweg/ found no exiting path!
49643 22:55:17 — — Information: Try placing random bus:
49644 22:55:20 — — Warning: Did not find texture file «textfeld.bmp»!
49645 22:55:20 — — Warning: Did not find texture file «textfeld3.bmp»!
49646 22:55:20 — — Warning: Did not find texture file «textfeld.bmp»!
49647 22:55:20 — — Warning: Did not find texture file «textfeld2.bmp»!
49648 22:55:20 — — Warning: Did not find texture file «textfeld3.bmp»!
49649 22:55:20 — — Warning: Did not find texture file «textfeld4.bmp»!
49650 22:55:20 — — Warning: Did not find texture file «textfeld5.bmp»!
49651 22:55:20 — — Warning: Did not find texture file «textfeld6.bmp»!
49652 22:55:20 — — Warning: Did not find texture file «textfeld7.bmp»!
49653 22:55:20 — — Warning: Did not find texture file «textfeld7.bmp»!
49654 22:55:21 — — Warning: Did not find texture file «textfeld.bmp»!
49655 22:55:21 — — Warning: Did not find texture file «textfeld.bmp»!
49656 22:55:21 — — Warning: Did not find texture file «VDV3.bmp»!
49657 22:55:21 — — Warning: Did not find texture file «text_vonNach.bmp»!
49658 22:55:21 — — Warning: Did not find texture file «text_vonNach.bmp»!
49659 22:55:21 — — Warning: Did not find texture file «text_vonNach.bmp»!
49660 22:55:21 — — Warning: Did not find texture file «text_Dep.bmp»!
49661 22:55:21 — — Warning: Did not find texture file «text_Linie.bmp»!
49662 22:55:21 — — Warning: Did not find texture file «text_Route.bmp»!
49663 22:55:21 — — Warning: Did not find texture file «text_vonNach.bmp»!
49664 22:55:22 — — Warning: Did not find texture file «textfeld.bmp»!
49665 22:55:22 — — Warning: Did not find texture file «textfeld2.bmp»!
49666 22:55:22 — — Warning: Did not find texture file «Mtx_Front_Fett_Eins.bmp»!
49667 22:55:22 — — Warning: Did not find texture file «Mtx_Front_Fett_Eins_OhneNr.bmp»!
49668 22:55:22 — — Warning: Did not find texture file «Mtx_Front_Fett_Zwei.bmp»!
49669 22:55:22 — — Warning: Did not find texture file «Mtx_Front_Fett_Zwei_OhneNr.bmp»!
49670 22:55:22 — — Warning: Did not find texture file «Mtx_Front_Schmal_Eins.bmp»!
49671 22:55:22 — — Warning: Did not find texture file «Mtx_Front_Schmal_Eins_OhneNr.bmp»!
49672 22:55:22 — — Warning: Did not find texture file «Mtx_Front_Schmal_Zwei.bmp»!
49673 22:55:22 — — Warning: Did not find texture file «Mtx_Front_Schmal_Zwei_OhneNr.bmp»!
49674 22:55:22 — — Warning: Did not find texture file «Mtx_Front_einzeilig.bmp»!
49675 22:55:22 — — Warning: Did not find texture file «Mtx_Front_ohneLinie.bmp»!
49676 22:55:22 — — Warning: Did not find texture file «Mtx_Linie.bmp»!
49677 22:55:22 — — Warning: Did not find texture file «Mtx_LinieFront.bmp»!
49678 22:55:22 — — Warning: Did not find texture file «Mtx_Seite_einzeilig.bmp»!
49679 22:55:22 — — Warning: Did not find texture file «Mtx_Ziel_Fett_Eins.bmp»!
49680 22:55:22 — — Warning: Did not find texture file «Mtx_Ziel_Fett_Zwei.bmp»!
49681 22:55:22 — — Warning: Did not find texture file «Mtx_Ziel_Schmal_Eins.bmp»!
49682 22:55:22 — — Warning: Did not find texture file «Mtx_Ziel_Schmal_Zwei.bmp»!
49683 22:55:28 — — Information: Try placing random bus:
49684 22:56:45 — — Warning: Direct3D-Device lost!
49685 22:56:45 — — Information: Direct3D-Device resetted!
49686 22:56:45 — — Information: Reset State Matrices.
49687 22:56:45 — — Information: Start Tex Thread.
49688 22:56:45 — — Information: Init Red Line.
49689 22:56:45 — — Information: Set Initial Render States.
49690 22:56:56 — — Warning: Direct3D-Device lost!
49691 22:56:57 — — Information: Direct3D-Device resetted!
49692 22:56:57 — — Information: Reset State Matrices.
49693 22:56:57 — — Information: Start Tex Thread.
49694 22:56:57 — — Information: Init Red Line.
49695 22:56:57 — — Information: Set Initial Render States.
49696 22:57:10 — — Information: Try placing random bus:
49697 22:57:10 — — Information: Try placing random bus:
49698 22:57:19 — — Information: Menu pos set
49699 22:58:23 — — Information: Try placing random bus:
49700 22:58:25 — — Information: Try placing random bus:
49701 22:59:22 — — Information: Refresh Tile: 82, mapsAachen Linie 33tile_1109_10762.map .
49702 22:59:23 — — Information: Mesh SceneryobjectsAachen_XmodelX_Hansemann_Form.o3d did not generate any materials!
49703 22:59:24 — — Warning: Texture «SceneryobjectsAachentexturePontviertel3.dds» failed!
49704 22:59:26 — — Information: Mesh SceneryobjectsAachen_XmodelX_Kaiserpl_Form.o3d did not generate any materials!
49705 22:59:27 — — Information: Refresh Tile: 68, mapsAachen Linie 33tile_1109_10763.map .
49706 22:59:27 — — Information: Refresh Tile: 69, mapsAachen Linie 33tile_1109_10764.map .
49707 23:00:34 — — Information: Try placing random bus:
49708 23:00:34 — — Information: Try placing random bus:
49709 23:01:17 — — Information: Mesh SceneryobjectsAachen_XmodelX_Scheibenstr_Form.o3d did not generate any materials!
49710 23:01:18 — — Information: Refresh Tile: 83, mapsAachen Linie 33tile_1110_10762.map .
49711 23:01:18 — — Information: Refresh Tile: 84, mapsAachen Linie 33tile_1110_10763.map .
49712 23:01:26 — — Information: Refresh Tile: 49, mapsAachen Linie 33tile_1108_10761.map .
49713 23:01:27 — — Information: Mesh SceneryobjectsAachen_XmodelX_Normaluhr_Form.o3d did not generate any materials!
49714 23:01:28 — — Information: Refresh Tile: 50, mapsAachen Linie 33tile_1109_10761.map .
49715 23:01:29 — — Information: Mesh SceneryobjectsAachen_XmodelX_Zollernstr_Form.o3d did not generate any materials!
49716 23:01:30 — — Information: Refresh Tile: 51, mapsAachen Linie 33tile_1110_10761.map .
49717 23:01:39 — — Information: Try placing random bus:
49718 23:01:39 — — Information: Try placing random bus:
49719 23:01:40 — — Information: Try placing random bus:
49720 23:01:46 — — Warning: Direct3D-Device lost!
49721 23:01:46 — — Fatal Error: Direct3D-Device-Reset schlug fehl, Fehler: D3DERR_INVALIDCALL
Edited once, last by LT586 ( Oct 29th 2016 ).
Источник
Hi Mister Programmer » «!
Since last update the RSl helper dont work for me on my pc.
its appear all time after update this error:
«Zugriffsverletzung bei Adresse 000000000040CCBB in Modul ‘RSLHelper.exe’. Schreiben von Adresse 0000000000000000»
and after this many window Info fields are open simultan like from magic hands.
I do complet remove rsl helper from the pc.I load the correkt re initial Exe for RSL helper and run all things with Admin Rights.
I have a 4k monitor with 3840×2160 solution
on 150% Letter skaling.
RSL version: 1742
Raid version: 4211
Issue: Autoclicker feature stops working after some time, the bot will not start a new battle
Symptoms:
- There is enough energy to start a new run
- User is in the battle finished screen
- RSL Helper shows in status «Waiting for battle to finish»
- Manually starting the battle will not help, you will be stuck again when the battle is finished on the client
- Closing client will NOT close RSL Helper
- Closing RSL Helper after closing client by X button is impossible. Only killing process through Task Manager would work
- Navigating between tabs in RSL Helper will cause an error «Zugriffsverletzung bei Adresse 0000000001138A8F in Modul ‘RSLHelper.exe’. Lesen von Adresse 0000000000000000»
Possible cause: either a memory leak or it has to do something with changing input language in Windows (have 2 languages set up).
Just tested with a different language. Switched to non-English lang and observed how the bot will act when it finishes the battle.
Result: the battle is started without any problems with the different language selected as an input language in Windows.
I have same issue from 1-4 steps…
- when I choose a hero icon —
@aermilin what languages do you have? and you talking about switching windows language? (or ingame)
For me, this behaviour occurs when RSL is not the active window in the foreground.
@Dwza English and Russian. Windows language (namely I’m switching to the other window i.e. some messenger). And I already tested the fact that language has no effect on RSL Helper. The cause is probably somewhere else.
what am i doing wrong?
Put the RSL-Window to the front…
Put the RSL-Window to the front…
I tried, but despite where the RSL window is found, the program refuses to autoclick
ok, may this si caused because of russian system language. i’m not sure if the pathes may contain cyrillian letters or so… but fact is, you both use russian as systemlanguage. so that has to be proved.
uhm i got exactly the same issues in english language .. can’t understand everything was perfectly working yesteday but ..
Edit: i just launched the helper and everything seems to be clear without any changes so.. hope you guys too
Dwza
added
the
bug
Something isn’t working
label
May 21, 2021
ok, may this si caused because of russian system language. i’m not sure if the pathes may contain cyrillian letters or so… but fact is, you both use russian as systemlanguage. so that has to be proved.
maybe the whole thing in graphic quality of the game? or frame rate limiter? or resolution of display?
after some manipulations with these parameters, RSL helper starts working, but after restarting the program everything stops working again …
you may be able to suggest settings for the above settings that are recommended for RSL helper?
by the way, I noticed that program always works from this place, but after the first battle it stops working
@aermilin were you able to solve your problem?
I faced the same issue like @aermilin @neorv86. In my case it happens only if I switch from EN to RU while the clicker is running. Btw, I have Ru set as the default lang and my windows interface is in RU too. So when I switch back to English the clicker works fine again. Weird 🤔
@doubleniki not weird, RU or Chinese are not supported.
These languages have special characters that the helper cannot handle.
@BlackHawk3000 by switching I meant switching the language of the keyboard layout, not the language of the whole system 
It is also worth mentioning that I do not have ru characters in the path to the application folder. I can only guess how the clicker works internally, but I guess it shouldn’t depend on the keyboard language. Or am I wrong?
no thats possible.
But if you get the error message like aermilin, then reinstall with the newest version. That should help.
Important, delete the complete installation folder!! The Helper has problems with old files.
- close, RAID, Helper, Updater.
- uninstall the installed Helper
- go to the installation folder and delete everything except the config folder (default directory: C:Users AppDataLocalProgramsCommonRSL_Helper_X64).
- download the current helper (pin here in the channel)
- install with admin rights
- pay attention to your installation path!
- run the updater
- close the updater
- start the helper and have fun!(Bearbeitet)
For a complete fresh installation
just use the link: https://bit.ly/3yGOqiY
@BlackHawk3000 actually I didn’t receive any error message. the clicker just couldn’t rerun a battle when I had ru keyboard layout on. Anyway, thanks for help.
I faced the same issue like @aermilin @neorv86. In my case it happens only if I switch from EN to RU while the clicker is running. Btw, I have Ru set as the default lang and my windows interface is in RU too. So when I switch back to English the clicker works fine again. Weird 🤔
tried to manipulate the keyboard layout, and you were right, the program starts working if the layout is English. I`m surprised and grateful for the hint!
this till not working for me set all for english from czech and nothing 
I faced the same issue like @aermilin @neorv86. In my case it happens only if I switch from EN to RU while the clicker is running. Btw, I have Ru set as the default lang and my windows interface is in RU too. So when I switch back to English the clicker works fine again. Weird 🤔
tried to manipulate the keyboard layout, and you were right, the program starts working if the layout is English. I`m surprised and grateful for the hint!
For me, too, when changing the layout, the program starts working
@BlackHawk3000 actually I didn’t receive any error message. the clicker just couldn’t rerun a battle when I had ru keyboard layout on. Anyway, thanks for help.
what key do you have to hit when you want to replay a round when you keyboard layout is set to RU?
on englisch its R, is it the same on RU layout?
on englisch its R, is it the same on RU layout?
Everything is correct R, nevertheless with RU layout the autoclicker does not start the next battle, only on EN.
I believe this is related to this issue
I close this thread because there are to many different issues inside here, please open a new one if you have some issues.
Thank you.
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrer_1Busfahrer_1_Berlin.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrer_1Busfahrer_1_Hamburg.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrer_1Busfahrer_1_London.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrer_2Busfahrer_2_Berlin.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrer_2Busfahrer_2_Hamburg.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrer_2Busfahrer_2_London.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrer_3Busfahrer_3_Berlin.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrer_3Busfahrer_3_Hamburg.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrer_3Busfahrer_3_London.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrerin_1Busfahrerin_1_Berlin.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrerin_1Busfahrerin_1_Hamburg.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrerin_1Busfahrerin_1_London.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrerin_2Busfahrerin_2_Berlin.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrerin_2Busfahrerin_2_Hamburg.hum
humansAddOn_DLP-Vol-6_KI-MenschenBusfahrerin_2Busfahrerin_2_London.hum
ich habe berlin X10 und Hamburg. Muss ich Da dann nur London Löschen oder berlin auch ?
the tool is used to view the ped models and edit its attributes …..
i checked all the files …. but none were with read — only attributes …. i wanted to get the ped model to use it to get a player model …. any recommendation for any other tool ???
i want to get only the head model of a ped …. so it would bt quite useful if any tool was available for stuff like that ….
That is going to take you more work, you will need an IMG editor, look for the peds index and extract TXD (texture) and DFF (3d model), if you just want to edit the texture, any graphic editor but MS PAint will be of use, but for peds you will need 3D Studio Max or G Max, this last is freeware, and get GTA Kam’s Tools, which is in the topic with the same name in tools forum, i recommend you to look for tutorials about 3D Editing, specially animation, if you want to edit PEDs, some of these information i for you to know
thanks for the info … i just thought the model of head and body are available separately …..
Mc Simmo — the name of the editor is simply » Pedestrian editor »