1. Hello Guest,

    We wanted to let you know that the NXS17 templates and viewers have been released!

    Grab them HERE
  2. Hello Guest,

    We wanted to let you know that besides the NXS17 templates and viewers, now we have released the NXS17 Mod as well!

    Grab the latest files HERE
  3. Hello Guest,

    We wanted to let you know that we are trying out a new feature at SRD. Your feedback is needed!

    Read more about the chatbox HERE

PROJECT: Chapman Track Creator

Discussion in 'NR2003 General Discussion' started by TChapman500, Dec 19, 2017.

  1. dacinch8

    dacinch8 Rookie Without A Cause

    Messages:
    46
    Likes Received:
    59
    Wow. This can be way better than Sandbox, Actually. Can’t wait to try it out on my WIP racetrack!
     
    TChapman500 likes this.
  2. TChapman500

    TChapman500 Member

    Messages:
    19
    Likes Received:
    48
    Progress Report Time:
    I think I finally solved the problem with the editor's API, and I've published an early version of the API on GitHub (link on the official page). I'm currently working on (a) making the mesh generator feature-complete, (b) making a grid generator and (c) getting the track editor to utilize all of the functionality of the API. The New Project dialog box has been updated because the previous version was malfunctioning for some unknown reason. This community doesn't need to use the API right now, as I'm using NR2003 to test the API as I develop the track editor.

    Also, everything about my website is working as it should. I even added a forum specifically for feature requests. Probably starting next week, I'll start posting updates on the official forum for the CTC in the appropriate thread as well as continuing to post updates here.
     
  3. TChapman500

    TChapman500 Member

    Messages:
    19
    Likes Received:
    48
    Progress Report Time:
    This week was spent debugging a few quarks of the MFC framework that was causing the track editor to misbehave. The good news is that it was just a single line of code that mapped a message to a function that the track editor was never going to use. This line of code is placed there for every "MDI" project using the MFC framework. That single line of code (and the corresponding function) has been removed.

    It pleases me to report some very good news concerning the compiler that I'm using. Visual Studio 2017 recently got an update that fixed a problem that forced me to use VS2015. So now I don't have to use two different compiler versions on this project. Oh, and I finally got the old version of the track editor working again after trying desperately to figure out what was wrong with the new version. It's coming to the point where I could just delete the old version and it wouldn't affect the project at all. I've kept it all this time more as a reference in case something goes wrong. But now, because the new version has all of the features of the old version, I almost don't need the old version anymore.

    The API got a major update as well. There are now more functions and more options to configure. Plus there's a brief tutorial on how to use the API on the GitHub page. I also have been using NR2003 to test the API functionality and it appears to be working perfectly.

    The Chapman Track Creator now has multi-threaded rendering implemented. That said, I'll be implementing a way for the track editor to update and send the generated mesh data over to the DLLs to be rendered. Now that the API seems to be working fairly well, I have been adding stuff to the UI to allow the user to change how the track is presented to them. Also on the topic of mesh generation, I've made a few changes to the event system that will make it easier for me to get the various objects to communicate with each other. I guess I should also implement a way for users to add stuff via the viewport now that the new rendering system is working. But first, I'm going to finish-up the mesh generator.
     
    nj9703, Mystical and USSTalladega like this.
  4. Mystical

    Mystical Always 110%

    Messages:
    3,624
    Likes Received:
    4,855
    When this project is out of the beta stages and you plan to finalize the UI if you need someone to create any logos, desktop icons, startup screens, or other images for the program I could definitely help with that (if you want the help of course).
     
    InsideLine and RacerXero84 like this.
  5. USSTalladega

    USSTalladega Cruising at Warp 9

    Messages:
    4,113
    Likes Received:
    1,079
    I will be watching your progress with great interest. It's no secrete that editing cameras and pit stalls for this game can be an absolute bitch. Checking such changes in real-time has been an NR2k3 dream of mine. Though regarding LP files how do you plan on going about creating them? I can see using a path tool like system with points that you can add to make it as smooth as possible. But then there is the main AI raceline which requires you to actually drive the track.

    I just thought of something that could be handy. Ghost cars. Ten cars max. Generic low poly stock car shape.

    Uses:
    Checking the alignment and spacing of each individual starting grid and pit stall positions in relation to adjacent stalls.
    Examining width and potential race-ability of a track segment. Ghost cars would only be a stationary guide.
    Checking changes to the camera angles. Ghost cars could either be single file(user specified drafting distance) or side by side(user defined lateral distance) along an LP line of your choice. 100mph max speed?

    Definitely not a must have but if you deem it reasonable then cool.
     
  6. TChapman500

    TChapman500 Member

    Messages:
    19
    Likes Received:
    48
    Logos and desktop items I will need help with. There probably won't be any start-up screens though, but there will be icons on the buttons that I would like help with. I can send you a copy of the ribbon as well as the image used for the Scene Explorer icons and the ClassID enum.

    Thanks.

    Which is exactly why I want this track editor to be able to do exactly that!

    I'll probably have a mixture of auto-generated AI lines and Bezier curves to tweak what's generated. I noticed a while back that the simulator tries to predict the maximum possible speed down the LPs that you drew with the car. I may try doing the same thing.

    That's an idea, but I'm thinking that the max should be the number of vehicles supported by simulator plus the pace car.

    For the first point, I intend to have a at least a rectangle drawn around the stalls as well as an additional buffer rectangle for stuff like stall entry, exit, and space between the car and the wall. Though I like the idea of using ghost cars for this. I also like the idea of your second and third points. But if I can get the correct speed predictions on the LP files, then we won't need an arbitrary maximum speed.
     
    USSTalladega and Mystical like this.
  7. Mystical

    Mystical Always 110%

    Messages:
    3,624
    Likes Received:
    4,855
    Sounds great. I can always mock up real quick placeholder images for you and we can refine them as the project goes. I can format the images to almost any standardized file you need that most programs would be compatible with as well.
     
  8. USSTalladega

    USSTalladega Cruising at Warp 9

    Messages:
    4,113
    Likes Received:
    1,079
    That all sounds great. You are a trooper for even attempting to take on such an endeavor.
     

Share This Page