What's up, RMers?

[Son_Rukiri]

The only thing I'm working on right now is the camera system for my RPG Kit.

[kyonides]

Since KSacrifice was not close enough to be finished, I have polished it a bit more and here you can check out the results!

The gems will change its color depending on which option is currently turned on (or selected).

[Mel]

I finally managed to tell my graphics card to stop stretching RMXP games to 16:9 resolution in full screen. That always annoyed me.

[Son_Rukiri]

I finally managed to tell my graphics card to stop stretching RMXP games to 16:9 resolution in full screen. That always annoyed me.

Nvidia or Amd? 
In Nvidia you just change the perform scaling option from Monitor to GPU which usually solves 99.99% of the problems, I believe AMD has a similar feature or may be named something else.

Been working on my Camera all day, currently working on a borderless full screen option.

Code:

//--------------------------------------------
// XenRPG Camera
// Ver 1.0
// XenRPG_camera(dw, dh, psf, target, cam_border_x, cam_border_y, aa, vsync, fullscreen);
//--------------------------------------------

//--------------------------------------------
// Init Variables
//--------------------------------------------
#region
globalvar display_width, display_height, internal_width, internal_height;
globalvar camera, camera_target, camera_border_x, camera_border_y, _curRoom;
globalvar aa, vsync, fullscreen, pixel_scaling_factor;
#endregion

//--------------------------------------------
// Game Settings
//--------------------------------------------
#region
display_width = argument0;
display_height = argument1;
pixel_scaling_factor = argument2;
internal_width = display_width / pixel_scaling_factor;
internal_height = display_height / pixel_scaling_factor;

aa = argument6;
vsync = argument7;
fullscreen = argument8;
#endregion

//--------------------------------------------
// Camera Settings
//--------------------------------------------
#region
_curRoom = room_add();
room_set_view_enabled(_curRoom,true);
camera = camera_create();
camera = camera_create_view(x, y, internal_width, internal_height, 0, self, -1, -1, internal_width / 2, internal_height / 2);
room_set_width(_curRoom, internal_width);
room_set_height(_curRoom, internal_height);
room_set_viewport(_curRoom, 0, true, 0, 0, internal_width, internal_height);
camera_matrix = matrix_build_lookat(x, y, -TILESIZE, x, y, 0, 0, 1, 0);
camera_projection = matrix_build_projection_ortho(internal_width, internal_height, 1, 9999);
camera_set_view_mat(camera, camera_matrix);
camera_set_proj_mat(camera, camera_projection);
view_camera[0] = camera;

cam_target = argument3;
cam_border_x = argument4;
cam_border_y = argument5;

window_set_size(internal_width * 1, internal_height * 1);
surface_resize(application_surface, internal_width, internal_height);
application_surface_draw_enable(true)
display_reset(aa, vsync);

if (os_type == os_windows || os_macosx || os_linux) {
  window_set_fullscreen(true);
}
#endregion

Code:

XenRPG_camera(1280, 720, 2, object18, 64, 32, 16, true, false);

Code:

//Update/lerp the camera pos
var cam_x = camera_get_view_x(camera);
var cam_y = camera_get_view_y(camera);

camera_set_view_pos(camera, lerp(cam_x, cam_target.x, 1), lerp(cam_y, cam_target.y, 1))

x = clamp(x, cam_target.x-cam_border_x, cam_target.x+cam_border_x);
y = clamp(y, cam_target.y-cam_border_y, cam_target.y+cam_border_y);

// RPG Maker screen size changes
if (os_type == os_windows || os_macosx || os_linux) {
    // If full screen go back to windowed mode
    if (window_get_fullscreen()) {
        if (keyboard_check_pressed(vk_f12)) {
            window_set_fullscreen(false);
            window_set_size(internal_width * 1, internal_height * 1);
            surface_resize(application_surface, internal_width, internal_height);
            application_surface_draw_enable(true)
            display_reset(aa, vsync);
       }
  } else {
        // if in windowed mode switch between base and double window sizes or go full screen
        if (keyboard_check_pressed(vk_f4)) {
            window_set_fullscreen(false);
            window_set_size(internal_width * 1, internal_height * 1);
            surface_resize(application_surface, internal_width, internal_height);
            application_surface_draw_enable(true)
            display_reset(aa, vsync);
        }
        if (keyboard_check_pressed(vk_f5)) {
            window_set_fullscreen(false);
            window_set_size(internal_width * 2 * 1, internal_height * 2 * 1);
            surface_resize(application_surface, internal_width, internal_height);
            application_surface_draw_enable(true)
            display_reset(aa, vsync);
        }
       if (keyboard_check_pressed(vk_f12)) {
           window_set_fullscreen(true);
       }
  }
}

