Jump to content

Welcome to OZx Forum

Welcome to OZx Forum guest,

Wouldn't it be nice if I would call you by your name or nickname of your choice ? 

Like most online communities you must register to post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be apart of OZx Forum by signing in or creating an account.

  • Start new topics and reply to others
  • Subscribe to topics and forums to get email updates
  • Get your own profile page and make new friends
  • Send personal messages to other members.

timothyr673

Registered
  • Content count

    19
  • Joined

  • Last visited

About timothyr673

Profile Information

  • Gender
    Male
  • Location
    The Midlands
  • Interests
    OMSI, Buses (especially Nottingham ones), Trains, Model Buses & Railways, many other things...

Recent Profile Visitors

858 profile views
  1. OMSI SDK Programs Don't Work

    Cheers guys, I had to download the DLL and the SDKs worked once I'd put it in the SDK folder
  2. OMSI SDK Programs Don't Work

    Hello (again) I recently downloaded the inofficial OMSI SDK to use the object converter and the repaint tool, but none of the programs work. Instead I get an error saying: "The code execution cannot proceed because qtinitf70.dll was not found. Reinstalling the program may fix this problem." What does this mean? I don't think reinstalling will help seeing as I just installed it. I seem to be missing some random DLL file which is crazy seeing as my PC is so new......? Thanks.
  3. OMSI 2 Error While Initialising/On Startup

    Actually, scratch that last post, I found a solution. Right clicked on OMSI application, went to Properties, into the Compatibility tab and checked the box called "override high DPI scaling behaviour" and then selected 'Application' from the drop-down box below it. After this, OMSI runs as normal except for the menus like the main menu and the ALT panel are a bit smaller. (but I can deal with that, I think)
  4. OMSI 2 Error While Initialising/On Startup

    A recent logfile entry error: Invalid floating-point operation - Init3D: Creating device what does it mean?
  5. OMSI 2 Error While Initialising/On Startup

    I searched this part up online, and the articles I saw talked about updating graphic card drivers. I tried this but Windows says they're up to date. Then I tried reinstalling DirectX from the folder included in OMSI. Still Nothing : (
  6. OMSI 2 Error While Initialising/On Startup

    So am I right in thinking that the logfile is a text-based report of the most recent time OMSI was opened? If so then there's an error and a couple of warnings!
  7. OMSI 2 Error While Initialising/On Startup

    The Windows version is Windows 10 and if I remember rightly the PC has 8gb of RAM This is what I have in the log file, though I'm not sure what it means: ==================== Start logging ==================== Date: 29/01/2018 Time: 17:27:06 Version: 2.2.032 0 17:27:06 - - Information: OMSI is working in fullscreen mode 1 17:27:07 - - Information: TIR - looking for DLL path... 2 17:27:07 - - Information: TIR - DLL path not found - TIR disabled [0] 3 17:27:16 - - Information: Options dialog created 4 17:27:16 - - Information: Weather dialog created 5 17:27:16 - - Information: Profiles dialog created 6 17:27:16 - - Information: Time table running dialog created 7 17:27:16 - - Information: Start dialog created 8 17:27:17 - - Information: Menu 2 created 9 17:27:17 - - Information: Menu 3 created 10 17:27:17 - - Information: Tut dialog created 11 17:27:17 - - Information: Menu pos set 12 17:27:17 - - Information: Bro initialized 13 17:27:17 - - Information: Human engine initialized 14 17:27:17 - - Information: Forms set 15 17:27:17 - - Information: Captions set 16 17:27:17 - - Information: Screen ration set 17 17:27:17 - - Information: Init3D: BackBufferFormat = 22 18 17:27:17 - - Information: Init3D: Hardware vertex processing 19 17:27:17 - - Information: Init3D: Max iso = 16 20 17:27:17 - - Information: Init3D: Hal active 21 17:27:17 - - Error: Ungültige Gleitkommaoperation - Init3D: Creating device 22 17:27:17 - - Information: 3D initialized 23 17:27:17 - - Information: Direct sound initialized 24 17:27:17 - - Information: Create main manager... 25 17:27:17 - - Information: Veh array created 26 17:27:17 - - Information: CS initialized 27 17:27:17 - - Information: Station manager created 28 17:27:17 - - Information: OBB created 29 17:27:17 - - Information: Tex managers created 30 17:27:17 - - Information: Tex manager started 31 17:27:17 - - Information: Tutorial manager created 32 17:27:17 - - Information: Material manager created 33 17:27:17 - - Information: Scenery object manager created 34 17:27:17 - - Information: Human manager created 35 17:27:17 - - Information: RV type manager created 36 17:27:17 - - Information: RV lists created 37 17:27:17 - - Information: Spline manager created 38 17:27:17 - - Information: Time table manager created 39 17:27:17 - - Information: Currency manager created 40 17:27:18 - - Warning: load x File - Direct9 Error: D3DERR_INVALIDCALL (-2005530516) 41 17:27:18 - - Warning: load x File - Direct9 Error: D3DERR_INVALIDCALL (-2005530516) 42 17:27:18 - - Warning: load x File - Direct9 Error: D3DERR_INVALIDCALL (-2005530516) 43 17:27:18 - - Information: Visual helpers created 44 17:27:18 - - Information: Audio Mixer erstellen... 45 17:27:18 - - Information: --- 46 17:27:18 - - Information: Download Internet Textures... 47 17:27:18 - - Information: Input Manager erstellen... 48 17:27:18 - - Information: Tastaturbefehle laden... 49 17:27:18 - - Information: Game Controller laden... 50 17:27:18 - - Information: Progman initialisieren... 51 17:27:18 - - Information: Partikelvertices initialisieren...
  8. Hello After OMSI 1 (well, Aerosoft Actually) giving up on me, I've been using OMSI 2. My PC needed the operating system reinstalling, but since then OMSI 2 never gets past the first initialising screen without errors (even after multiple re-installations) After a typical 'Zugriff' error, I click OK, the screen goes black and then it says 'Eigenschaft Visible kann in OnShow oder OnHide nicht verandert werden' and won't go any further. This is weird as OMSI worked fine before and it's not even a new operating system, just the old one reinstalled. This is frustrating as I can't even get to the menu or options. I've seen something about deleting files in the Plugins folder in the files, but my Plugins folder is empty. Can anyone help? (right now, none of my two copies of OMSI work and that's pretty annoying) Thanks in advance, timr673
  9. View File Nottingham City Transport repaints for MB O405 Hi This repaint sees the Mercedes O405 in eight liveries, five in Nottingham City Tranport's green and cream colours from the '90s and early 2000s with various line branding plus one in the later 'network' style livery (with navy line branding), a South Notts bus and as a bonus livery for separate company Trent Buses. The green and cream variant comes in: Plain green & cream Green line branded Orange line branded Navy Line Branded Turquoise Line Branded NCT did not operate O405s but these just represent the NCT paint schemes seen on Alexander PS, Alexander Dash, Leyland National and other types of bus bodywork. After NCT took over the South Notts buses they kept the colours and name, just painting the buses in a livery pattern the same as the green examples, hence the inclusion of the South Notts bus. Around 2000 time they introduced colour-coded lines for the bus services, soon launching the Go2 buses in a predominantly white livery (with colour coding) and the rest of the services to follow, initially in a livery like the network navy line repaint. Hope they are useful and enjoyable, tr673 To install: Extract files using WinRAR or something Go into the MB O405 NCT Repaints folder copy and paste the textures and CTI files into Vehicles > MB O405 Camo > Repaints_Camus Submitter timothyr673 Submitted 04/20/2017 Category OMSI Repaints Which version of OMSI is this download for ? V1  
  10. Version 1.0.0

    36 downloads

    A pack of eight repaints for the O405 Camo. 5 Nottingham City, one South Notts and a bonus one. Hi This repaint sees the Mercedes O405 in eight liveries, five in Nottingham City Tranport's green and cream colours from the '90s and early 2000s with various line branding plus one in the later 'network' style livery (with navy line branding), a South Notts bus and as a bonus livery for separate company Trent Buses. The green and cream variant comes in: Plain green & cream Green line branded Orange line branded Navy Line Branded Turquoise Line Branded NCT did not operate O405s but these just represent the NCT paint schemes seen on Alexander PS, Alexander Dash, Leyland National and other types of bus bodywork. After NCT took over the South Notts buses they kept the colours and name, just painting the buses in a livery pattern the same as the green examples, hence the inclusion of the South Notts bus. Around 2000 time they introduced colour-coded lines for the bus services, soon launching the Go2 buses in a predominantly white livery (with colour coding) and the rest of the services to follow, initially in a livery like the network navy line repaint. Hope they are useful and enjoyable, tr673 To install: Extract files using WinRAR or something Go into the MB O405 NCT Repaints folder copy and paste the textures and CTI files into Vehicles > MB O405 Camo > Repaints_Camus
  11. AI Bus Problem on (and off!) Splines... (help?)

    Thanks again. I'd done this but realised my error was not inputting anything into the 'name' section of the .hof file so it was still called 'Spandau'. I've also cracked how to assign buses with specific repaints on lines (using the repaints 'name', NOT what the .cti file is called!). Things are looking good!
  12. AI Bus Problem on (and off!) Splines... (help?)

    Thanks, but I managed to make it work by altering the docking distance until the bus stopped where I want it. I also tested to see if the bus followed all the trackentries correctly after I corrected some duplicated inputs. It did so the bus drives normally now. I will keep in mind the info in case other stop cubes present the same problem. Now I'm just trying to make sure the AI bus always loads the correct .hof file because at the moment it loads a random one and the destination doesn't work.
  13. AI Bus Problem on (and off!) Splines... (help?)

    Thanks for reply! This is the bus stop cube and the path. I have reduced the problem slightly by reducing the 'dock dist.' number in the bus stop options (to 10). The bus does now stop, but still buries itself into the building and then waits for about 20 minutes instead of carrying on it's route. I might have been able to fix the teleporting bus because I found duplicated and mismatched track entries in the area where I had the problem, but I have not tested to see if it works yet...
  14. Why are my repaints not working??

    I have used repaint tool a few times (the one from the OMSI sdk). Here's how I use it: First I find the exterior texture template for the bus I want to repaint. Copy it Repaint it (you have to cover it completely and any areas you leave the same must be magenta colour) and save open 'repaint tool' click the choose repaint or whatever's written on the button find the thing I just repainted and select it wait for the tool to work it's magic get the .dds file at the end put into the 'werbung' (repaint) file of the respective bus and create a .cti file open OMSI to test the repaint. Don't know if this is what you do but it's always worked for me. If there is an error I made somewhere in the process the repaint goes silver if the texture is broken (or white if there is no texture working at all) and I go through the steps again and then it usually works. :-)
  15. Found a Leyland National for OMSI.

    Where does it come from? I've seen pictures but never any reference to downloads (so I assume it was never posted on to any download sites)?
×