[kyonides]

Let me see, I've been busy and had no time to spend coding anything. This means there's no place for personal requests. Besides I started developing the KustomSkill XP script. What is it supposed to do? It should let you do two specific things. First you will need to get or predefine or perhaps even steal a Skill Talisman! Then you might get a few general and skill specific bonuses (or some sp cost increase in exchange for extra power). It turns out your skills will suck at first because they are at level 0, yeah not even 1, still you can deal some damage... Keep in mind you can improve the talisman! (At least up to some point...)

My script will modify some basic skill effect script sections so it might not be fully with a few scripts... Any useful suggestions are welcome.

[Son_Rukiri]

My 3 day weekend is almost over (granted only had today off as I have to work Saturday :( )
I managed to get my camera pretty smooth and has a border system so the camera doesn't follow every pixel but around a border, by default 64x32 is what I use and it works great!
Tested with both my free and grid movement scripts and everything works as it's suppose to!

Now the next step is to create classes, Game Maker Language doesn't have classes but the way you do this is with parent_objects and well placed scripting.
I'm going to start with game_player, now keep in mind player is done but I have to adjust a few things so it can be a copy/past job for game_npc.

Now keep in mind I have moved on from RPG Maker for a few reasons, 1 obviously being I prefer working on A-RPGs everyone and even the developers know and do tell people RPG Maker is not a great tool for A-RPGs... I would love for Kadakowa to release a action rpg maker, but with Pixel Game Maker this will probably be the tool they tell you to go to. The second reason I feel I'm bogged and slowed down, obviously rewriting entire cores and over 10k lines of code will do that... MV has been released for almost 3 years now, in that same span since XP, VX, and even Ace there were complete ABS scripts (albeit not good, but complete non the less). ABS scripts for MV get cancelled or are in dev hell, QABS tghe one with actual promise has essentially been in progress since MV was launched... The Zelda Project (XP and Ace Versions) were never finished, but the team behind it well always seemed to change...

Even my own MV script which I just never decided to talk about mainly because it to has been in dev hell since launch is about as close as xenrpg is to being done... Not close at all... With Xen I just haven't had time to really work on it or I just didn't feel like coding. With my MV abs I was putting in 8-12 hours a day for 3 years and guess what? It's not even close to being done>< It's about as far as QABS or the Chrono Engine is, but my reasoning for not making a page is simple. MV has performance issues, on a machine that can run AAA games at 4k/60fps (not maxed of course but high settings).

This is the one reason why I decided to stay with Game Maker, rapid development and shit works the way it's supposed to and oh, no performance issues!

My expectations for RPG have been going downhill for awhile, for traditional RPGs (basically everything that isn't real-time) it's great! Pixel MV seems to be going in a good direction, nodes have parameters so I guess custom algorithms and possibly math functions can be used (yay). The next update will probably go over the nodes in better detail, cocos2d-x, programable event notes, has me excited! But, will it suck and more importantly be worth the $99 asking price?

[kyonides]

There was IG Maker by Enterbrain/Kadokawa but I refused to install about 1 GB of "sucker" software that might not work as expected, plus it gave me a bad first impression like not being as intuitive as it was supposed to be... Plus it could have been even heavier than MV while running the game project... Oh, and it didn't seem to offer any scripting support...

[Son_Rukiri]

There was IG Maker by Enterbrain/Kadokawa but I refused to install about 1 GB of "sucker" software that might not work as expected, plus it gave me a bad first impression like not being as intuitive as it was supposed to be... Plus it could have been even heavier than MV while running the game project... Oh, and it didn't seem to offer any scripting support...

You couldn't code for anything in IG Maker, it had some basic variable and switch support but honestly it was too far limited to be used for anything and yea the 1gb was a lot for an engine that basically sucks  

[Mel]

I would only switch to a new engine if I'm able to import my RMXP project into it without many complications.
I just put too many hours into it (something around 2000 over the years) to start from scratch.

[Son_Rukiri]

I would only switch to a new engine if I'm able to import my RMXP project into it without many complications.
I just put too many hours into it (something around 2000 over the years) to start from scratch.

The only thing you can switch to is RGSS3, or the open implementation of RGSS/XP.
2000 hours? wow, I wouldn't switch if I had that much into it either!